From: Eli Zaretskii <eliz@gnu.org>
To: Shigeru Fukaya <shigeru.fukaya@gmail.com>
Cc: 17479-done@debbugs.gnu.org
Subject: bug#17479: 24.3.91; Doc Bug: mule.texi
Date: Mon, 12 May 2014 21:53:16 +0300 [thread overview]
Message-ID: <83sioeq15v.fsf@gnu.org> (raw)
In-Reply-To: <29CF6E10C04959shigeru.fukaya@gmail.com>
> From: Shigeru Fukaya <shigeru.fukaya@gmail.com>
> Date: Tue, 13 May 2014 03:34:04 +0900
>
> I found a documentation bug in an info file, emacs/doc/emacs/mule.texi.
>
> There is a command/phrase,
>
> @anchor{Describe Language Environment}
>
> in node `Language Environments'.
>
> It is placed at the end of a paragraph, and makes the adjacent two
> paragraphs into one that the author must not intend. Besides the
> ahchored words are referred from nowhere.
Thanks, fixed.
prev parent reply other threads:[~2014-05-12 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 18:34 bug#17479: 24.3.91; Doc Bug: mule.texi Shigeru Fukaya
2014-05-12 18:53 ` Eli Zaretskii [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=83sioeq15v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17479-done@debbugs.gnu.org \
--cc=shigeru.fukaya@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).