From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: bug#23794: Emacs bug #23794; sort-line behavior regressed from prior Emacs versions
Date: Sun, 19 Jun 2016 20:55:07 -0400 [thread overview]
Message-ID: <jwvoa6wadiy.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: CA+OMD9jOBhas2Bt-7rc92UdLuPxWhJj2mEAc2KLgWAVdGFaOvw@mail.gmail.com
> The problem with that approach is that each mode has to be aware of this
> and add a setting, really not much different than each mode having its own
> sort function or way of calling a sort function.
Right. To be an improvement, the setting should be one which makes
sense independently from the modes which sets it and independently from
the packages that uses the setting. I.e. one needs to get at the core
reason *why* we want this behavior in this case.
I suggest something like
`invisible-text-belongs-to-the-preceding-visible-text' (which hence
implies that if you move one, you need to move the other along with it).
Maybe a more concise name is in order, tho ;-)
Stefan
next prev parent reply other threads:[~2016-06-20 0:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 17:01 Emacs bug #23794; sort-line behavior regressed from prior Emacs versions Robert Weiner
2016-06-18 17:26 ` Eli Zaretskii
2016-06-18 17:42 ` Eli Zaretskii
2016-06-18 17:50 ` Robert Weiner
2016-06-18 18:15 ` Eli Zaretskii
2016-06-18 18:22 ` Stefan Monnier
2016-06-18 18:28 ` Eli Zaretskii
2016-06-18 18:37 ` Robert Weiner
2016-06-18 18:31 ` Robert Weiner
2016-06-18 21:28 ` Drew Adams
2016-06-18 22:41 ` Robert Weiner
2016-06-19 2:39 ` Eli Zaretskii
2016-06-19 13:31 ` Robert Weiner
2016-06-19 15:18 ` Eli Zaretskii
2016-06-19 16:12 ` Robert Weiner
2016-06-19 16:30 ` Eli Zaretskii
2016-06-19 16:51 ` bug#23794: " Robert Weiner
2016-06-19 16:55 ` Eli Zaretskii
2016-06-19 17:03 ` Robert Weiner
2016-06-19 20:59 ` Drew Adams
2016-06-20 0:55 ` Stefan Monnier [this message]
2016-06-19 18:16 ` John Wiegley
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=jwvoa6wadiy.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).