1
0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2024-11-26 07:33:47 +00:00

Merge from emacs-24; up to 2013-01-01T11:02:14Z!rudalics@gmx.at

This commit is contained in:
Glenn Morris 2013-07-25 00:10:56 -07:00
commit 6ccb9cab43
10 changed files with 228 additions and 123 deletions

View File

@ -1,3 +1,26 @@
2013-07-25 Glenn Morris <rgm@gnu.org>
* erc.texi (Special Features): Update contact information.
(History): Avoid using @email.
* eshell.texi (Bugs and ideas): Minor updates.
* faq.texi (Reporting bugs, Origin of the term Emacs)
(Setting up a customization file)
(Using an already running Emacs process, Turning off beeping)
(Packages that do not come with Emacs)
(Replying to the sender of a message): Avoid using @email.
* pcl-cvs.texi (Contributors, Bugs): Avoid using @email.
* reftex.texi (Imprint): Avoid using @email.
* ses.texi (Top): Update bug reporting instructions.
(Acknowledgments): Avoid using @email.
* woman.texi (Introduction, Background): Remove outdated information.
(Bugs, Acknowledgments): Avoid using @email.
2013-07-24 Xue Fuqiao <xfq.free@gmail.com> 2013-07-24 Xue Fuqiao <xfq.free@gmail.com>
* ido.texi: New file. * ido.texi: New file.

View File

@ -234,9 +234,8 @@ forwards.
Different channels and servers may have different language encodings. Different channels and servers may have different language encodings.
In addition, it is possible to translate the messages that ERC uses multiple languages. Please contact the Emacs developers
into multiple languages. Please contact the developers of Emacs at if you are interested in helping with the
@email{emacs-devel@@gnu.org} if you are interested in helping with the
translation effort. translation effort.
@item user scripting @item user scripting
@ -784,9 +783,9 @@ To report a bug in ERC, use @kbd{M-x report-emacs-bug}.
@chapter History @chapter History
@cindex history, of ERC @cindex history, of ERC
ERC was originally written by Alexander L. Belikoff @c abel@@bfr.co.il, sergey.berezin@@cs.cmu.edu
@email{abel@@bfr.co.il} and Sergey Berezin ERC was originally written by Alexander L. Belikoff and Sergey Berezin.
@email{sergey.berezin@@cs.cmu.edu}. They stopped development around They stopped development around
December 1999. Their last released version was ERC 2.0. December 1999. Their last released version was ERC 2.0.
P.S.: If one of the original developers of ERC reads this, we'd like to P.S.: If one of the original developers of ERC reads this, we'd like to
@ -796,8 +795,9 @@ general.
@itemize @itemize
@item 2001 @item 2001
In June 2001, Mario Lang @email{mlang@@delysid.org} and Alex Schroeder @c mlang@@delysid.org, alex@@gnu.org
@email{alex@@gnu.org} took over development and created a ERC Project at In June 2001, Mario Lang and Alex Schroeder
took over development and created a ERC Project at
@uref{http://sourceforge.net/projects/erc}. @uref{http://sourceforge.net/projects/erc}.
In reaction to a mail about the new ERC development effort, Sergey In reaction to a mail about the new ERC development effort, Sergey
@ -825,7 +825,8 @@ ERC 4.0 was released.
@item 2005 @item 2005
ERC 5.0 was released. Michael Olson @email{mwolson@@gnu.org} became @c mwolson@@gnu.org
ERC 5.0 was released. Michael Olson became
the release manager and eventually the maintainer. the release manager and eventually the maintainer.
After some discussion between him and the Emacs developers, it was After some discussion between him and the Emacs developers, it was

View File

@ -819,16 +819,18 @@ Eshell module.} You also need to load the following as shown:
@cindex known bugs @cindex known bugs
@cindex bugs, known @cindex bugs, known
If you find a bug or misfeature, don't hesitate to let me know! Send If you find a bug or misfeature, don't hesitate to report it, by
email to @email{johnw@@gnu.org}. Feature requests should also be sent using @kbd{M-x report-emacs-bug}. The same applies to feature requests.
there. I prefer discussing one thing at a time. If you find several It is best to discuss one thing at a time. If you find several
unrelated bugs, please report them separately. unrelated bugs, please report them separately.
@ignore
If you have ideas for improvements, or if you have written some If you have ideas for improvements, or if you have written some
extensions to this package, I would like to hear from you. I hope you extensions to this package, I would like to hear from you. I hope you
find this package useful! find this package useful!
@end ignore
Below is a complete list of known problems with Eshell version 2.4.2, Below is a list of some known problems with Eshell version 2.4.2,
which is the version included with Emacs 22. which is the version included with Emacs 22.
@table @asis @table @asis

