unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: bug-gnu-emacs@gnu.org, monnier@iro.umontreal.ca
Subject: Re: convert-standard-filename documentation is insufficient
Date: Fri, 12 Nov 2004 07:54:14 -0600 (CST)	[thread overview]
Message-ID: <200411121354.iACDsEJ12962@raven.dms.auburn.edu> (raw)
In-Reply-To: <16787.61351.738129.455604@lx-desk84.amd.com> (jeff.dwork@amd.com)

I probably used the wrong terminology in my previous reply and
explained things somewhat inaccurately.  It probably works better on
an example.  The "standard file name" of the file to store abbrevs in
is ".abbrev_defs" on GNU/Unix type systems.  This file name follows
some standard conventions on GNU/Linux.  It is not just "valid" on
GNU/Linux.  On MS-DOS this gets converted to _abbrev.def, which is not
just valid on MS-DOS, but follows conventions standard on MS-DOS.

In:

Convert a standard file's name to something suitable for the OS.

"standard file name" means something like ".abbrev_defs", as opposed
to a file name chosen by the user.  "something suitable for the OS".
means not just merely valid, but also following standard conventions
for the OS.

Sincerely,

Luc.

  parent reply	other threads:[~2004-11-12 13:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 22:02 convert-standard-filename documentation is insufficient Luc Teirlinck
2004-11-11 23:03 ` Jeff Dwork
2004-11-12  5:24   ` Werner LEMBERG
2004-11-12 13:34   ` Luc Teirlinck
2004-11-12 13:54   ` Luc Teirlinck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-08 21:58 Luc Teirlinck
     [not found] <mailman.1099.1099774836.8225.bug-gnu-emacs@gnu.org>
2004-11-08 19:29 ` Stefan Monnier
2004-11-07 22:00 Luc Teirlinck
2004-11-07 22:42 ` Eli Zaretskii
2004-11-06 18:07 Jari Aalto
2004-11-07  4:41 ` 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=200411121354.iACDsEJ12962@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).