From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: bug with file name completing
Date: Sat, 08 Oct 2005 03:05:27 +0300 [thread overview]
Message-ID: <87vf08x1gr.fsf@jurta.org> (raw)
In-Reply-To: <E1ENxaY-00045J-4w@fencepost.gnu.org> (Richard M. Stallman's message of "Fri, 07 Oct 2005 15:09:02 -0400")
> This is the completion-ignored-extensions feature at work.
> .pdf is ignored; .ps is not, because (the idea is) that's a language
> people sometimes edit.
>
> In fact, nearly all .ps files are generated by programs, just as .pdf
> files are. Should we add .ps to completion-ignored-extensions?
There are not many reasons to treat .ps differently than .pdf
nowadays. So I think the question is whether to add them both to
completion-ignored-extensions or to remove them both from it.
I want to remind that completion-ignored-extensions is used also by
dired to display files with these extensions in a different face.
There is actually no problem to have .ps and .pdf files name displayed
differently than other files, but what is bad is that dired-x uses
completion-ignored-extensions to omit files from dired buffers.
.ps, .pdf and .dvi files contain the resulting material that users
very likely may want to view via external programs calling a shell
command on them. So removing them from the dired buffer is not
a good choice. Omitting the files in dired-x is controlled by the
variable dired-omit-extensions created from the value of
completion-ignored-extensions. I suggest to remove .pdf and .dvi
from the default value dired-omit-extensions.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-10-08 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 4:29 bug with file name completing Werner LEMBERG
2005-10-07 9:37 ` Andreas Schwab
2005-10-07 15:31 ` Werner LEMBERG
2005-10-07 19:09 ` Richard M. Stallman
2005-10-08 0:05 ` Juri Linkov [this message]
2005-10-08 22:56 ` Richard M. Stallman
2005-10-08 0:07 ` Juri Linkov
2005-10-09 18:16 ` Richard M. Stallman
2005-10-15 13:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vf08x1gr.fsf@jurta.org \
--to=juri@jurta.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.