unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 358@debbugs.gnu.org
Subject: bug#358: dabbrev-abbrev-char-regexp
Date: Thu, 23 Mar 2017 13:24:19 -0700 (PDT)	[thread overview]
Message-ID: <5e7a0ecf-0410-4080-9553-11e3da1361ba@default> (raw)
In-Reply-To: <CAM-tV--4R5B_VdcdMR4g3B83PPw9Ux3q=2vqEu7+YkYOPYq3Dw@mail.gmail.com>

> >> +For instance, if you are programming in Lisp, `yes-or-no-p' is a
> >> +symbol, while `yes', `or', `no' and `p' are considered words.
> >
> > This text (same as before) is a bit misleading.  It makes it sound
> > like `yes', `or', `no', and `p' are considered words but not symbols.
> > They are also considered symbols.  Each of their characters has word
> > syntax, but in Lisp those names name symbols.
> >
> > It is better not to talk about Lisp symbols at all here, I think.
> > This is about the syntax categories symbol and word.  It is not
> > about which names can be used for Lisp symbols.  (And there is
> > no such thing as a Lisp "word".)
> 
> The text is using "symbol" as a shorthand for "text which
> `forward-symbol' would move over" or "sequence of characters with word
> or symbol constituent syntax", and "word" as short for "text which
> `forward-word' would move over" or "sequence of characters with word
> constituent syntax".

Yes, that's the intended meaning.  Which is why it should not
mention Lisp symbols, which are something else again.

> I think it's reasonably clear from context (as
> you say, there is no such thing as a Lisp "word" in any other sense),
> but I have no problem replacing it with something less ambiguous if
> you can come up with something that's not too long.

I don't think any example is needed.  Essentially we are saying
here that if a letter has word syntax and `-' has symbol syntax
then \"\\\\sw\" matches a word char and \"\\\\sw\\\\|\\\\s_\"
matches a word char or a symbol char.  Not worth saying, IMO.





  reply	other threads:[~2017-03-23 20:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 13:30 bug#358: dabbrev-abbrev-char-regexp Otto Maddox
2008-10-14  1:07 ` Glenn Morris
2008-10-23  1:28   ` Glenn Morris
2011-07-06 17:46     ` Lars Magne Ingebrigtsen
2017-03-23 18:28 ` Noam Postavsky
2017-03-23 19:42   ` Drew Adams
2017-03-23 20:07     ` Noam Postavsky
2017-03-23 20:24       ` Drew Adams [this message]
2017-03-23 20:50         ` Noam Postavsky
2017-03-23 20:58           ` Drew Adams
2017-03-23 21:37             ` Noam Postavsky
2017-03-23 21:49               ` Drew Adams
2017-03-24 15:19                 ` Noam Postavsky
2017-03-26 13:25                   ` npostavs

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=5e7a0ecf-0410-4080-9553-11e3da1361ba@default \
    --to=drew.adams@oracle.com \
    --cc=358@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).