From: Miles Bader <miles@lsi.nec.co.jp>
Cc: Karl Eichwalder <keichwa@gmx.net>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: file extensions for gettext/msgfmt
Date: 08 Jul 2002 18:10:24 +0900 [thread overview]
Message-ID: <buosn2uzitb.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <Pine.SUN.3.91.1020707110755.23445A@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> > These files are binary files.
>
> IMHO, being binary files is not a reason good enough to be added to that
> list.
It's sometimes desirable to edit binary files, but it's certainly
annoying to have them interfere with completion. I think it's a
judgement call that should be made by someone experienced with that sort
of file (who that is, I don't know).
> > You don't want to edit them
>
> That's for the user to decide; there's "M-x hexl-find-file".
But emacs ought to provide good defaults.
`hexl-find-file' is a special case, and probably ought to override
completion-ignored-extensions if it can, because it's typically used for
editing files you normally don't want to edit.
-Miles
--
Yo mama's so fat when she gets on an elevator it HAS to go down.
next prev parent reply other threads:[~2002-07-08 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 10:20 file extensions for Openoffice Francesco Potorti`
2002-07-05 15:39 ` file extensions for gettext/msgfmt Karl Eichwalder
2002-07-07 4:50 ` Eli Zaretskii
2002-07-07 6:38 ` Karl Eichwalder
2002-07-07 8:09 ` Eli Zaretskii
2002-07-08 8:52 ` Andreas Schwab
2002-07-08 14:44 ` Karl Eichwalder
2002-07-08 9:10 ` Miles Bader [this message]
2002-07-09 1:43 ` Richard Stallman
2002-07-09 6:01 ` Miles Bader
2002-07-08 18:20 ` Richard Stallman
2002-07-08 13:09 ` Stefan Monnier
2002-07-05 21:04 ` file extensions for Openoffice Pavel Janík
2002-07-05 22:04 ` Richard Stallman
2002-07-07 18:31 ` Francesco Potorti`
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=buosn2uzitb.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=keichwa@gmx.net \
--cc=miles@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).