From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 9233@debbugs.gnu.org
Subject: bug#9233: Small error in Elisp manual
Date: Sun, 11 Sep 2011 04:04:32 +0200 [thread overview]
Message-ID: <m3vcsz7s27.fsf@stories.gnus.org> (raw)
In-Reply-To: <CAAeL0STvqGXvB8LWBvT9q7YwG_c_t3JAxCQjvm8CiZ0QrCKenQ@mail.gmail.com> (Juanma Barranquero's message of "Thu, 4 Aug 2011 02:14:13 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> It should instead say something like: "The server's process buffer
> value is never used directly, but the log function can retrieve it and
> use it to log connections by inserting text there."
Ok; I've now installed this.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2011-09-11 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 0:14 bug#9233: Small error in Elisp manual Juanma Barranquero
2011-09-11 2:04 ` Lars Magne Ingebrigtsen [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3vcsz7s27.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=9233@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).