unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: 14087@debbugs.gnu.org
Subject: bug#14087: [PATCH] Some fixes for refcard.tex
Date: Thu, 09 May 2013 02:21:26 -0400	[thread overview]
Message-ID: <sky5bo65cp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAF+z6Fs2ArZRgvjdgXb3u+jPb+PzU4wZEjZ6SwskO4DpaXqtw@mail.gmail.com> (Xue Fuqiao's message of "Thu, 9 May 2013 12:59:46 +0800")

Xue Fuqiao wrote:

> (Sorry, but I cannot configure my email client to use `X-Debbugs-CC'.)

i) That option only affects new reports, not replies to existing
reports, so I don't see the relevance.

ii) I guess your mail client doesn't let you add X- headers.
Well, you can put it in the first line of the body instead.
No, it probably isn't in the documentation.

>>> ! \key{eval {\bf sexp} before point}{C-x C-e} % sexp?  form?  expression?  S-expression?
>>
>> sexp seems fine for a quick reference card.
>
> In (info "(elisp) Intro Eval"):
>
>     A Lisp object that is intended for evaluation is called a "form" or
>   "expression".
> [...]
>     It is sometimes also referred to as an "S-expression" or "sexp",
>   but we generally do not use this terminology in this manual.
>
> IMO we can use "form" here since it is consistent with the manual and
> not too long.

A reference card is not a manual.
The command is "eval-last-sexp"; "Evaluate sexp before point".
Using the word "sexp" will therefore be confusing to literally no-one,
and has added mnemonic value wrt the command-name.
There is no need to change it.





  reply	other threads:[~2013-05-09  6:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29  9:02 bug#14087: [PATCH] Some fixes for refcard.tex Xue Fuqiao
2013-05-08 17:18 ` Glenn Morris
2013-05-09  4:59   ` Xue Fuqiao
2013-05-09  6:21     ` Glenn Morris [this message]
2013-05-09  8:06       ` Xue Fuqiao
2013-05-25  2:18 ` Xue Fuqiao

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=sky5bo65cp.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=14087@debbugs.gnu.org \
    --cc=xfq.free@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).