all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 31623@debbugs.gnu.org
Subject: bug#31623: 27.0; Elisp manual, index entry "; in comment"
Date: Tue, 29 May 2018 20:14:33 -0400	[thread overview]
Message-ID: <877enmc846.fsf@gmail.com> (raw)
In-Reply-To: <524f86f7-78e2-44a5-89fd-5df5fde0dda6@default> (Drew Adams's message of "Tue, 29 May 2018 16:47:07 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> OK, if you say so. ;-)  I was thinking more about "in"
> meaning after `comment-start'.  But yes, I guess that's
> what was intended.
>
> If that's the intention then I think it might be clearer
> if the index entry were "; outside a comment" or maybe
> "; not in a comment".

A later sentence in `(elisp) Comments' has:

    The Lisp reader discards comments; they do not become part of the
    Lisp objects which represent the program within the Lisp system.

The discarded comment includes the leading ";", so I don't think it
makes sense to treat the comment starter as being outside the comment.

> In any case, that statement is not really true: a semicolon
> does not always start a comment in Lisp whenever it is not
> within a string or a character constant.  There is also the
> case of it being escaped in a symbol name.  E.g.,
>
> (setq a\;b  42)
>
> (Dunno whether there are additional cases - perhaps not.)

I think not.  So add "unescaped"?

    In Lisp, an unescaped semicolon (`;') starts a comment if it is not
    within a string or character constant.





  reply	other threads:[~2018-05-30  0:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 14:35 bug#31623: 27.0; Elisp manual, index entry "; in comment" Drew Adams
2018-05-29 23:32 ` Noam Postavsky
2018-05-29 23:47   ` Drew Adams
2018-05-30  0:14     ` Noam Postavsky [this message]
2018-05-30  0:38       ` Drew Adams
2018-05-30  1:58         ` Noam Postavsky
2018-05-30  2:23           ` Drew Adams
2018-06-20 12:48           ` Noam Postavsky

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=877enmc846.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31623@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.