From: Nir Nagid <sailor.nir@gmail.com>
To: rgm@gnu.org, 32519@debbugs.gnu.org
Subject: bug#32519: elisp manual filename conflict
Date: Sat, 25 Aug 2018 10:23:22 +0300 [thread overview]
Message-ID: <CALqNkd=n9NCAYtZ+EcHkTFyow+6n_x9EOYqBVZG5Y-UKH6HL-w@mail.gmail.com> (raw)
In-Reply-To: <5p8t4vu0qy.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Ah, yes, of course, I should've mentioned - Win7. I supposed there are
workarounds, but it's somewhat of an overkill to mess with settings for my
whole system to fix this one issue, isn't it? I thought they should
consider making the filenames case-insensitively unique, or I'll just
modify one of the filenames locally.
Tnx anyway.
On Fri, 24 Aug 2018 at 20:34, Glenn Morris <rgm@gnu.org> wrote:
> Nir Nagid wrote:
>
> > Hi, just downloaded the "html-compressed" version of elisp manual. Trying
> > to extract got a filename conflict - the "main" html index and the
> > "document" index are both named "index" (in different case) and my zip
> app
> > (7-zip) doesn't like it :(
>
> I assume this is on MS Windows? Apparently, it can optionally do
> case-sensitive directories since Windows 10 of April 2018, so maybe look
> into that.
>
> Apparently there is a makeinfo html output option controlled by
> CASE_INSENSITIVE_FILENAMES that could be turned on to handle this, but
> it sounds like it would make things worse for case sensitive systems (by
> having two pages in the same file but separated by anchors). And I'm not
> sure what version of texinfo added it (it doesn't seem to be in 4.13).
>
[-- Attachment #2: Type: text/html, Size: 1609 bytes --]
next prev parent reply other threads:[~2018-08-25 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 15:26 bug#32519: elisp manual filename conflict Nir Nagid
2018-08-24 17:34 ` Glenn Morris
2018-08-25 7:23 ` Nir Nagid [this message]
2018-08-28 5:51 ` Eli Zaretskii
2018-08-28 15:34 ` Glenn Morris
2018-08-28 21:24 ` Richard Stallman
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='CALqNkd=n9NCAYtZ+EcHkTFyow+6n_x9EOYqBVZG5Y-UKH6HL-w@mail.gmail.com' \
--to=sailor.nir@gmail.com \
--cc=32519@debbugs.gnu.org \
--cc=rgm@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 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.