From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: michael_heerdegen@web.de, 18051@debbugs.gnu.org
Subject: bug#18051: 24.3.92; ls-lisp: Sorting; make ls-lisp-string-lessp a normal function?
Date: Wed, 27 Aug 2014 18:37:01 +0300 [thread overview]
Message-ID: <83lhqaj65e.fsf@gnu.org> (raw)
In-Reply-To: <878uma2u7y.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, michael_heerdegen@web.de, 18051@debbugs.gnu.org
> Date: Wed, 27 Aug 2014 10:49:05 +0200
>
> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>
> >>> An optional argument to string-lessp could be inconvenient. IMHO, the
> >>> most important use-case of string-lessp is being a PREDICATE of
> >>> sort. This does not support optional arguments.
> >
> > Of course it does:
> >
> > (sort foo (lambda (x y) (string-lessp x y 'optional-arg)))
>
> Yes, but this would also expect optional-arg to be a variable which can
> be set by the user. That's similar to what I have proposed, I believe.
True. So I suggest to define a new variable, say,
string-collate-options, which is a key-value list with up to 2
members: ':locale' (a string), and ':case-fold' (a flag). If the
locale's codeset is UTF-8, the collation on Windows will emulate what
glibc evidently does. Lisp programs will bind string-collate-options
to the value they need.
Then we can remove the reference to process-environment from the code
of string_collate.
WDYT?
next prev parent reply other threads:[~2014-08-27 15:37 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XMiOq-0000si-VD@vcs.savannah.gnu.org>
2014-07-18 6:22 ` bug#18051: 24.3.92; ls-lisp: Sorting; make ls-lisp-string-lessp a normal function? Michael Heerdegen
2014-07-18 6:53 ` Eli Zaretskii
2014-07-18 7:33 ` Michael Heerdegen
2014-07-18 8:53 ` Eli Zaretskii
2014-07-18 9:37 ` Michael Heerdegen
2014-07-18 9:46 ` Eli Zaretskii
2014-07-18 10:18 ` Michael Heerdegen
2014-07-18 13:03 ` Eli Zaretskii
2014-07-19 1:25 ` Michael Heerdegen
2014-07-19 8:17 ` Eli Zaretskii
2014-07-19 10:52 ` Michael Heerdegen
2014-07-19 10:56 ` Eli Zaretskii
2014-07-18 9:24 ` Michael Albinus
2014-07-18 9:33 ` Eli Zaretskii
2014-07-18 10:12 ` Michael Albinus
2014-07-18 12:57 ` Eli Zaretskii
2014-07-18 13:18 ` Michael Albinus
2014-07-18 13:44 ` Eli Zaretskii
2014-07-18 16:21 ` Michael Albinus
2014-07-20 5:49 ` Michael Heerdegen
2014-07-20 6:07 ` Eli Zaretskii
2014-07-20 6:21 ` Michael Heerdegen
2014-07-20 6:33 ` Eli Zaretskii
2014-07-20 7:30 ` Michael Heerdegen
2014-07-20 8:14 ` Eli Zaretskii
2014-07-20 8:24 ` Michael Heerdegen
2014-07-20 8:38 ` Eli Zaretskii
2014-07-20 9:15 ` Michael Heerdegen
2014-07-20 9:18 ` Eli Zaretskii
2014-07-20 11:44 ` Michael Albinus
2014-07-20 11:59 ` Eli Zaretskii
2014-07-20 15:26 ` Michael Albinus
2014-07-20 16:16 ` Eli Zaretskii
2014-08-16 21:52 ` Michael Albinus
2014-08-17 16:38 ` Eli Zaretskii
2014-08-17 17:55 ` Eli Zaretskii
2014-08-17 18:46 ` Michael Albinus
2014-08-17 18:52 ` Eli Zaretskii
2014-08-21 9:05 ` Michael Albinus
2014-08-21 14:41 ` Eli Zaretskii
2014-08-22 14:23 ` Michael Albinus
2014-08-23 9:05 ` Eli Zaretskii
2014-08-23 16:42 ` Michael Albinus
2014-08-23 17:33 ` Eli Zaretskii
2014-08-23 20:32 ` Michael Albinus
2014-08-24 14:54 ` Eli Zaretskii
2014-08-24 16:18 ` Michael Albinus
2014-08-25 15:01 ` Stefan Monnier
2014-08-27 8:49 ` Michael Albinus
2014-08-27 15:37 ` Eli Zaretskii [this message]
2014-08-27 18:02 ` Michael Albinus
2014-08-27 15:48 ` Glenn Morris
2014-08-27 16:53 ` Eli Zaretskii
2014-08-28 3:23 ` Stefan Monnier
2014-08-27 18:08 ` Michael Albinus
2014-08-27 18:30 ` Glenn Morris
2014-08-25 16:45 ` Glenn Morris
2014-08-25 17:36 ` Eli Zaretskii
2014-07-20 6:18 ` Michael Heerdegen
2014-07-20 14:22 ` Stefan Monnier
2014-08-27 23:57 ` bug#18051: trunk r117751: Improve robustness of new string-collation code Katsumi Yamaoka
2014-08-28 0:51 ` Paul Eggert
2014-08-28 3:09 ` Katsumi Yamaoka
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=83lhqaj65e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18051@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=michael_heerdegen@web.de \
/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.