unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: oitofelix@gmail.com (Bruno Félix Rezende Ribeiro)
To: 12562@debbugs.gnu.org
Subject: bug#12562: 24.1; GNU Emacs Lisp Reference Manual; Couple comma's lack, might cause fuss; Section 12.13, "Determining whether a Function is Safe to Call"; First paragraph; First Sentence.
Date: Tue, 02 Oct 2012 16:38:16 -0300	[thread overview]
Message-ID: <87pq50aclz.fsf@gmail.com> (raw)

This bug report will be sent to the Bug-GNU-Emacs mailing list
and the GNU bug tracker at debbugs.gnu.org.  Please check that
the From: line contains a valid email address.  After a delay of up
to one day, you should receive an acknowledgement at that address.

Please write in English if possible, as the Emacs maintainers
usually do not have translators for other languages.

Please describe exactly what actions triggered the bug, and
the precise symptoms of the bug.  If you can, give a recipe
starting from `emacs -Q':

In GNU Emacs Lisp Reference Manual, Section 12.13, entitled "Determining
whether a Function is Safe to Call", in the first paragraph and first
sentence one can read:

Some major modes such as SES call functions that are stored in user
files.

I took several seconds to realize the real sentence's meaning.  It could
be due to my poor english skills, because I'm not, actually, a native
english speaker; or my trend to read very fast when there isn't
punctuation; or even the several reading hours which I submitted
myself.  Though it's clear to me the sentence has only one possible
meaning by the context, I think if the expression "such as SES" _was_ surrounded by
commas the sentence would be fairly simple to understand and that change
won't cause any harm.  For instance:

Some major modes, such as SES, call functions that are stored in user
files.

Thanks in advance.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
For information about debugging Emacs, please read the file
/share/emacs/24.1/etc/DEBUG.


In GNU Emacs 24.1.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
 of 2012-08-26 on felix-laptop
Windowing system distributor `The X.Org Foundation', version 11.0.10903000
Configured using:
 `configure 'CFLAGS=-pipe -O3 -march=atom -mtune=atom -mmmx -msse -msse2
 -msse3 -mssse3 -mfpmath=sse''

-- 
 ,= ,-_-. =.  Bruno Félix Rezende Ribeiro (oitofelix)
((_/)o o(\_)) Uns o chamam de super-vaca...
 `-'(. .)`-'  Outros de hiper-touro...
     \_/      Eu o chamo simplesmente: meta-gnu!






             reply	other threads:[~2012-10-02 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 19:38 Bruno Félix Rezende Ribeiro [this message]
2012-10-03  7:26 ` bug#12562: 24.1; GNU Emacs Lisp Reference Manual; Couple comma's lack, might cause fuss; Section 12.13, "Determining whether a Function is Safe to Call"; First paragraph; First Sentence Glenn Morris

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=87pq50aclz.fsf@gmail.com \
    --to=oitofelix@gmail.com \
    --cc=12562@debbugs.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 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).