Mercurial > emacs
view etc/emacsclient.1 @ 49506:ac9e2eeeb03d
New format of AUTHORS file; list each
author name once followed by contributed and changed files.
Improve selection of entries to include in list, and generate list
of unrecognized entries indicating syntax errors in ChangeLog files.
(authors-coding-system): New variable.
(authors-many-files): Update doc string.
(authors-aliases): Change format. Now one entry with multiple
aliases per author.
(authors-valid-file-names, authors-renamed-files-alist)
(authors-renamed-files-regexps): New variables.
(authors-canonical-file-name): New function. Validates that file
exists or occurs in one of the above lists. Record unrecognized
file names in global authors-invalid-file-names list.
(authors-add): Change to record per-change counts.
(authors-canonical-author-name): Handle new format of
authors-aliases list.
(authors-scan-change-log): Rename FILE arg to LOG-FILE.
Change doc string to describe new entry format.
Only add author entries for valid file names.
(authors-print): Replace by authors-add-to-author-list.
(authors-add-to-author-list): New function which reorders
per-file entries and adds them to global authors-author-list.
(authors): Instead of authors-print to insert in *Authors* buffer,
use authors-add-to-author-list to reorder the list and then
insert result in *Authors* buffer with new format.
Generate *Authors Errors* compilation-mode buffer listing
unrecognized ChangeLog entries.
author | Kim F. Storm <storm@cua.dk> |
---|---|
date | Wed, 29 Jan 2003 00:13:11 +0000 |
parents | 3b27be508d4e |
children | 695cf19ef79e d7ddb3e565de |
line wrap: on
line source
.TH EMACSCLIENT 1 .\" NAME should be all caps, SECTION should be 1-8, maybe w/ subsection .\" other parms are allowed: see man(7), man(1) .SH NAME emacsclient \- tells a running Emacs to visit a file .SH SYNOPSIS .B emacsclient .I "[options] files ..." .SH "DESCRIPTION" This manual page documents briefly the .BR emacsclient command. This manual page was written for the Debian GNU/Linux distribution because the original program does not have a manual page. Instead, it has documentation in the GNU Info format; see below. .PP .B emacsclient works in conjunction with the built-in server of Emacs. .PP You typically do not call .B emacsclient directly. Instead, you set the environment variable EDITOR to .B emacsclient and let programs like 'vipw' or 'bug' or anything run it for you, which will use an existing Emacs to visit the file. For .B emacsclient to work, you need an already running Emacs with a server. Within Emacs, call the function `server-start'. (Your `.emacs' file can do this automatically if you add the expression `(server-start)' to it.) When you've finished editing the buffer, type `C-x #' (`server-edit'). This saves the file and sends a message back to the `emacsclient' program telling it to exit. The programs that use `EDITOR' wait for the "editor" (actually, `emacsclient') to exit. `C-x #' also checks for other pending external requests to edit various files, and selects the next such file. If you set the variable `server-window' to a window or a frame, `C-x #' displays the server buffer in that window or in that frame. .SH OPTIONS The programs follow the usual GNU command line syntax, with long options starting with two dashes (`-'). .TP .B \-n, \-\-no-wait returns immediately without waiting for you to "finish" the buffer in Emacs. .TP .B \-e, \-\-eval do not visit files but instead evaluate the arguments as Emacs Lisp expressions. .TP .B \-a, \-\-alternate-editor=EDITOR if the Emacs server is not running, run the specified editor instead. This can also be specified via the `ALTERNATE_EDITOR' environment variable. .TP .B \-d, \-\-display=DISPLAY tell the server to display the files on the given display. .SH "SEE ALSO" The program is documented fully in .IR "Using Emacs as a Server" available via the Info system. .SH BUGS If there is no running Emacs server, .B emacsclient cannot launch one. I use a small Perl script instead of raw .B emacsclient to do it (it works only with systems which have BSD sockets, which is fine for Debian GNU/Linux). .SH AUTHOR This manual page was written by Stephane Bortzmeyer <bortzmeyer@debian.org>, for the Debian GNU/Linux system (but may be used by others). .SH COPYING This manual page is in the public domain.