From: Juanma Barranquero <lekktu@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: 21766@debbugs.gnu.org, Markus Triska <triska@metalevel.at>
Subject: bug#21766: 25.0.50; delete-trailing-whitespace sometimes deletes non-whitespace
Date: Tue, 27 Oct 2015 10:16:28 +0100 [thread overview]
Message-ID: <CAAeL0SS+SHEA=bqH4aTf6WfzzvcmRXkZ8djypAHG5jckCJVZdg@mail.gmail.com> (raw)
In-Reply-To: <mvm611shegz.fsf@hawking.suse.de>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
On Tue, Oct 27, 2015 at 10:01 AM, Andreas Schwab <schwab@suse.de> wrote:
> No, skip-syntax-backward is safe. There must be something in
> line-beginning-position that does this, but only indirectly.
(skip-syntax-backward "-"
(save-match-data
(line-beginning-position)))
still shows the bug, while
(save-match-data
(skip-syntax-backward "-" (line-beginning-position)))
fixes it.
[-- Attachment #2: Type: text/html, Size: 776 bytes --]
next prev parent reply other threads:[~2015-10-27 9:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 23:07 bug#21766: 25.0.50; delete-trailing-whitespace sometimes deletes non-whitespace Markus Triska
2015-10-27 0:15 ` Juanma Barranquero
2015-10-27 7:07 ` Andreas Röhler
2015-10-27 7:53 ` Juanma Barranquero
2015-10-27 8:05 ` martin rudalics
2015-10-27 8:12 ` Juanma Barranquero
2015-10-27 8:25 ` martin rudalics
2015-10-27 8:32 ` Juanma Barranquero
2015-10-27 9:01 ` Andreas Schwab
2015-10-27 9:16 ` Juanma Barranquero [this message]
2015-10-27 9:24 ` martin rudalics
2015-10-27 9:46 ` Andreas Schwab
2015-10-27 10:21 ` Juanma Barranquero
2015-10-27 16:03 ` Juanma Barranquero
2015-10-28 1:51 ` Stephen Leake
2015-10-28 9:08 ` Juanma Barranquero
2015-10-28 9:08 ` Juanma Barranquero
2015-10-28 17:38 ` Juanma Barranquero
2015-10-28 1:51 ` Stephen Leake
2015-10-27 16:03 ` Juanma Barranquero
2015-10-28 19:19 ` Stefan Monnier
2015-10-29 6:30 ` Andreas Röhler
2015-10-29 9:41 ` Juanma Barranquero
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAeL0SS+SHEA=bqH4aTf6WfzzvcmRXkZ8djypAHG5jckCJVZdg@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=21766@debbugs.gnu.org \
--cc=schwab@suse.de \
--cc=triska@metalevel.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.