From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs/doc/lispref os.texi
Date: Mon, 14 Sep 2009 09:50:40 +0000 [thread overview]
Message-ID: <20090914095040.GA4331@muc.de> (raw)
In-Reply-To: <83bplg1t0u.fsf@gnu.org>
On Sat, Sep 12, 2009 at 11:12:01AM +0300, Eli Zaretskii wrote:
> > Date: Fri, 11 Sep 2009 20:27:50 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Subject: [Emacs-diffs] emacs/doc/lispref os.texi
> > To: emacs-diffs@gnu.org
> > Index: os.texi
> > ===================================================================
> > RCS file: /cvsroot/emacs/emacs/doc/lispref/os.texi,v
> > retrieving revision 1.29
> > retrieving revision 1.30
> > diff -u -b -r1.29 -r1.30
> > --- os.texi 10 Jul 2009 06:10:35 -0000 1.29
> > +++ os.texi 11 Sep 2009 20:27:50 -0000 1.30
> > @@ -1954,7 +1954,8 @@
> > Control characters in @var{string} have terminal-dependent effects.
> > This function operates only on text terminals. @var{terminal} may be
> > a terminal object, a frame, or @code{nil} for the selected frame's
> > -terminal.
> > +terminal. In batch mode, @var{string} is sent to stdout when
> > +@var{terminal} is @code{nil}.
> > One use of this function is to define function keys on terminals that
> > have downloadable function key definitions. For example, this is how (on
> Thanks, but please give "stdout" a @code markup, since it is a
> symbol.
DONE.
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2009-09-14 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1MmDd5-0001Ia-89@monty-python.gnu.org>
2009-09-12 8:12 ` [Emacs-diffs] emacs/doc/lispref os.texi Eli Zaretskii
2009-09-14 9:50 ` Alan Mackenzie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090914095040.GA4331@muc.de \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.