unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: 358@debbugs.gnu.org
Subject: bug#358: dabbrev-abbrev-char-regexp
Date: Thu, 23 Mar 2017 17:37:55 -0400	[thread overview]
Message-ID: <CAM-tV-_koqkiF6tL++k-oqoCf51b+F6DFpsvKWsPmNvuT+HubA@mail.gmail.com> (raw)
In-Reply-To: <fa6f8898-227c-4a52-b48b-b07e142f9f3c@default>

On Thu, Mar 23, 2017 at 4:58 PM, Drew Adams <drew.adams@oracle.com> wrote:
>
> Of course, the problem here is that we are talking about expanding
> `yes-or-no-p', which in Lisp is a Lisp symbol.  It would probably
> be better to talk about using dabbrev in another context, besides
> Lisp.  Then it would be clearer that we are talking only about
> symbol vs word syntax.

As in, use a C example instead?

For instance, suppose the current buffer is in `c-mode'.  If this
variable is nil or \"\\\\sw\\\\|\\\\s_\", then expanding
`debug_print_in_' looks for a symbol starting with
`debug_print_in_'.  If you set this variable to \"\\\\sw\", that
expansion looks for a word prefixed with `in_' (e.g., it would
match `in_range', but not `in_close_range').  If expanding
`debug_print_in' it would look for a word starting with
`in' (e.g. `integer')."





  reply	other threads:[~2017-03-23 21:37 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
2017-03-23 20:50         ` Noam Postavsky
2017-03-23 20:58           ` Drew Adams
2017-03-23 21:37             ` Noam Postavsky [this message]
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=CAM-tV-_koqkiF6tL++k-oqoCf51b+F6DFpsvKWsPmNvuT+HubA@mail.gmail.com \
    --to=npostavs@users.sourceforge.net \
    --cc=358@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 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).