From: Marcin Borkowski <mbork@mbork.pl>
To: "Simen Heggestøyl" <simenheg@gmail.com>
Cc: 19940@debbugs.gnu.org
Subject: bug#19940: 25.0.50; Infinite loop in `studlify-word' with Subword mode
Date: Sun, 03 Apr 2016 05:49:10 +0200 [thread overview]
Message-ID: <87r3enfj2h.fsf@mbork.pl> (raw)
In-Reply-To: <1424812744.9280.0@smtp.gmail.com> ("Simen Heggestøyl"'s message of "Tue, 24 Feb 2015 22:19:04 +0100")
On 2015-02-24, at 21:19, Simen Heggestøyl <simenheg@gmail.com> wrote:
> An infinite loop occurs when Subword mode is active and
>
> `studlify-word' is run on a word with more than one subword. The bug
>
>
> seems to have been introduced by changes made to subword.el in commit
>
>
> 6ddc44225e743e2b2a0d5c192f50aefd7a4a915b.
>
>
> Here is a recipe that triggers the bug, starting from emacs -Q:
>
>
> 1. Open a new buffer, and type in "subWord".
>
>
> 2. Activate Subword mode by `M-x subword-mode'.
>
>
> 3. Move point to the beginning of the line, and run `M-x
>
>
> studlify-word'.
Hi,
I can confirm this behavior on GNU Emacs 25.1.50.7 (commit 7570b35).
The problem seems to be that `studlify-region' assumes that
`forward-word' and `backward-word' will stop at non-word characters (in
the sense of the regex `\W').
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.
--
Marcin Borkowski
next prev parent reply other threads:[~2016-04-03 3:49 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 [this message]
2016-04-03 14:43 ` Eli Zaretskii
2016-04-03 16:07 ` Marcin Borkowski
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=87r3enfj2h.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=19940@debbugs.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).