# publicrailwaycat/emacs-mac-port

### Subversion checkout URL

You can clone with HTTPS or Subversion.

Fetching contributors…

Cannot retrieve contributors at this time

file 615 lines (467 sloc) 24.961 kb
 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 Copyright (C) 2007-2013 Free Software Foundation, Inc.See the end of the file for license conditions.NOTES ON COPYRIGHTS AND LICENSESSome terminology:A "copyright notice" consists of one or a few lines of this format:"Copyright (C) 2006, 2007 Free Software Foundation, Inc."A "license notice" is a statement of permissions, and is usually muchlonger, eg the text "GNU Emacs is free software...".Summary for the impatient:1. Don't add code to Emacs written by someone other than yourselfwithout thinking about the legal aspect. Even if the changes aretrivial, consider if they combine with previous changes by the sameauthor to make a non-trivial total. If so, make sure they have anassignment. If adding a whole file adjust the copyright statements inthe file.2. When installing code written by someone else, the ChangeLog entryshould be in the name of the author of the code, not the person whoinstalls it. Also use bzr commit's "--author" option.Do not install any of your own changes in the same commit.3. With images, add the legal info to a README file in the directorycontaining the image.4. If you add a lot of text to a previously trivial file that had nolegal notices, consider if you should add a copyright statement.5. Please don't just add an FSF copyright without checking that is theright thing to do.Every non-trivial file distributed through the Emacs repository should beself-explanatory in terms of copyright and license. This includesfiles that are not distributed in Emacs releases (for example, theadmin/ directory), because the whole Emacs repository is publiclyavailable.The definition of triviality is a little vague, but a rule of thumb isthat any file with less than 15 lines of actual content is trivial. Ifa file is auto-generated (eg ldefs-boot.el) from another one in therepository, then it does not really matter about adding a copyrightstatement to the generated file.Legal advice says that we could, if we wished, put a license noticeeven in trivial files, because copyright law in general looks at theoverall work as a whole. It is not _necessary_ to do so, and rmsprefers that we do not. This means one needs to take care that trivialfiles do not grow and become non-trivial without having a licenseadded. NB consequently, if you add a lot of text to a small file,consider whether your changes have made the file worthy of a copyrightnotice, and if so, please add one.It can be helpful to put a reminder comment at the start of a trivialfile, eg: "add a license notice if this grows to > 10 lines of code".The years in the copyright notice should be updated every year (seefile "years" in this directory). The PDF versions of refcards etcshould display copyright notices (an exception to the rule about"generated" files), but these can just display the latest year. Thefull list of years should be kept in comments in the source file. Ifthese are distributed in the repository, check in a regeneratedversion when the tex files are updated.Copyright changes should be propagated to any associated repositories(eg Gnus, MH-E), but I think in every case this happens automatically(?).All README (and other such text files) that are non-trivial shouldcontain copyright statements and GPL license notices, exactly as .elfiles do (see e.g. README in the top-level directory). Before 2007,we used a simple, short statement permitting copying and modificationprovided legal notices were retained. In Feb 2007 we switched to thestandard GPL text, on legal advice. Some older text files in etc/should, however, keep their current licenses (see below for list).For image files, the copyright and license details should be recordedin a README file in each directory with images. (Legal advice saysthat we need not add notices to each image file individually, if theyallow for that.). It is recommended to use the word "convert" todescribe the automatic process of changing an image from one format toanother (http://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00618.html).When installing a file with an "unusual" license (after checking firstit is ok), put a copy of the copyright and license in the file (ifpossible. It's ok if this makes the file incompatible with itsoriginal format, if it can still be used by Emacs), or in a READMEfile in the relevant directory.The vast majority of files are copyright FSF and distributed under theGPL. A few files (mainly related to language and charset support) arecopyright AIST alone, or both AIST and FSF. (Contact Kenichi Handawith questions about legal issues in such files.) In all these cases,the copyright years in each file should be updated each year.There are some exceptions to the points in the previous paragraph, andthese are listed below for reference, together with any files wherethe copyright needs to be updated in "unusual" ways.If you find any other such cases, please consult to check they are ok,and note them in this file. This includes missing copyright notices,and "odd" copyright holders. In most cases, individual authors shouldnot appear in copyright statements. Either the copyright has beenassigned (check copyright.list) to the FSF (in which case the originalauthor should be removed and the year(s) transferred to the FSF); orelse it is possible the file should not be in Emacs at all (pleasereport!).Note that it seems painfully clear that one cannot rely on commit logs,or even ChangeLogs, for older changes. People often installed changesfrom others, without recording the true authorship.[For reference, most of these points were established via email withrms, 2007/1, "Copyright years".In March 2011, information on some files no longer included was removed.Consult older versions of this document if interested.]lisp/version.el # emacs-copyrightlib-src/ebrowse.c # versionlib-src/etags.c # print_versionlib-src/rcs2log # CopyrightCocoa/Emacs.base/Contents/Info.plistCocoa/Emacs.base/Contents/Resources/English.lproj/InfoPlist.stringsGNUstep/Emacs.base/Resources/Info-gnustep.plist   set-copyright' in admin.el will do all the above.aclocal.m4configurem4/*.m4 - copyright FSF, with unlimited permission to copy, distribute and modifylib/Makefile.in - copyright FSF, with MIT-like licensebuild-aux/install-sh - this file is copyright MIT, which is OK. Leave the copyright alone.etc/refcards/*.tex  also update the \def\year macro for the latest year.etc/future-bug - doesn't need a humorless disclaimer, because Karl Fogel says we can consider it part of Emacs, and he has a blanker disclaimer for Emacs changes. (email to rgm "[Emacs-commit] emacs/etc future-bug", 2007028)etc/letter.pbm,letter.xpm  - trivial, no notice needed.etc/FTP, ORDERS  - trivial (at time of writing), no license neededetc/GNU, INTERVIEW, LINUX-GNU, MOTIVATION, SERVICE, THE-GNU-PROJECT,WHY-FREE  rms: "These are statements of opinion or testimony. Their licenses  should permit verbatim copying only. Please don't change the  licenses that they have. They are distributed with Emacs but they  are not part of Emacs."etc/HELLO  standard notices. Just a note that although the file itself is not  really copyrightable, in the wider context of it being part of  Emacs (and written by those with assignments), a standard notice is  fine.etc/MAILINGLISTS  rms: simple license is fine for this fileleim/CXTERM-DIC/4Corner.tit, ARRAY30.tit, CCDOSPY.tit, ECDICT.tit,ETZY.tit, PY-b5.tit, Punct-b5.tit, Punct.tit, QJ-b5.tit, QJ.tit,SW.tit, TONEPY.tit, ZOZY.tit  - leave the copyrights alone.leim/MISC-DIC/CTLau-b5.html, CTLau.html, cangjie-table.b5, cangjie-table.cns,pinyin.map, ziranma.cin  - leave the copyright alone.Note that pinyin.map, ziranma.cin (and hence the generatedleim/quail/PY.el, ZIRANMA.el) are under GPLv1 or later.leim/SKK-DIC/SKK-JISYO.Lja-dic/ja-dic.el  (the latter is auto-generated from the former). Leave the copyright alone.lib-src/etags.c  Copyright information is duplicated in etc/ETAGS.README. Update that  file too.  Until 2007 etags.c was described as being copyright FSF and Ken Arnold.  After some investigation in Feb 2007, then to the best of our  knowledge we believe that the original 1984 Emacs version was based  on the version in BSD4.2. See for example this 1985 post from Ken Arnold:      I have received enough requests for the current source to ctags    to post it. Here is the latest version (what will go out with    4.3, modulo any bugs fixed during the beta period). It is the    4.2 ctags with recognition of yacc and lex tags added.  See also a 1984 version of ctags (no copyright) posted to net.sources:    Version of etags.c in emacs-16.56 duplicates comment typos.  Accordingly, in Feb 2007 we added a 1984 copyright for the  University of California and a revised BSD license. The terms of  this require that the full license details be available in binary  distributions - hence the file etc/ETAGS.README. The fact that the  --version output just says "Copyright FSF" is apparently OK  from a legal point of view.lisp/cedet/semantic/imenu.el  - See http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg00410.html   in which Eric Ludlam established that the remaining contributions   from authors other than himself were negligible.lisp/play/tetris.el  - no special rules about the copyright. We note here that we believe  (2007/1) there is no problem with our use of the name "tetris" or  the concept.  rms: "My understanding is that game rules as such are not copyrightable."    rms: Legal advice is that we are ok and need not worry about this.lisp/net/tramp.el  - there are also copyrights in the body of the file. Update these too.lwlib/rms (2007/02/17): "lwlib is not assigned to the FSF; we don't considerit part of Emacs. [...] Therefore non-FSF copyrights are ok in lwlib."NB don't change the GPL version used for lwlib .c and .h files (seebelow).FSF copyrights should only appear in files which have undergonenon-trivial cumulative changes from the original versions in the LucidWidget Library. NB this means that if you make non-trivial changes toa file with no FSF copyright, you should add one. Also, if changes arereverted to the extent that a file becomes basically the same as theoriginal version, the FSF copyright should be removed.In my (rgm) opinion, as of Feb 2007, all the non-trivial files differsignificantly from the original versions, with the exception oflwlib-Xm.h. Most of the changes that were made to this file havesubsequently been reverted. Therefore I removed the FSF copyright fromthis file (which is arguably too trivial to merit a notice anyway). Iadded FSF copyright to the following files which did not have themalready: Makefile.in, lwlib-Xaw.c, lwlib-int.h (borderline),lwlib-utils.c (borderline), lwlib.c, lwlib.h.Copyright years before the advent of public CVS in 2001 were thosewhen I judged (from the CVS logs) that non-trivial amounts of changehad taken place. I also adjusted the existing FSF years in xlwmenu.c,xlwmenu.h, and xlwmenuP.h on the same basis.Note that until Feb 2007, the following files in lwlib were lackingnotices: lwlib-int.h, lwlib.h, lwlib-Xaw.h, lwlib-Xlw.h, lwlib-utils.hThe following files did not list a Lucid copyright: xlwmenu.h,xlwmenuP.h.To the best of our knowledge, all the code files in lwlib wereoriginally part of the Lucid Widget Library, even if they did not sayso explicitly. For example, they were all present in Lucid Emacs 19.1in 1992. The exceptions are the two Xaw files, which did not appeartill Lucid Emacs 19.9 in 1994. The file lwlib-Xaw.h is too trivial tomerit a copyright notice, but would presumably have the same one aslwlib-Xaw.c. We have been unable to find a true standalone version ofLWL, if there was such a thing, to check definitively.To clarify the situation, in Feb 2007 we added Lucid copyrights andGPL notices to those files lacking either that were non-trivial,namely: lwlib-int.h, lwlib.h, xlwmenu.h, xlwmenuP.h. This representsour best understanding of the legal status of these files. We alsoclarified the notices in Makefile.in, which was originally theMakefile auto-generated from Lucid's Imakefile.As of Feb 2007, the following files are considered too trivial fornotices: lwlib-Xaw.h, lwlib-Xlw.h, lwlib-utils.h.The version of lwlib/ first installed in Emacs seems to be the same asthat used in Lucid Emacs 19.8 (released 6-sep-93); except the two Xawfiles, which did not appear till Athena support was added in LucidEmacs 19.9. In Lucid Emacs 19.1, all files were under GPLv1 or later,but by Lucid Emacs 19.8, lwlib.c and xlwmenu.c had been switched to v2or later. These are the versions that were first installed in Emacs.So in GNU Emacs, these two files have been under v2 or later since1994.It seems that it was the intention of Lucid to use v1 or later(excepting the two files mentioned previously); so this is the licensewe have used when adding notices to code that did not have noticesoriginally. Although we have the legal right to switch to v2 or later,rms prefers that we do not do so.doc/*/doclicense.texi  - leave the copyright alone in this imported file.doc/*/*.texi - All manuals should be under GFDL (but see below), andshould include a copy of it, so that they can be distributedseparately. faq.texi has a different license, for some reason no-onecan remember.http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00583.htmlhttp://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00618.htmldoc/misc/mh-e.texi is dual-licensed (GPL and GFDL) per agreement withFSF (reconfirmed by rms Aug 25 2008). Discussion withlicensing@fsf.org starting on Thu, 07 Aug 2003 with subject:"[gnu.org #58812] Changing license of MH-E manual"msdos/is_exec.c, sigaction.c - these files are copyright DJ Delorie.Leave the copyrights alone. Leave the Eli Zaretskii copyright inis_exec.c alone. See the msdos/README file for the legal history ofthese files.msdos/sed*.inp - These files are copyright FSF and distributed underan MIT-like license.oldXMenu/  Keep the "copyright.h" method used by X11, rather than moving the  licenses into the files. Note that the original X10.h did not use  copyright.h, but had an explicit notice, which we retain.If you make non-trivial changes to a file which does not have an FSFnotice, add one and a GPL notice (as per Activate.c). If changes to afile are reverted such that it becomes essentially the same as theoriginal X11 version, remove the FSF notice and GPL.Only the files which differ significantly from the original X11versions should have FSF copyright and GPL notices. At time of writing(Feb 2007), this is: Activate.c, Create.c, Internal.c. I (rgm)established this by diff'ing the current files against those in X11R1,and when I found significant differences looking in the ChangeLog forthe years they originated (the CVS logs are truncated before 1999). Itherefore removed the FSF notices (added in 200x) from the otherfiles. There are some borderline cases IMO: AddSel.c, InsSel.c,XMakeAssoc.c, XMenu.h. For these I erred on the side of NOT adding FSFnotices.With regards to whether the files we have changed should have GPLadded or not, rms says (2007-02-25, "oldXmenu issues"):    It does not make much difference, because oldXmenu is obsolete    except for use in Emacs (and it is not normally used in Emacs any    more either).    So, to make things simple, please put our changes under the GPL.insque.c had no copyright notice until 2005. The version of insque.cadded to Emacs 1992-01-27 is essentially the same as insremque.c addedto glic three days later by Roland McGrath, with an FSF copyright andGPL, but no ChangeLog entry:To the best of his recollection, McGrath (who has a copyrightassignment) was the author of this file (email from roland at frob.comto rms, 2007-02-23, "Where did insque.c come from?"). The FSFcopyright and GPL in this file are therefore correct as far as weunderstand it.Imakefile had no legal info in Feb 2007, but was obviously based onthe X11 version (which also had no explicit legal info). As it wasunused, I removed it. It would have the same MIT copyright asMakefile.in does now.src/gmalloc.c  - contains numerous copyrights from the GNU C library. Leave them alone.src/ndir.h  - see comments below. This file is OK to be released with Emacs  22, but we may want to revisit it afterwards.** Some notes on resolved issues, for historical information onlyetc/TERMSrms: "surely written either by me or by ESR. (If you can figure outwhich year, I can probably tell you which.) Either way, we have papersfor it." It was present in Emacs-16.56 (15-jul-85). rms: "Then Iconclude it was written by me."lisp/term/README  - had no copyright notice till Feb 2007. ChangeLog.3 suggests it was  written by Eric Raymond. When asked by rms on 14 Feb 2007 he said:    I don't remember writing it, but it reads like my prose and I believe    I wrote the feature(s) it's describing. So I would have been the    likeliest person to write it.    Odds are that I did, but I'm not certain.  Accordingly, FSF copyright was added.src/unexhp9k800.c  http://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00138.html  - briefly removed due to legal uncertainly Jan-Mar 2007. The  relevant assignment is under "hp9k800" in copyright.list. File was  written by John V. Morris at HP, and disclaimed by the author and  HP. So this file is public domain.lisp/progmodes/python.elDave Love alerted us to a potential legal problem:http://lists.gnu.org/archive/html/emacs-pretest-bug/2007-04/msg00459.htmlOn consultation with a lawyer, we found there was no problem:http://lists.gnu.org/archive/html/emacs-devel/2007-05/msg00466.html** Issues that are "fixed" for the release of Emacs 22, but we may   wish to revisit later in more detailadmin/check-doc-strings  File says it's in the public domain, but that might not make it so.etc/e/eterm-color.tisrc/ndir.h  On legal advice from Matt Norwood, the following comment was added  to these files in Feb/Mar 2007:    The code here is forced by the interface, and is not subject to    copyright, constituting the only possible expression of the    algorithm in this format.  With the addition of this notice, these files are OK for the  upcoming Emacs-22 release. Post-release, we can revisit this issue  and possibly add a list of all authors who have changed these files.  (details in email from Matt Norwood to rms, 2007/02/03).src/s/aix3-2.h, hpux8.h, hpux9.h, irix5-0.h, netbsd.h, usg5-4-2.h  [note some of these have since been merged into other files]  - all these (not obviously trivial) files were missing copyrights  till Feb 2007, when FSF copyright was added. Matt Norwood advised:    For now, I think the best policy is to assume that we do have    assignments from the authors (I recall many of these header files    as having been originally written by rms), and to attach an FSF    copyright with GPL notice. We can amend this if and when we    complete the code audit. Any additions to these files by    non-assigned authors are arguably "de minimis" contributions to    Emacs: small changes or suggestions to a work that are subsumed in    the main authors' copyright in the entire work.Here is my (rgm) take on the details of the above files:? irix5-0.h  I would say started non-trivial (1993, jimb, heavily based  on irix4-0.h). A few borderline non-tiny changes since.usg5-4-2.h started non-trivial, but was heavily based on usg5-4.h, which was and is copyright FSF. only tiny changes since installed.aix3-2.h, hpux8.h, hpux9.h, netbsd.h  started trivial, grown in tiny changes.netbsd.h:Roland McGrath said to rms (2007/02/17): "I don't really rememberanything about it. If I put it in without other comment, then probablyI wrote it myself."Someone might want to tweak the copyright years (for dates before2001) that I used in all these files.Note: erring on the side of caution, I also added notices to somefiles I thought might be considered non-trivial (if one includescomment) in s/:  aix4-1.h hpux10.h irix6-5.h  sol2.h(everything with > 30 non-blank lines, which at least is _some_ kind ofsystem)*** These are copyright issues that need not be fixed until after    Emacs 22 is released (though if they can be fixed before, that is    obviously good):Is it OK to just bzr remove' a file for legal reasons, or issomething more drastic needed? A removed file is still available fromthe repository, if suitable options are applied. (This issue obviouslydoes not affect a release).  rms: will ask lawyerMake sure that all files with non-standard copyrights or licenses arenoted in this file.REMOVED etc/gnu.xpm, nt/icons/emacs21.ico, nt/icons/sink.ico  - Restore if find legal info. emacs21.ico is not due to Davenport.  Geoff Voelker checked but could not find a record of where it came  from.etc/images  Image files from GTK, Gnome are under GPLv2 (no "or later"?). RMS will  contact image authors in regards to future switch to v3.etc/TUTORIAL* (translations)  switch to GPL (see english TUTORIAL)  rms: "We can leave the TUTORIAL translations alone until their  maintainers update them."  Can adapt short license text from end of GPL translations at:  http://www.gnu.org/licenses/translations.html  Only a few sentences around the license notice need changing from  previous version.Done: TUTORIAL.eo*** These are copyright issues still to be addressed:None known.** NOTES ON RELICENSING TO GPL3The EMACS_22_BASE branch was changed to GPLv3 (or later) 2007/07/25.Some notes:(see http://lists.gnu.org/archive/html/emacs-devel/2007-07/msg01431.html)1. There are some files in the Emacs tree which are not part of Emacs (egthose included from Gnulib). These are all copyright FSF and (at timeof writing) GPL >= 2. rms says may as well leave the licenses of thesealone (may import them from Gnulib again). These are:    Gnulib:    build-aux/compile    build-aux/config.guess    build-aux/config.sub    build-aux/depcomp    build-aux/missing    build-aux/move-if-change    build-aux/snippet/_Noreturn.h    build-aux/snippet/arg-nonnull.h    build-aux/snippet/c++defs.h    build-aux/snippet/warn-on-use.h    doc/man/texinfo.tex    lib/*.[ch]    lib/gnulib.mk    src/gmalloc.c    src/termcap.c    src/tparam.cNote _not_ included in the above are src/regex.{c,h} (rms: "Thatforked version is only in Emacs, so definitely relicense that."), andoldXMenu/insque.c (rms: "We wrote that specifically for Emacs, sodefinitely relicense that.").2. The files that are copyright FSF and AIST, or AIST alone, should beand were updated, ditto the oldXMenu files with FSF copyright, andmsdos/is_exec.c and sigaction.c.3. lwlib/Files originally in Lucid Widget Library were left alone (excludesChangeLog, etc), ie remain under GPL v1 or later, or v2 or later.(rms: "We may as well leave this alone, since we are never going tochange it much.")4. There are some files where the FSF holds no copyright. These wereleft alone:   leim/MISC-DIC/CTLau-b5.html >= v2   leim/MISC-DIC/CTLau.html >= v2     (above included in lisp/international/titdic-cnv.el)   leim/MISC-DIC/pinyin.map >= v1   leim/MISC-DIC/ziranma.cin >= v1   leim/SKK-DIC/SKK-JISYO.L >= v2   leim/SKK-DIC/README >= v2   leim/ja-dic/ja-dic.el >= v25. At time of writing, some non-Emacs icons included from Gnome remainunder GPLv2 (no "or later"). See:   etc/images/gnus/README   etc/images/mail/README   etc/images/README   nt/icons/READMEThis file is part of GNU Emacs.GNU Emacs is free software: you can redistribute it and/or modifyit under the terms of the GNU General Public License as published bythe Free Software Foundation, either version 3 of the License, or(at your option) any later version.GNU Emacs is distributed in the hope that it will be useful,but WITHOUT ANY WARRANTY; without even the implied warranty ofMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See theGNU General Public License for more details.You should have received a copy of the GNU General Public Licensealong with GNU Emacs. If not, see .
Something went wrong with that request. Please try again.