From: Juanma Barranquero <lektu@terra.es>
Subject: Two questions about typos in the RC
Date: Wed, 12 Feb 2003 18:04:16 +0100 [thread overview]
Message-ID: <20030212174827.5CDB.LEKTU@terra.es> (raw)
I suppose 21.3 is nearer every day, and, as I'm kinda an
Obsessive-Compulsive Berserk Typo Hunter, I really *hate* leaving around
known typos; so, I'd appreciate answers for these two questions:
1.- In allout.el, `outline-pre-command-business' has the following
incomplete docstring:
> [...] The outline-mode post-command hook will
> position a cursor that has moved as a result of such reinterpretation,
> on the destination topic's bullet, when the cursor wound up in the
> ^^^^^^
> The upshot is that you can get easy, single (ie, unmodified) key
> outline maneuvering operations by positioning the cursor on the bullet
> char. [...]
What's supposed to be there? Any idea? I neither know allout nor trust
that much my English skills...
2.- I recently fixed a bunch of typos in the trunk's lisp/ebnf-* modules
where "syntatic" was used instead of "syntactic" (I consulted with
Vinicius before making the change). I'd like to backport the fixes to RC.
Of course, the fixes to docstrings aren't likely to break anything so
these would be OK. Trouble is, the customization group name should be
changed too. I'd bet the likelihood of some code out there depending on
the name of the customization group of ebnf-*.el is ~ 0, but still,
strictly speaking that's not a bug fix, so I'd like to get a "go" before
changing it...
/L/e/k/t/u
next reply other threads:[~2003-02-12 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 17:04 Juanma Barranquero [this message]
2003-02-13 10:08 ` Two questions about typos in the RC Richard Stallman
2003-02-13 11:05 ` Juanma Barranquero
2003-02-13 18:50 ` Kevin Rodgers
2003-02-13 20:43 ` Juanma Barranquero
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=20030212174827.5CDB.LEKTU@terra.es \
--to=lektu@terra.es \
/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.