From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 358@debbugs.gnu.org
Subject: bug#358: dabbrev-abbrev-char-regexp
Date: Wed, 06 Jul 2011 19:46:23 +0200 [thread overview]
Message-ID: <m3d3hn1evk.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <sw1vy85ccg.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 22 Oct 2008 21:28:31 -0400")
Glenn Morris <rgm@gnu.org> writes:
> After looking at this again, there's still no difference between nil
> and \\sw\\|\\s- AFAICS,
I've now changed the doc string to reflect this.
> but now dabbrev--abbrev-at-point makes little
> sense to me:
>
> emacs -Q --eval '(setq dabbrev-abbrev-char-regexp "\\sw")'
>
> in scratch:
>
> yes-or-no---
>
> followed by M-/ gives
>
> "No dynamic expansion for `no---' found". Obviously, "---" are not
> word constituents, yet they are included in the abbrev, in flat
> contradiction to the doc-string of dabbrev-abbrev-char-regexp:
>
> if you set this variable to "\\sw", then expanding `yes-or-no-'
> signals an error because `-' is not part of a word
>
> This is caused by dabbrev--abbrev-at-point's:
>
> ;; If we aren't right after an abbreviation,
> ;; move point back to just after one.
> ;; This is so the user can get successive words
> ;; by typing the punctuation followed by M-/.
I have no idea how dabbrev works, but isn't that a new bug report? :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-06 17:46 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 [this message]
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
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=m3d3hn1evk.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=358@debbugs.gnu.org \
--cc=rgm@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).