From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Chong Yidong <cyd@gnu.org>
Cc: kzhr@d1.dion.ne.jp, 11640@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#11640: 24.1.50; texinfo-format-printindex fails on Windows with Windows's sort
Date: Thu, 07 Jun 2012 19:23:46 +0300 [thread overview]
Message-ID: <831ulrw0od.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SSymp0LdbeFcRcRxG=cWKvjA22Po3wVfT_0ZSFrYfvSaQ@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Thu, 7 Jun 2012 13:49:58 +0200
> Cc: Kazuhiro Ito <kzhr@d1.dion.ne.jp>, 11640@debbugs.gnu.org
>
> On Thu, Jun 7, 2012 at 1:43 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> > Wouldn't it make sense to use it everywhere?
>
> I don't know. That code was removed in revno:89810, and was only used
> for MS-DOS, Windows and VMS.
I agree with Andreas: if we have a built-in functionality, using it is
better than relying on an external program.
> I don't know the rationale for using the system sort on other
> OSes. Performance, perhaps?
How about tradition? ;-)
Seriously, I find it hard to believe that performance matters in this
case, especially since texinfmt.el is no longer the main recommended
way of producing Info from Texinfo, which is why it doesn't get
updated with the latest features of the Texinfo language.
Stefan, Chong, any objections to sorting the indices in Lisp in this
case?
next prev parent reply other threads:[~2012-06-07 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 16:56 bug#11640: 24.1.50; texinfo-format-printindex fails on Windows with Windows's sort Kazuhiro Ito
2012-06-07 11:04 ` Juanma Barranquero
2012-06-07 11:43 ` Andreas Schwab
2012-06-07 11:49 ` Juanma Barranquero
2012-06-07 16:23 ` Eli Zaretskii [this message]
2012-06-07 18:47 ` Juanma Barranquero
2012-06-08 5:45 ` Stefan Monnier
2012-06-08 12:25 ` Juanma Barranquero
2012-06-07 16:24 ` Eli Zaretskii
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=831ulrw0od.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11640@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=kzhr@d1.dion.ne.jp \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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).