From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: oub@mat.ucm.es, emacs-devel@gnu.org
Subject: Re: sort-lines including non ASCII
Date: Thu, 07 Jul 2016 19:56:36 +0300 [thread overview]
Message-ID: <83twg1jsjf.fsf@gnu.org> (raw)
In-Reply-To: <8760shfm0u.fsf@web.de> (message from Michael Heerdegen on Thu, 07 Jul 2016 18:30:57 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
> Date: Thu, 07 Jul 2016 18:30:57 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > How do you solve the problem of different argument lists in different
> > predicates? And how do we allow to specify such an alternative
> > comparison in interactive usage?
>
> Yes, both objections are a problem indeed.
>
> > Also, if string-collate-lessp is the only additional possibility we
> > can think of, why not change sort-subr to use it "when it's TRT", as
> > we do currently when sort-subr's PREDICATE argument is nil? Making
> > sort-lines entirely open-ended like the suggestion says might be too
> > much.
>
> Yeah, I came to the same conclusion. But when exactly is "when it's
> TRT"?
Maybe if we figure out how to allow this in interactive usage, we can
pass that bit down? And if worse comes to worst, perhaps a separate
command is in order, which uses collation by default?
next prev parent reply other threads:[~2016-07-07 16:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 20:58 sort-lines including non ASCII Uwe Brauer
2016-07-05 21:57 ` Óscar Fuentes
2016-07-07 7:35 ` Uwe Brauer
2016-07-06 14:34 ` Eli Zaretskii
2016-07-06 14:52 ` Michael Heerdegen
2016-07-07 7:34 ` Uwe Brauer
2016-07-07 15:17 ` Eli Zaretskii
2016-07-07 16:30 ` Michael Heerdegen
2016-07-07 16:56 ` Eli Zaretskii [this message]
2016-07-07 17:32 ` Michael Heerdegen
2016-07-07 19:53 ` Eli Zaretskii
2016-07-07 22:55 ` Michael Heerdegen
2016-07-08 10:01 ` Eli Zaretskii
2016-07-14 21:10 ` Michael Heerdegen
2016-07-14 21:14 ` Clément Pit--Claudel
2016-07-14 21:19 ` Noam Postavsky
2016-07-14 21:26 ` Michael Heerdegen
2016-07-14 21:57 ` Noam Postavsky
2016-07-08 13:40 ` Richard Stallman
2016-07-08 14:36 ` Michael Heerdegen
2016-07-09 16:58 ` Richard Stallman
2016-07-12 23:06 ` John Wiegley
2016-07-07 7:41 ` Uwe Brauer
2016-07-07 15:20 ` Eli Zaretskii
2016-07-07 16:13 ` Uwe Brauer
2016-07-07 16:35 ` Eli Zaretskii
2016-07-07 8:23 ` Teemu Likonen
2016-07-07 15:23 ` Eli Zaretskii
2016-07-08 4:17 ` Teemu Likonen
2016-07-08 6:32 ` Eli Zaretskii
2016-07-08 6:36 ` Eli Zaretskii
2016-07-08 6:50 ` Teemu Likonen
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=83twg1jsjf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=oub@mat.ucm.es \
/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).