From: Marcin Borkowski <mbork@mbork.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19940@debbugs.gnu.org, simenheg@gmail.com
Subject: bug#19940: 25.0.50; Infinite loop in `studlify-word' with Subword mode
Date: Sun, 03 Apr 2016 18:07:54 +0200 [thread overview]
Message-ID: <878u0uvfol.fsf@mbork.pl> (raw)
In-Reply-To: <83fuv2rbwl.fsf@gnu.org>
On 2016-04-03, at 16:43, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Marcin Borkowski <mbork@mbork.pl>
>> Date: Sun, 03 Apr 2016 05:49:10 +0200
>> Cc: 19940@debbugs.gnu.org
>>
>> One possible solution would be to temporarily switch `subword-mode' off
>> in `studlify-region'. Given the nonsensicality of the latter, and the
>> fact that it breaks studlyCapsIdentifiers anyway, this might be the
>> preferred solution. If nobody proposes anything better, I'll tryto
>> prepare such a patch within a few days.
>
> Actually, the right solution is described in this NEWS entry:
>
> ** The new implementation of Subword mode affects word movement everywhere.
> When Subword mode is turned on, 'forward-word', 'backward-word', and
> everything that uses them will move by sub-words, effectively
> overriding the buffer's syntax table. Lisp programs that shouldn't be
> affected by Subword mode should call the new functions
> 'forward-word-strictly' and 'backward-word-strictly' instead.
>
> At the time I wrote this NEWS entry, I reviewed all the callers of
> forward/backward-word and changed those which I thought needed that; I
> guess I missed studly.el at that time. Sorry about that.
Ah, good to know. I suspected that such function would exist, but was
too lazy to actually find out - sorry!
I'll make a patch tomorrow.
> Thanks.
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2016-04-03 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 21:19 bug#19940: 25.0.50; Infinite loop in `studlify-word' with Subword mode Simen Heggestøyl
2016-04-03 3:49 ` Marcin Borkowski
2016-04-03 14:43 ` Eli Zaretskii
2016-04-03 16:07 ` Marcin Borkowski [this message]
2016-04-06 11:49 ` Marcin Borkowski
2016-04-08 7:59 ` Eli Zaretskii
2016-04-08 18:14 ` Marcin Borkowski
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=878u0uvfol.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=19940@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=simenheg@gmail.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).