From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: accessing own info files
Date: Tue, 14 Jan 2003 18:14:41 +0100 [thread overview]
Message-ID: <84adi3irge.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: m3u1gbn3q0.fsf@cicero.benny.turtle-trading.net
Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de> writes:
> Yes, if I were a debian user, I would do that. If they have reason to
> provide an alternative, incompatible program for installing info
> files, they should use a different name for it.
Well, Debian was there first. So actually, GNU should have used
another name.
I guess the best we can hope for is for the two implementations to
provide similar features, so that they can be used interchangeably.
My current pet peeve with the Debian version is that it doesn't
create dir files automatically. Anyone care to ask them to add that
feature?
It's difficult to convince the Debian maintainers that there is
another info directory besides /usr/share/info, and that the whole
world does not consist of Debian packages.
--
Ambibibentists unite!
next prev parent reply other threads:[~2003-01-14 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 12:59 accessing own info files Michael Below
2003-01-12 16:28 ` Benjamin Riefenstahl
2003-01-13 22:10 ` Michael Below
2003-01-14 7:17 ` Kai Großjohann
2003-01-14 15:36 ` Benjamin Riefenstahl
2003-01-14 17:14 ` Kai Großjohann [this message]
2003-01-15 1:09 ` Peter S Galbraith
2003-01-15 18:39 ` Benjamin Riefenstahl
2003-01-16 11:11 ` Alfred M. Szmidt
[not found] ` <mailman.367.1042715506.21513.help-gnu-emacs@gnu.org>
2003-01-16 15:43 ` Kai Großjohann
2003-01-16 17:04 ` Alfred M. Szmidt
[not found] ` <mailman.388.1042737292.21513.help-gnu-emacs@gnu.org>
2003-01-16 20:01 ` Kai Großjohann
2003-01-17 11:42 ` Alfred M. Szmidt
2003-01-16 19:11 ` Michael Below
2003-01-17 11:40 ` Alfred M. Szmidt
2003-01-13 3:16 ` Galen Boyer
2003-01-14 13:48 ` solution for " Michael Below
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=84adi3irge.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.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.
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).