From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: gnu-emacs-bug@moderators.isc.org
Subject: Re: File Name Aliases not indexed in the Concept Index
Date: Thu, 28 Aug 2003 22:34:43 +0200 [thread overview]
Message-ID: <2593-Thu28Aug2003223442+0300-eliz@elta.co.il> (raw)
In-Reply-To: <3F4E4D82.4040600@yahoo.com> (message from Kevin Rodgers on Thu, 28 Aug 2003 12:44:18 -0600)
> From: Kevin Rodgers <ihs_4664@yahoo.com>
> Newsgroups: gnu.emacs.bug
> Date: Thu, 28 Aug 2003 12:44:18 -0600
>
> The File Name Aliases node of the Emacs manual should have "hard links" and
> "soft links" entries in the Concept Index.
Agreed.
> Also, I don't know anyone who refers to symbolic links as symlinks
I do (and I thought everyone else did ;-)
prev parent reply other threads:[~2003-08-28 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 18:44 File Name Aliases not indexed in the Concept Index Kevin Rodgers
2003-08-28 20:34 ` Eli Zaretskii [this message]
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=2593-Thu28Aug2003223442+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=gnu-emacs-bug@moderators.isc.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).