From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 13736@debbugs.gnu.org
Subject: bug#13736: 24.3.50; (emacs) `Editing Format Info' typos
Date: Mon, 10 Feb 2014 09:45:11 -0800 (PST) [thread overview]
Message-ID: <71492b97-9298-4541-91c3-c97463a7bffb@default> (raw)
In-Reply-To: <878utj4ff4.fsf@building.gnus.org>
> I didn't see any ... in any menus in that node. (Or any menus in
> that node.)
>
> > In node (emacs) `Editing Format Info', this is not the case, but
> > it should be.
>
> Could you include example offending and correct text?
Text Properties should be `Text Properties' (two places).
Edit should be `Edit'.
next prev parent reply other threads:[~2014-02-10 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 18:56 bug#13736: 24.3.50; (emacs) `Editing Format Info' typos Drew Adams
2014-02-10 7:04 ` Lars Ingebrigtsen
2014-02-10 17:42 ` Drew Adams
2014-02-10 17:45 ` Drew Adams [this message]
2014-02-11 6:34 ` Lars Ingebrigtsen
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=71492b97-9298-4541-91c3-c97463a7bffb@default \
--to=drew.adams@oracle.com \
--cc=13736@debbugs.gnu.org \
--cc=larsi@gnus.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 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).