View File

@ -444,9 +444,9 @@ mail-to-news gateway).
The correct way to report Emacs bugs is to use the command The correct way to report Emacs bugs is to use the command
@kbd{M-x report-emacs-bug}. It sets up a mail buffer with the @kbd{M-x report-emacs-bug}. It sets up a mail buffer with the
essential information and the correct e-mail address, which is essential information and the correct e-mail address,
@email{bug-gnu-emacs@@gnu.org} for the released versions of Emacs. @email{bug-gnu-emacs@@gnu.org}.
Anything sent to @email{bug-gnu-emacs@@gnu.org} also appears in the Anything sent there also appears in the
newsgroup @uref{news:gnu.emacs.bug}, but please use e-mail instead of newsgroup @uref{news:gnu.emacs.bug}, but please use e-mail instead of
news to submit the bug report. This ensures a reliable return address news to submit the bug report. This ensures a reliable return address
so you can be contacted for further details. so you can be contacted for further details.
@ -459,13 +459,17 @@ report (@pxref{Bugs, , Reporting Bugs, emacs, The GNU Emacs Manual}).
RMS says: RMS says:
@quotation @quotation
Sending bug reports to @email{help-gnu-emacs@@gnu.org} (which has the Sending bug reports to
effect of posting on @uref{news:gnu.emacs.help}) is undesirable because @url{http://lists.gnu.org/mailman/listinfo/help-gnu-emacs,
it takes the time of an unnecessarily large group of people, most of the help-gnu-emacs mailing list}
whom are just users and have no idea how to fix these problem. (which has the effect of posting on @uref{news:gnu.emacs.help}) is
@email{bug-gnu-emacs@@gnu.org} reaches a much smaller group of people undesirable because it takes the time of an unnecessarily large group
who are more likely to know what to do and have expressed a wish to of people, most of whom are just users and have no idea how to fix
receive more messages about Emacs than the others. these problem.
@url{http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs, The
bug-gnu-emacs list} reaches a much smaller group of people who are
more likely to know what to do and have expressed a wish to receive
more messages about Emacs than the others.
@end quotation @end quotation
RMS says it is sometimes fine to post to @uref{news:gnu.emacs.help}: RMS says it is sometimes fine to post to @uref{news:gnu.emacs.help}:
@ -960,7 +964,8 @@ by RMS for the editor TECO (Text Editor and COrrector, originally Tape
Editor and COrrector) under ITS (the Incompatible Timesharing System) on Editor and COrrector) under ITS (the Incompatible Timesharing System) on
a PDP-10. RMS had already extended TECO with a ``real-time'' a PDP-10. RMS had already extended TECO with a ``real-time''
full-screen mode with reprogrammable keys. Emacs was started by full-screen mode with reprogrammable keys. Emacs was started by
@email{gls@@east.sun.com, Guy Steele} as a project to unify the many @c gls@@east.sun.com
Guy Steele as a project to unify the many
divergent TECO command sets and key bindings at MIT, and completed by divergent TECO command sets and key bindings at MIT, and completed by
RMS. RMS.
@ -1340,7 +1345,9 @@ of files from Macintosh, Microsoft, and Unix platforms.
In general, new Emacs users should not be provided with @file{.emacs} In general, new Emacs users should not be provided with @file{.emacs}
files, because this can cause confusing non-standard behavior. Then files, because this can cause confusing non-standard behavior. Then
they send questions to @email{help-gnu-emacs@@gnu.org} asking why Emacs they send questions to
@url{http://lists.gnu.org/mailman/listinfo/help-gnu-emacs,
the help-gnu-emacs mailing list} asking why Emacs
isn't behaving as documented. isn't behaving as documented.
Emacs includes the Customize facility (@pxref{Using Customize}). This Emacs includes the Customize facility (@pxref{Using Customize}). This
@ -1805,7 +1812,8 @@ requested by @code{emacsclient}, Emacs will switch to it; otherwise
@cindex @code{gnuserv} @cindex @code{gnuserv}
There is an alternative version of @samp{emacsclient} called There is an alternative version of @samp{emacsclient} called
@samp{gnuserv}, written by @email{ange@@hplb.hpl.hp.com, Andy Norman} @c ange@@hplb.hpl.hp.com
@samp{gnuserv}, written by Andy Norman
(@pxref{Packages that do not come with Emacs}). @samp{gnuserv} uses (@pxref{Packages that do not come with Emacs}). @samp{gnuserv} uses
Internet domain sockets, so it can work across most network connections. Internet domain sockets, so it can work across most network connections.
@ -1973,7 +1981,8 @@ On some systems, @key{Insert} toggles @code{overwrite-mode} on and off.
@cindex Visible bell @cindex Visible bell
@cindex Bell, visible @cindex Bell, visible
@email{martin@@cc.gatech.edu, Martin R. Frank} writes: @c martin@@cc.gatech.edu
Martin R. Frank writes:
Tell Emacs to use the @dfn{visible bell} instead of the audible bell, Tell Emacs to use the @dfn{visible bell} instead of the audible bell,
and set the visible bell to nothing. and set the visible bell to nothing.
@ -3304,7 +3313,7 @@ to get more details about the features that it offers, and then if you
wish, Emacs can download and automatically install it for you. wish, Emacs can download and automatically install it for you.
@uref{http://www.damtp.cam.ac.uk/user/sje30/emacs/ell.html, The Emacs Lisp @uref{http://www.damtp.cam.ac.uk/user/sje30/emacs/ell.html, The Emacs Lisp
List (ELL)}, maintained by @email{S.J.Eglen@@damtp.cam.ac.uk, Stephen Eglen}, List (ELL)}, maintained by Stephen Eglen,
aims to provide one compact list with links to all of the current Emacs aims to provide one compact list with links to all of the current Emacs
Lisp files on the Internet. The ELL can be browsed over the web, or Lisp files on the Internet. The ELL can be browsed over the web, or
from Emacs with @uref{http://www.damtp.cam.ac.uk/user/sje30/emacs/ell.el, from Emacs with @uref{http://www.damtp.cam.ac.uk/user/sje30/emacs/ell.el,
@ -4313,7 +4322,8 @@ these systems, you should configure @code{movemail} to use @code{flock}.
@cindex Sender, replying only to @cindex Sender, replying only to
@cindex Rmail, replying to the sender of a message in @cindex Rmail, replying to the sender of a message in
@email{isaacson@@seas.upenn.edu, Ron Isaacson} says: When you hit @c isaacson@@seas.upenn.edu
Ron Isaacson says: When you hit
@key{r} to reply in Rmail, by default it CCs all of the original @key{r} to reply in Rmail, by default it CCs all of the original
recipients (everyone on the original @samp{To} and @samp{CC} recipients (everyone on the original @samp{To} and @samp{CC}
lists). With a prefix argument (i.e., typing @kbd{C-u} before @key{r}), lists). With a prefix argument (i.e., typing @kbd{C-u} before @key{r}),

View File

@ -172,17 +172,20 @@ Per Cederqvist wrote most of the otherwise unattributed functions in
PCL-CVS as well as all the documentation. PCL-CVS as well as all the documentation.
@item @item
@email{inge@@lysator.liu.se, Inge Wallin} wrote the skeleton of @c inge@@lysator.liu.se
Inge Wallin wrote the skeleton of
@file{pcl-cvs.texi}, and gave useful comments on it. He also wrote @file{pcl-cvs.texi}, and gave useful comments on it. He also wrote
the files @file{elib-node.el} and @file{compile-all.el}. The file the files @file{elib-node.el} and @file{compile-all.el}. The file
@file{cookie.el} was inspired by Inge.@refill @file{cookie.el} was inspired by Inge.@refill
@item @item
@email{linus@@lysator.liu.se, Linus Tolke} contributed useful comments @c linus@@lysator.liu.se
Linus Tolke contributed useful comments
on both the functionality and the documentation.@refill on both the functionality and the documentation.@refill
@item @item
@email{jwz@@jwz.com, Jamie Zawinski} contributed @c jwz@@jwz.com
Jamie Zawinski contributed
@file{pcl-cvs-lucid.el}, which was later renamed to @file{pcl-cvs-lucid.el}, which was later renamed to
@file{pcl-cvs-xemacs.el}.@refill @file{pcl-cvs-xemacs.el}.@refill
@ -191,34 +194,40 @@ Leif Lonnblad contributed RCVS support (since superseded by the new
remote CVS support). remote CVS support).
@item @item
@email{jimb@@cyclic.com, Jim Blandy} contributed hooks to automatically @c jimb@@cyclic.com
Jim Blandy contributed hooks to automatically
guess CVS log entries from @file{ChangeLog} contents, and initial support of guess CVS log entries from @file{ChangeLog} contents, and initial support of
the new Cygnus / Cyclic remote CVS, as well as various sundry bug fixes the new Cygnus / Cyclic remote CVS, as well as various sundry bug fixes
and cleanups. and cleanups.
@item @item
@email{kingdon@@cyclic.com, Jim Kingdon} contributed lots of fixes to @c kingdon@@cyclic.com
Jim Kingdon contributed lots of fixes to
the build and installation procedure. the build and installation procedure.
@item @item
@email{woods@@weird.com, Greg A. Woods} contributed code to implement @c woods@@weird.com
Greg A. Woods contributed code to implement
the use of per-file diff buffers, and vendor join diffs with emerge and the use of per-file diff buffers, and vendor join diffs with emerge and
ediff, as well as various and sundry bug fixes and cleanups. ediff, as well as various and sundry bug fixes and cleanups.
@item @item
@email{greg.klanderman@@alum.mit.edu, Greg Klanderman} implemented @c greg.klanderman@@alum.mit.edu
Greg Klanderman implemented
toggling of marked files, setting of CVS command flags via prefix toggling of marked files, setting of CVS command flags via prefix
arguments, updated the XEmacs support, updated the manual, and fixed arguments, updated the XEmacs support, updated the manual, and fixed
numerous bugs. numerous bugs.
@item @item
@email{monnier@@gnu.org, Stefan Monnier} added a slew of other @c monnier@@gnu.org
Stefan Monnier added a slew of other
features and introduced even more new bugs. If there's any bug left, features and introduced even more new bugs. If there's any bug left,
you can be sure it's his. you can be sure it's his.
@item @item
@c wordy to avoid an underfull hbox @c wordy to avoid an underfull hbox
@email{masata-y@@is.aist-nara.ac.jp, Masatake YAMATO} made a gracious @c masata-y@@is.aist-nara.ac.jp
Masatake YAMATO made a gracious
contribution of his cvstree code to display a tree of tags which was later contribution of his cvstree code to display a tree of tags which was later
superseded by the new @code{cvs-status-mode}. superseded by the new @code{cvs-status-mode}.
@end itemize @end itemize
@ -1369,18 +1378,19 @@ Used to highlight CVS messages.
@cindex FAQ @cindex FAQ
@cindex Problems, list of common @cindex Problems, list of common
If you find a bug or misfeature, don't hesitate to tell us! Send email If you find a bug or misfeature, don't hesitate to tell us!
to @email{bug-gnu-emacs@@gnu.org} which is gatewayed to the newsgroup Use @kbd{M-x report-emacs-bug} to send us a report.
@samp{gnu.emacs.bugs}. Feature requests should also be sent there. We You can follow the same process for feature requests.
prefer discussing one thing at a time. If you find several unrelated We prefer discussing one thing at a time. If you find several unrelated
bugs, please report them separately. If you are running PCL-CVS under bugs, please report them separately. If you are running PCL-CVS under
XEmacs, you should also send a copy of bug reports to XEmacs, you should also send a copy of bug reports to
@email{xemacs-beta@@xemacs.org}. the @url{http://lists.xemacs.org/mailman/listinfo/xemacs-beta,
XEmacs mailing list}.
If you have problems using PCL-CVS or other questions, send them to If you have problems using PCL-CVS or other questions, send them to
@email{help-gnu-emacs@@gnu.org}, which is gatewayed to the the @url{http://lists.gnu.org/mailman/listinfo/help-gnu-emacs,
@samp{gnu.emacs.help} newsgroup. This is a good place to get help, as help-gnu-emacs mailing list}. This is a good place to get help, as is
is @email{cvs-info@@gnu.org}, gatewayed to @samp{gnu.cvs.help}. the @url{http://lists.nongnu.org/mailman/listinfo/info-cvs, info-cvs list}.
If you have ideas for improvements, or if you have written some If you have ideas for improvements, or if you have written some
extensions to this package, we would like to hear from you. We hope that extensions to this package, we would like to hear from you. We hope that

View File

@ -3639,8 +3639,8 @@ With @i{Viper} mode prior to Vipers version 3.01, you need to protect
@cindex @code{http}, @RefTeX{} home page @cindex @code{http}, @RefTeX{} home page
@cindex @code{ftp}, @RefTeX{} site @cindex @code{ftp}, @RefTeX{} site
@RefTeX{} was written by @i{Carsten Dominik} @c dominik@@science.uva.nl
@email{dominik@@science.uva.nl}, with contributions by @i{Stephen @RefTeX{} was written by @i{Carsten Dominik}, with contributions by @i{Stephen
Eglen}. @RefTeX{} is currently maintained by @value{MAINTAINER}, see Eglen}. @RefTeX{} is currently maintained by @value{MAINTAINER}, see
the @value{MAINTAINERSITE} for detailed information. the @value{MAINTAINERSITE} for detailed information.

View File

@ -60,7 +60,7 @@ by formulas that can refer to the values of other cells.
@end display @end display
@end ifnottex @end ifnottex
To report bugs, send email to @email{jyavner@@member.fsf.org}. To report bugs, use @kbd{M-x report-emacs-bug}.
@insertcopying @insertcopying
@ -997,39 +997,62 @@ cell.
Coding by: Coding by:
@quotation @quotation
Jonathan Yavner @email{jyavner@@member.fsf.org}@* @c jyavner@@member.fsf.org
Stefan Monnier @email{monnier@@gnu.org}@* Jonathan Yavner,
Shigeru Fukaya @email{shigeru.fukaya@@gmail.com} @c monnier@@gnu.org
Stefan Monnier,
@c shigeru.fukaya@@gmail.com
Shigeru Fukaya
@end quotation @end quotation
@noindent @noindent
Texinfo manual by: Texinfo manual by:
@quotation @quotation
Jonathan Yavner @email{jyavner@@member.fsf.org}@* @c jyavner@@member.fsf.org
Brad Collins <brad@@chenla.org> Jonathan Yavner,
@c brad@@chenla.org
Brad Collins
@end quotation @end quotation
@noindent @noindent
Ideas from: Ideas from:
@quotation @quotation
Christoph Conrad @email{christoph.conrad@@gmx.de}@* @c christoph.conrad@@gmx.de
CyberBob @email{cyberbob@@redneck.gacracker.org}@* Christoph Conrad,
Syver Enstad @email{syver-en@@online.no}@* @c cyberbob@@redneck.gacracker.org
Ami Fischman @email{fischman@@zion.bpnetworks.com}@* CyberBob,
Thomas Gehrlein @email{Thomas.Gehrlein@@t-online.de}@* @c syver-en@@online.no
Chris F.A. Johnson @email{c.f.a.johnson@@rogers.com}@* Syver Enstad,
Yusong Li @email{lyusong@@hotmail.com}@* @c fischman@@zion.bpnetworks.com
Juri Linkov @email{juri@@jurta.org}@* Ami Fischman,
Harald Maier @email{maierh@@myself.com}@* @c Thomas.Gehrlein@@t-online.de
Alan Nash @email{anash@@san.rr.com}@* Thomas Gehrlein,
François Pinard @email{pinard@@iro.umontreal.ca}@* @c c.f.a.johnson@@rogers.com
Pedro Pinto @email{ppinto@@cs.cmu.edu}@* Chris F.A. Johnson,
Stefan Reichör @email{xsteve@@riic.at}@* @c lyusong@@hotmail.com
Oliver Scholz @email{epameinondas@@gmx.de}@* Yusong Li,
Richard M. Stallman @email{rms@@gnu.org}@* @c juri@@jurta.org
Luc Teirlinck @email{teirllm@@dms.auburn.edu}@* Juri Linkov,
J. Otto Tennant @email{jotto@@pobox.com}@* @c maierh@@myself.com
Jean-Philippe Theberge @email{jphil@@acs.pagesjaunes.fr} Harald Maier,
@c anash@@san.rr.com
Alan Nash,
@c pinard@@iro.umontreal.ca
François Pinard,
@c ppinto@@cs.cmu.edu
Pedro Pinto,
@c xsteve@@riic.at
Stefan Reichör,
@c epameinondas@@gmx.de
Oliver Scholz,
@c rms@@gnu.org
Richard M. Stallman,
@c teirllm@@dms.auburn.edu
Luc Teirlinck,
@c jotto@@pobox.com
J. Otto Tennant,
@c jphil@@acs.pagesjaunes.fr
Jean-Philippe Theberge
@end quotation @end quotation
@c =================================================================== @c ===================================================================

View File

@ -105,10 +105,7 @@ version of Emacs. It was developed primarily on various versions of
Microsoft Windows, but has also been tested on MS-DOS, and various Microsoft Windows, but has also been tested on MS-DOS, and various
versions of UNIX and GNU/Linux. versions of UNIX and GNU/Linux.
WoMan is distributed with GNU Emacs. In addition, the current source WoMan is distributed with GNU Emacs.
code and documentation files are available from
@uref{http://centaur.maths.qmw.ac.uk/Emacs/WoMan/, the WoMan web
server}.
WoMan implements a subset of the formatting performed by the Emacs WoMan implements a subset of the formatting performed by the Emacs
@code{man} (or @code{manual-entry}) command to format a Unix-style @code{man} (or @code{manual-entry}) command to format a Unix-style
@ -148,11 +145,7 @@ which begin with the prefix @code{woman-} (or occasionally
either running the command @code{woman-mini-help} or selecting the WoMan either running the command @code{woman-mini-help} or selecting the WoMan
menu option @samp{Mini Help}. menu option @samp{Mini Help}.
WoMan is (of course) still under development! Please Guidance on reporting bugs is given below. @xref{Bugs, , Reporting Bugs}.
@email{F.J.Wright@@qmw.ac.uk, let me know} what doesn't work---I am
adding and improving functionality as testing shows that it is
necessary. Guidance on reporting bugs is given below. @xref{Bugs, ,
Reporting Bugs}.
@c =================================================================== @c ===================================================================
@ -276,6 +269,7 @@ of the facilities implemented in the Emacs @code{man} library. WoMan
and man can happily co-exist, which is very useful for comparison and and man can happily co-exist, which is very useful for comparison and
debugging purposes. debugging purposes.
@ignore
@code{nroff} simulates non-@acronym{ASCII} characters by using one or more @code{nroff} simulates non-@acronym{ASCII} characters by using one or more
@acronym{ASCII} characters. WoMan should be able to do much better than @acronym{ASCII} characters. WoMan should be able to do much better than
this. I have recently begun to add support for WoMan to use more of the this. I have recently begun to add support for WoMan to use more of the
@ -284,6 +278,7 @@ aspect that I intend to develop further in the near future. It should
be possible to move WoMan from an emulation of @code{nroff} to an be possible to move WoMan from an emulation of @code{nroff} to an
emulation of @code{troff} as GNU Emacs moves to providing bit-mapped emulation of @code{troff} as GNU Emacs moves to providing bit-mapped
display facilities. display facilities.
@end ignore
@node Finding @node Finding
@chapter Finding and Formatting Man Pages @chapter Finding and Formatting Man Pages
@ -1290,8 +1285,8 @@ try the latest version of @file{woman.el} from the Emacs repository
on @uref{http://savannah.gnu.org/projects/emacs/}. If it still fails, please on @uref{http://savannah.gnu.org/projects/emacs/}. If it still fails, please
@item @item
send a bug report to @email{bug-gnu-emacs@@gnu.org} and to use @kbd{M-x report-emacs-bug} to send a bug report.
@email{F.J.Wright@@qmw.ac.uk}. Please include the entry from the Please include the entry from the
@code{*WoMan-Log*} buffer relating to the problem file, together with @code{*WoMan-Log*} buffer relating to the problem file, together with
a brief description of the problem. Please indicate where you got the a brief description of the problem. Please indicate where you got the
man source file from, but do not send it unless asked to send it. man source file from, but do not send it unless asked to send it.
@ -1310,43 +1305,80 @@ I also thank the following for helpful suggestions, bug reports, code
fragments, general interest, etc.: fragments, general interest, etc.:
@quotation @quotation
Jari Aalto, @email{jari.aalto@@cs.tpu.fi}@* @c jari.aalto@@cs.tpu.fi
Dean Andrews, @email{dean@@dra.com}@* Jari Aalto,
Juanma Barranquero, @email{barranquero@@laley-actualidad.es}@* @c dean@@dra.com
Karl Berry, @email{kb@@cs.umb.edu}@* Dean Andrews,
Jim Chapman, @email{jchapman@@netcomuk.co.uk}@* @c barranquero@@laley-actualidad.es
Frederic Corne, @email{frederic.corne@@erli.fr}@* Juanma Barranquero,
Peter Craft, @email{craft@@alacritech.com}@* @c kb@@cs.umb.edu
Charles Curley, @email{ccurley@@trib.com}@* Karl Berry,
Jim Davidson, @email{jdavidso@@teknowledge.com}@* @c jchapman@@netcomuk.co.uk
Kevin D'Elia, @email{Kevin.DElia@@mci.com}@* Jim Chapman,
John Fitch, @email{jpff@@maths.bath.ac.uk}@* @c frederic.corne@@erli.fr
Hans Frosch, @email{jwfrosch@@rish.b17c.ingr.com}@* Frederic Corne,
Guy Gascoigne-Piggford, @email{ggp@@informix.com}@* @c craft@@alacritech.com
Brian Gorka, @email{gorkab@@sanchez.com}@* Peter Craft,
Nicolai Henriksen, @email{nhe@@lyngso-industri.dk}@* @c ccurley@@trib.com
Thomas Herchenroeder, @email{the@@software-ag.de}@* Charles Curley,
Alexander Hinds, @email{ahinds@@thegrid.net}@* @c jdavidso@@teknowledge.com
Stefan Hornburg, @email{sth@@hacon.de}@* Jim Davidson,
Theodore Jump, @email{tjump@@cais.com}@* @c Kevin.DElia@@mci.com
Paul Kinnucan, @email{paulk@@mathworks.com}@* Kevin D'Elia,
Jonas Linde, @email{jonas@@init.se}@* @c jpff@@maths.bath.ac.uk
Andrew McRae, @email{andrewm@@optimation.co.nz}@* John Fitch,
Howard Melman, @email{howard@@silverstream.com}@* @c jwfrosch@@rish.b17c.ingr.com
Dennis Pixton, @email{dennis@@math.binghamton.edu}@* Hans Frosch,
T. V. Raman, @email{raman@@Adobe.com}@* @c ggp@@informix.com
Bruce Ravel, @email{bruce.ravel@@nist.gov}@* Guy Gascoigne-Piggford,
Benjamin Riefenstahl, @email{benny@@crocodial.de}@* @c gorkab@@sanchez.com
Kevin Ruland, @email{kruland@@seistl.com}@* Brian Gorka,
Tom Schutter, @email{tom@@platte.com}@* @c nhe@@lyngso-industri.dk
Wei-Xue Shi, @email{wxshi@@ma.neweb.ne.jp}@* Nicolai Henriksen,
Fabio Somenzi, @email{fabio@@joplin.colorado.edu}@* @c the@@software-ag.de
Karel Sprenger, @email{ks@@ic.uva.nl}@* Thomas Herchenroeder,
Chris Szurgot, @email{szurgot@@itribe.net}@* @c ahinds@@thegrid.net
Paul A. Thompson, @email{pat@@po.cwru.edu}@* Alexander Hinds,
Arrigo Triulzi, @email{arrigo@@maths.qmw.ac.uk}@* @c sth@@hacon.de
Geoff Voelker, @email{voelker@@cs.washington.edu}@* Stefan Hornburg,
Eli Zaretskii, @email{eliz@@is.elta.co.il} @c tjump@@cais.com
Theodore Jump,
@c paulk@@mathworks.com
Paul Kinnucan,
@c jonas@@init.se
Jonas Linde,
@c andrewm@@optimation.co.nz
Andrew McRae,
@c howard@@silverstream.com
Howard Melman,
@c dennis@@math.binghamton.edu
Dennis Pixton,
@c raman@@Adobe.com
T. V. Raman,
@c bruce.ravel@@nist.gov
Bruce Ravel,
@c benny@@crocodial.de
Benjamin Riefenstahl,
@c kruland@@seistl.com
Kevin Ruland,
@c tom@@platte.com
Tom Schutter,
@c wxshi@@ma.neweb.ne.jp
Wei-Xue Shi,
@c fabio@@joplin.colorado.edu
Fabio Somenzi,
@c ks@@ic.uva.nl
Karel Sprenger,
@c szurgot@@itribe.net
Chris Szurgot,
@c pat@@po.cwru.edu
Paul A. Thompson,
@c arrigo@@maths.qmw.ac.uk
Arrigo Triulzi,
@c voelker@@cs.washington.edu
Geoff Voelker,
@c eliz@@is.elta.co.il
Eli Zaretskii
@end quotation @end quotation
@c =================================================================== @c ===================================================================

View File

@ -1,3 +1,7 @@
2013-07-25 Glenn Morris <rgm@gnu.org>
* dired-x.el (dired-mark-extension): Convert comment to doc string.
2013-07-25 Juanma Barranquero <lekktu@gmail.com> 2013-07-25 Juanma Barranquero <lekktu@gmail.com>
* desktop.el (desktop--make-frame): Do not pass the `fullscreen' * desktop.el (desktop--make-frame): Do not pass the `fullscreen'

View File

@ -331,9 +331,9 @@ See also the functions:
;; Mark files with some extension. ;; Mark files with some extension.
(defun dired-mark-extension (extension &optional marker-char) (defun dired-mark-extension (extension &optional marker-char)
"Mark all files with a certain EXTENSION for use in later commands. "Mark all files with a certain EXTENSION for use in later commands.
A `.' is *not* automatically prepended to the string entered." A `.' is *not* automatically prepended to the string entered.
;; EXTENSION may also be a list of extensions instead of a single one. EXTENSION may also be a list of extensions instead of a single one.
;; Optional MARKER-CHAR is marker to use. Optional MARKER-CHAR is marker to use."
(interactive "sMarking extension: \nP") (interactive "sMarking extension: \nP")
(or (listp extension) (or (listp extension)
(setq extension (list extension))) (setq extension (list extension)))