From: Jim Meyering <jim@meyering.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bastien ROUCARIES <roucaries.bastien@gmail.com>,
eggert@cs.ucla.edu, bug-gnulib@gnu.org, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: Files from gnulib
Date: Wed, 26 Jan 2011 12:02:47 +0100 [thread overview]
Message-ID: <87sjwgorl4.fsf@meyering.net> (raw)
In-Reply-To: <83hbcwxr2l.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Jan 2011 05:49:06 +0200")
Eli Zaretskii wrote:
>> From: Bastien ROUCARIES <roucaries.bastien@gmail.com>
>> Date: Tue, 25 Jan 2011 23:37:08 +0100
>>
>> (if and only if doslfn is buggy, and it does not seems according to
>> a quick search).
>
> Your search was too quick.
Considering your wish to continue supporting emacs on DOS,
I would have thought you would jump at a possible solution like this.
If it works (and indications are that it does), then it defines
away the whole problem. Wouldn't you welcome the idea of a DOS
port with no risk of 8.3 collisions?
What if the solution really is as easy as it appears? Here is a
recently-updated FAQ:
http://www-user.tu-chemnitz.de/~heha/hs_freeware/what_lfn.htm.en
Please give it an honest try before dismissing it.
Just because someone wrote about a problem does not
mean using it to build Emacs will trigger the same one.
And even if it does, report it nicely and someone might
even fix it right away.
next prev parent reply other threads:[~2011-01-26 11:02 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 8:20 RE : Re: Files from gnulib Bastien ROUCARIES
2011-01-25 14:05 ` Eli Zaretskii
2011-01-25 14:51 ` Jim Meyering
2011-01-25 15:33 ` Eli Zaretskii
2011-01-25 16:32 ` Jim Meyering
2011-01-25 18:48 ` Eli Zaretskii
2011-01-26 0:45 ` Miles Bader
2011-01-26 6:08 ` Eli Zaretskii
2011-01-26 6:41 ` Miles Bader
2011-01-26 2:42 ` Leo
2011-01-26 4:14 ` Eli Zaretskii
2011-01-26 10:52 ` Jim Meyering
2011-01-26 12:42 ` Eli Zaretskii
2011-01-26 13:09 ` Jim Meyering
2011-01-26 13:29 ` Eli Zaretskii
2011-01-25 16:50 ` Ulrich Mueller
2011-01-25 18:50 ` Eli Zaretskii
2011-01-25 19:31 ` Ulrich Mueller
2011-01-25 19:38 ` Eli Zaretskii
2011-01-25 20:00 ` Ulrich Mueller
2011-01-25 20:09 ` Eli Zaretskii
2011-01-25 19:52 ` Óscar Fuentes
2011-01-25 20:19 ` Eli Zaretskii
2011-01-25 19:04 ` Stefan Monnier
2011-01-25 19:36 ` Eli Zaretskii
2011-01-25 22:37 ` Bastien ROUCARIES
2011-01-26 3:49 ` Eli Zaretskii
2011-01-26 11:02 ` Jim Meyering [this message]
2011-01-26 11:52 ` Bastien ROUCARIES
2011-01-26 11:58 ` Bastien ROUCARIES
2011-01-26 13:12 ` Eli Zaretskii
2011-01-26 12:52 ` Eli Zaretskii
2011-01-26 13:33 ` Bastien ROUCARIES
2011-01-26 13:48 ` Eli Zaretskii
2011-01-26 15:26 ` Bastien ROUCARIES
2011-01-26 15:46 ` Eli Zaretskii
2011-01-26 15:57 ` Bastien ROUCARIES
2011-01-26 18:56 ` Eli Zaretskii
2011-01-26 14:35 ` Andy Moreton
2011-01-26 15:31 ` Bastien ROUCARIES
2011-01-26 18:28 ` Miles Bader
2011-01-26 18:59 ` Eli Zaretskii
2011-01-27 10:54 ` Simon Josefsson
2011-01-28 2:27 ` Paul Eggert
2012-08-23 11:36 ` Bastien ROUCARIES
2012-08-23 16:23 ` Eli Zaretskii
2011-01-25 16:03 ` RE : " Leo
2011-01-25 17:16 ` Miles Bader
2011-01-26 2:33 ` Stephen J. Turnbull
2011-01-26 7:18 ` Dan Nicolaescu
2011-01-26 16:15 ` Stefan Monnier
2011-01-27 3:08 ` Dan Nicolaescu
2011-01-25 18:05 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2011-01-23 12:15 Eli Zaretskii
2011-01-23 12:40 ` Eli Zaretskii
2011-01-23 19:29 ` Paul Eggert
2011-01-23 22:16 ` Bruno Haible
2011-01-24 3:26 ` Stefan Monnier
2011-01-24 4:01 ` Eli Zaretskii
2011-01-24 23:26 ` Paul Eggert
2011-01-25 4:00 ` Eli Zaretskii
2011-01-25 8:48 ` Paul Eggert
2011-01-25 11:24 ` Eli Zaretskii
2011-01-25 11:32 ` Bastien ROUCARIES
2011-01-25 14:07 ` Eli Zaretskii
2011-01-25 18:07 ` Paul Eggert
2011-01-25 19:02 ` Eli Zaretskii
2011-01-25 21:03 ` Stefan Monnier
2011-01-25 21:54 ` Eli Zaretskii
2011-01-25 22:15 ` Stefan Monnier
2011-01-26 1:05 ` Paul Eggert
2011-01-26 4:12 ` Eli Zaretskii
2011-01-26 6:01 ` Eli Zaretskii
2011-01-26 16:11 ` Stefan Monnier
2011-01-26 4:02 ` Eli Zaretskii
2011-01-26 0:32 ` Jason Rumney
2011-01-26 3:12 ` Stefan Monnier
2011-01-25 21:24 ` Paul Eggert
2011-01-25 22:06 ` Eli Zaretskii
2011-01-26 0:54 ` Paul Eggert
2011-01-26 4:10 ` Eli Zaretskii
2011-01-26 11:13 ` Jim Meyering
2011-01-26 13:09 ` Eli Zaretskii
2011-01-26 13:23 ` Jim Meyering
2011-01-26 13:29 ` Lennart Borgman
2011-01-26 13:33 ` Eli Zaretskii
2011-01-26 13:37 ` Eli Zaretskii
2011-01-26 13:50 ` Jim Meyering
2011-01-26 12:27 ` Andreas Schwab
2011-01-26 13:17 ` Eli Zaretskii
2011-01-26 13:24 ` Andreas Schwab
2011-01-26 13:41 ` Eli Zaretskii
2011-01-27 8:32 ` Paul Eggert
2011-01-27 11:08 ` Eli Zaretskii
2011-01-28 7:30 ` Paul Eggert
2011-01-28 14:20 ` Eli Zaretskii
2011-01-24 7:57 ` Glenn Morris
2011-01-24 16:37 ` Stefan Monnier
2011-01-24 4:07 ` 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=87sjwgorl4.fsf@meyering.net \
--to=jim@meyering.net \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=roucaries.bastien@gmail.com \
/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).