unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash <pbqbqp@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 23705@debbugs.gnu.org
Subject: bug#23705: 25.0.94; Upper-case abbrev expansion doesn't work with subword-mode enabled
Date: Wed, 06 Jul 2016 12:31:09 +0430	[thread overview]
Message-ID: <8637nn19h6.fsf@gmail.com> (raw)
In-Reply-To: <qqfus3g6zz.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 23 Jun 2016 13:17:04 -0400")

> My comment is that if the OP's reaction "I'll just stop using
> subword-mode then" is a common one, then the changes to make
> subword-mode more pervasive are problematic.

By his explanation I thaught the two modes are incompatible so I gave
up! (actually I didn't think that, I just didn't want to be mean lol)

So, My situation:
I'm using mixed case abbrevs in a abbrev/tempo setup, for example (with
^ being the cursor)

"8g" expands:
struct ^

"8G" expands:
struct ^ {
    ^
};
(I have tons of these! and I'm used to them and I love 'em)

and subword-mode might have been a little help in camelCase/PascalCase
codes.

Anyway! I reported the bug/incompatiblity, so now you know!
Hope it gets fixed before 25 (if it's a bug).





  reply	other threads:[~2016-07-06  8:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06  7:18 bug#23705: 25.0.94; Upper-case abbrev expansion doesn't work with subword-mode enabled Arash
2016-06-07 21:51 ` Glenn Morris
2016-06-08  2:40   ` Eli Zaretskii
2016-06-09 15:01     ` Arash
2016-06-09 15:06       ` Eli Zaretskii
2016-06-18 18:22         ` Eli Zaretskii
2016-06-23 17:17           ` Glenn Morris
2016-07-06  8:01             ` Arash [this message]
2016-07-06 14:56               ` Eli Zaretskii
2016-07-07  1:14                 ` Arash
2016-07-07 19:58                   ` Eli Zaretskii

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=8637nn19h6.fsf@gmail.com \
    --to=pbqbqp@gmail.com \
    --cc=23705@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).