unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: .info files
Date: Sat, 14 Apr 2012 14:28:44 +0300	[thread overview]
Message-ID: <83obqu1rir.fsf@gnu.org> (raw)
In-Reply-To: <87d37afwmi.fsf@gnu.org>

> From: Chong Yidong <cyd@gnu.org>
> Cc: rgm@gnu.org,  emacs-devel@gnu.org
> Date: Sat, 14 Apr 2012 18:14:45 +0800
> 
> Fail in the sense that 8+3 filenames can't have more than 3 characters
> in the +3 part of the filename.  So they can't be part of the Emacs
> tarball if we want to preserve 8+3 compatibility.

That's right.

> I think you missed out on a couple of messages.

I definitely did, sorry.

> What we're discussing is adding a .info extension to the info files
> in Emacs (which apparently means .info-N extensions for multi-part
> info files).

Doing so is indeed incompatible with MS-DOS.

But wasn't this discussion about visiting Info files in Info mode
automatically?  If so, instead of renaming file to .info*, I think
it's much better and more robust to detect the telltale first line,
viz.:

  This is FOO, produced by makeinfo version X.Y.Z from BAR

That's because nothing forces Info files to have the .info extension.
In fact, the Texinfo package itself distributes Info files 'texinfo',
'texinfo-1', etc.



  reply	other threads:[~2012-04-14 11:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 14:38 .info files Alfred M. Szmidt
2012-04-12 16:12 ` Stefan Monnier
2012-04-12 16:49   ` Alfred M. Szmidt
2012-04-12 18:30     ` Stefan Monnier
2012-04-12 21:58       ` Alfred M. Szmidt
2012-04-13  9:34         ` Eli Zaretskii
2012-04-19 10:44           ` Alfred M. Szmidt
2012-05-04  6:53             ` Glenn Morris
2012-05-04  9:32               ` Eli Zaretskii
2012-05-04 19:16                 ` Paul Eggert
2012-05-04 20:49                   ` Eli Zaretskii
2012-05-04 21:33                     ` Paul Eggert
2012-05-04 23:01                       ` Juanma Barranquero
2012-05-05  0:30                       ` Stefan Monnier
2012-05-06  1:24                         ` Paul Eggert
2012-05-06  2:55                           ` Eli Zaretskii
2012-05-05  7:05                       ` Eli Zaretskii
2012-05-05 11:41                         ` Juanma Barranquero
2012-05-05 20:14                         ` Glenn Morris
2012-05-06  2:52                           ` Eli Zaretskii
2012-05-08  6:28                         ` Paul Eggert
2012-05-08 17:31                           ` Eli Zaretskii
2012-04-17 13:34         ` Nix
2012-04-13 19:19       ` Glenn Morris
2012-04-13 21:01         ` Eli Zaretskii
2012-04-13 21:19           ` Glenn Morris
2012-04-14  7:01             ` Eli Zaretskii
2012-04-14  8:04               ` Chong Yidong
2012-04-14  9:15                 ` Eli Zaretskii
2012-04-14 10:14                   ` Chong Yidong
2012-04-14 11:28                     ` Eli Zaretskii [this message]
2012-04-14 18:01                       ` Glenn Morris
2012-04-14 18:13                         ` Eli Zaretskii
2012-04-16 17:44                           ` Glenn Morris
2012-04-16 19:13                             ` Eli Zaretskii
2012-04-16 20:26                               ` Glenn Morris
2012-04-16 20:33                                 ` Glenn Morris
2012-04-14 17:56                   ` Glenn Morris
2012-04-14 18:12                     ` 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=83obqu1rir.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cyd@gnu.org \
    --cc=emacs-devel@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 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).