GNU bug report logs -
#18716
24.3; dired-omit-extensions's default value omits COPYING.LIB
Previous Next
Reported by: Reuben Thomas <rrt <at> sc3d.org>
Date: Tue, 14 Oct 2014 14:51:01 UTC
Severity: minor
Found in version 24.3
Done: Reuben Thomas <rrt <at> sc3d.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18716 in the body.
You can then email your comments to 18716 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Tue, 14 Oct 2014 14:51:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Reuben Thomas <rrt <at> sc3d.org>:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org.
(Tue, 14 Oct 2014 14:51:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
This is a bit unfortunate for a GNU program! The pattern that matches
is, I presume, “*.lib”; the obvious question, for me, on a
case-sensitive filing system is, need it be case-insensitive? After all,
omitting .lib files seems sensible to me, but this is a .LIB file.
In GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.7)
of 2014-03-07 on lamiak, modified by Debian
Windowing system distributor `The X.Org Foundation', version 11.0.11600000
System Description: Ubuntu 14.04.1 LTS
Configured using:
`configure '--build' 'x86_64-linux-gnu' '--build' 'x86_64-linux-gnu'
'--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib'
'--localstatedir=/var/lib' '--infodir=/usr/share/info'
'--mandir=/usr/share/man' '--with-pop=yes'
'--enable-locallisppath=/etc/emacs24:/etc/emacs:/usr/local/share/emacs/24.3/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/24.3/site-lisp:/usr/share/emacs/site-lisp'
'--with-crt-dir=/usr/lib/x86_64-linux-gnu' '--with-x=yes'
'--with-x-toolkit=gtk3' '--with-toolkit-scroll-bars'
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall'
'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro'
'CPPFLAGS=-D_FORTIFY_SOURCE=2''
Important settings:
value of $LC_MONETARY: en_GB.UTF-8
value of $LC_NUMERIC: en_GB.UTF-8
value of $LC_TIME: en_GB.UTF-8
value of $LANG: en_GB.UTF-8
value of $XMODIFIERS: @im=local
locale-coding-system: utf-8-unix
default enable-multibyte-characters: t
Major mode: Help
Minor modes in effect:
show-paren-mode: t
server-mode: t
savehist-mode: t
minibuffer-electric-default-mode: t
icomplete-mode: t
global-auto-revert-mode: t
desktop-save-mode: t
global-undo-tree-mode: t
undo-tree-mode: t
global-whitespace-mode: t
TeX-PDF-mode: t
TeX-source-correlate-mode: t
dtrt-indent-mode: t
global-auto-complete-mode: t
ido-everywhere: t
shell-dirtrack-mode: t
tooltip-mode: t
mouse-wheel-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
buffer-read-only: t
column-number-mode: t
line-number-mode: t
transient-mark-mode: t
Recent input:
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-x k <return> C-x C-f
<M-backspace> i n t <tab> <return> C-s C O P Y I N
G . L B C-a C-s O P Y <backspace> <backspace> <backspace>
C O P Y I N G C-s C-s C-s C-a C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n M-< C-x C-f C O P <tab> <tab> <tab> <return> C-x
b <return> M-o M-o M-o M-o M-o M-o M-o C-h v d i r
e d - o m i <tab> e x <tab> <return> C-s l i b C-s
C-s C-a M-x r e p o r t b <backspace> - e m a c s -
b u g <return>
Recent messages:
Omitted 3 lines.
Dired-Omit mode disabled
Omitting...
Omitted 3 lines.
Dired-Omit mode disabled
Omitting...
Omitted 3 lines.
Dired-Omit mode disabled
Type "q" to restore previous buffer.
Mark saved where search started
Load-path shadows:
/home/rrt/.emacs.d/el-get/org-mode/.dir-locals hides /home/rrt/.emacs.d/el-get/ess/.dir-locals
/home/rrt/.emacs.d/el-get/org-mode/.dir-locals hides /home/rrt/.emacs.d/el-get/el-get/.dir-locals
/home/rrt/.emacs.d/el-get/dictionary/lpath hides /home/rrt/.emacs.d/el-get/auctex/lpath
/home/rrt/.emacs.d/el-get/ess/lisp/ess-xls-d hides /usr/share/emacs24/site-lisp/ess/ess-xls-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-mouse hides /usr/share/emacs24/site-lisp/ess/ess-mouse
/home/rrt/.emacs.d/el-get/ess/lisp/ess-noweb hides /usr/share/emacs24/site-lisp/ess/ess-noweb
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sp5-d hides /usr/share/emacs24/site-lisp/ess/ess-sp5-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sta-l hides /usr/share/emacs24/site-lisp/ess/ess-sta-l
/home/rrt/.emacs.d/el-get/ess/lisp/ess-comp hides /usr/share/emacs24/site-lisp/ess/ess-comp
/home/rrt/.emacs.d/el-get/ess/lisp/ess-compat hides /usr/share/emacs24/site-lisp/ess/ess-compat
/home/rrt/.emacs.d/el-get/ess/lisp/ess-toolbar hides /usr/share/emacs24/site-lisp/ess/ess-toolbar
/home/rrt/.emacs.d/el-get/ess/lisp/ess-arc-d hides /usr/share/emacs24/site-lisp/ess/ess-arc-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess hides /usr/share/emacs24/site-lisp/ess/ess
/home/rrt/.emacs.d/el-get/ess/lisp/ess-dde hides /usr/share/emacs24/site-lisp/ess/ess-dde
/home/rrt/.emacs.d/el-get/ess/lisp/ess-lsp-l hides /usr/share/emacs24/site-lisp/ess/ess-lsp-l
/home/rrt/.emacs.d/el-get/ess/lisp/ess-r-gui hides /usr/share/emacs24/site-lisp/ess/ess-r-gui
/home/rrt/.emacs.d/el-get/ess/lisp/ess-install hides /usr/share/emacs24/site-lisp/ess/ess-install
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sas-l hides /usr/share/emacs24/site-lisp/ess/ess-sas-l
/home/rrt/.emacs.d/el-get/ess/lisp/ess-utils hides /usr/share/emacs24/site-lisp/ess/ess-utils
/home/rrt/.emacs.d/el-get/ess/lisp/ess-rdired hides /usr/share/emacs24/site-lisp/ess/ess-rdired
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sas-a hides /usr/share/emacs24/site-lisp/ess/ess-sas-a
/home/rrt/.emacs.d/el-get/ess/lisp/msdos hides /usr/share/emacs24/site-lisp/ess/msdos
/home/rrt/.emacs.d/el-get/ess/lisp/ess-font-lock hides /usr/share/emacs24/site-lisp/ess/ess-font-lock
/home/rrt/.emacs.d/el-get/ess/lisp/ess-jags-d hides /usr/share/emacs24/site-lisp/ess/ess-jags-d
/home/rrt/.emacs.d/el-get/ess/lisp/make-regexp hides /usr/share/emacs24/site-lisp/ess/make-regexp
/home/rrt/.emacs.d/el-get/ess/lisp/ess-gretl hides /usr/share/emacs24/site-lisp/ess/ess-gretl
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sta-d hides /usr/share/emacs24/site-lisp/ess/ess-sta-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-s4-d hides /usr/share/emacs24/site-lisp/ess/ess-s4-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-trns hides /usr/share/emacs24/site-lisp/ess/ess-trns
/home/rrt/.emacs.d/el-get/ess/lisp/ess-custom hides /usr/share/emacs24/site-lisp/ess/ess-custom
/home/rrt/.emacs.d/el-get/ess/lisp/ess-mode hides /usr/share/emacs24/site-lisp/ess/ess-mode
/home/rrt/.emacs.d/el-get/ess/lisp/ess-noweb-mode hides /usr/share/emacs24/site-lisp/ess/ess-noweb-mode
/home/rrt/.emacs.d/el-get/ess/lisp/ess-roxy hides /usr/share/emacs24/site-lisp/ess/ess-roxy
/home/rrt/.emacs.d/el-get/ess/lisp/ess-debug hides /usr/share/emacs24/site-lisp/ess/ess-debug
/home/rrt/.emacs.d/el-get/ess/lisp/ess-rd hides /usr/share/emacs24/site-lisp/ess/ess-rd
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sas-d hides /usr/share/emacs24/site-lisp/ess/ess-sas-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-menu hides /usr/share/emacs24/site-lisp/ess/ess-menu
/home/rrt/.emacs.d/el-get/ess/lisp/ess-r-args hides /usr/share/emacs24/site-lisp/ess/ess-r-args
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sp3-d hides /usr/share/emacs24/site-lisp/ess/ess-sp3-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-omg-d hides /usr/share/emacs24/site-lisp/ess/ess-omg-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-vst-d hides /usr/share/emacs24/site-lisp/ess/ess-vst-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sp6-d hides /usr/share/emacs24/site-lisp/ess/ess-sp6-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-s3-d hides /usr/share/emacs24/site-lisp/ess/ess-s3-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-swv hides /usr/share/emacs24/site-lisp/ess/ess-swv
/home/rrt/.emacs.d/el-get/ess/lisp/mouseme hides /usr/share/emacs24/site-lisp/ess/mouseme
/home/rrt/.emacs.d/el-get/ess/lisp/ess-inf hides /usr/share/emacs24/site-lisp/ess/ess-inf
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sp4-d hides /usr/share/emacs24/site-lisp/ess/ess-sp4-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-help hides /usr/share/emacs24/site-lisp/ess/ess-help
/home/rrt/.emacs.d/el-get/ess/lisp/ess-r-d hides /usr/share/emacs24/site-lisp/ess/ess-r-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-developer hides /usr/share/emacs24/site-lisp/ess/ess-developer
/home/rrt/.emacs.d/el-get/ess/lisp/ess-s-l hides /usr/share/emacs24/site-lisp/ess/ess-s-l
/home/rrt/.emacs.d/el-get/ess/lisp/ess-sp6w-d hides /usr/share/emacs24/site-lisp/ess/ess-sp6w-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-omg-l hides /usr/share/emacs24/site-lisp/ess/ess-omg-l
/home/rrt/.emacs.d/el-get/ess/lisp/ess-tracebug hides /usr/share/emacs24/site-lisp/ess/ess-tracebug
/home/rrt/.emacs.d/el-get/ess/lisp/ess-r-a hides /usr/share/emacs24/site-lisp/ess/ess-r-a
/home/rrt/.emacs.d/el-get/ess/lisp/ess-noweb-font-lock-mode hides /usr/share/emacs24/site-lisp/ess/ess-noweb-font-lock-mode
/home/rrt/.emacs.d/el-get/ess/lisp/ess-send2 hides /usr/share/emacs24/site-lisp/ess/ess-send2
/home/rrt/.emacs.d/el-get/ess/lisp/ess-rutils hides /usr/share/emacs24/site-lisp/ess/ess-rutils
/home/rrt/.emacs.d/el-get/ess/lisp/ess-site hides /usr/share/emacs24/site-lisp/ess/ess-site
/home/rrt/.emacs.d/el-get/ess/lisp/ess-send hides /usr/share/emacs24/site-lisp/ess/ess-send
/home/rrt/.emacs.d/el-get/ess/lisp/essd-els hides /usr/share/emacs24/site-lisp/ess/essd-els
/home/rrt/.emacs.d/el-get/ess/lisp/ess-bugs-l hides /usr/share/emacs24/site-lisp/ess/ess-bugs-l
/home/rrt/.emacs.d/el-get/ess/lisp/ess-eldoc hides /usr/share/emacs24/site-lisp/ess/ess-eldoc
/home/rrt/.emacs.d/el-get/ess/lisp/ess-bugs-d hides /usr/share/emacs24/site-lisp/ess/ess-bugs-d
/home/rrt/.emacs.d/el-get/ess/lisp/ess-julia hides /usr/share/emacs24/site-lisp/ess/ess-julia
/home/rrt/.emacs.d/el-get/apache-mode/apache-mode hides /usr/share/emacs24/site-lisp/emacs-goodies-el/apache-mode
/home/rrt/.emacs.d/el-get/org-mode/contrib/lisp/htmlize hides /usr/share/emacs24/site-lisp/emacs-goodies-el/htmlize
/home/rrt/.emacs.d/el-get/quack/quack hides /usr/share/emacs24/site-lisp/emacs-goodies-el/quack
/home/rrt/.emacs.d/el-get/graphviz-dot-mode/graphviz-dot-mode hides /usr/share/emacs24/site-lisp/emacs-goodies-el/graphviz-dot-mode
/home/rrt/.emacs.d/el-get/browse-kill-ring/browse-kill-ring hides /usr/share/emacs24/site-lisp/emacs-goodies-el/browse-kill-ring
/home/rrt/.emacs.d/el-get/filladapt/filladapt hides /usr/share/emacs24/site-lisp/emacs-goodies-el/filladapt
/home/rrt/.emacs.d/el-get/xrdb-mode/xrdb-mode hides /usr/share/emacs24/site-lisp/emacs-goodies-el/xrdb-mode
/home/rrt/.emacs.d/el-get/markdown-mode/markdown-mode hides /usr/share/emacs24/site-lisp/emacs-goodies-el/markdown-mode
/home/rrt/.emacs.d/el-get/cmake-mode/cmake-mode hides /usr/share/emacs/site-lisp/cmake-mode
/home/rrt/.local/share/emacs/site-lisp/lilypond-font-lock hides /usr/share/emacs/site-lisp/lilypond-font-lock
/home/rrt/.local/share/emacs/site-lisp/lilypond-mode hides /usr/share/emacs/site-lisp/lilypond-mode
/home/rrt/.local/share/emacs/site-lisp/lilypond-init hides /usr/share/emacs/site-lisp/lilypond-init
/usr/share/emacs/24.3/site-lisp/cdargs hides /usr/share/emacs/site-lisp/cdargs
/home/rrt/.local/share/emacs/site-lisp/lilypond-indent hides /usr/share/emacs/site-lisp/lilypond-indent
/usr/share/emacs/24.3/site-lisp/debian-startup hides /usr/share/emacs/site-lisp/debian-startup
/home/rrt/.local/share/emacs/site-lisp/lilypond-song hides /usr/share/emacs/site-lisp/lilypond-song
/home/rrt/.local/share/emacs/site-lisp/lilypond-what-beat hides /usr/share/emacs/site-lisp/lilypond-what-beat
/home/rrt/.local/share/emacs/site-lisp/whitespace hides /usr/share/emacs/24.3/lisp/whitespace
/usr/share/emacs/site-lisp/rst hides /usr/share/emacs/24.3/lisp/textmodes/rst
/usr/share/emacs24/site-lisp/dictionaries-common/flyspell hides /usr/share/emacs/24.3/lisp/textmodes/flyspell
/usr/share/emacs24/site-lisp/dictionaries-common/ispell hides /usr/share/emacs/24.3/lisp/textmodes/ispell
/home/rrt/.emacs.d/el-get/cperl-mode/cperl-mode hides /usr/share/emacs/24.3/lisp/progmodes/cperl-mode
/home/rrt/.emacs.d/el-get/flymake/flymake hides /usr/share/emacs/24.3/lisp/progmodes/flymake
/home/rrt/.emacs.d/el-get/org-mode/.dir-locals hides /usr/share/emacs/24.3/lisp/gnus/.dir-locals
Features:
(shadow sort mail-extr emacsbug message rfc822 mml mml-sec mm-decode
mm-bodies mm-encode mailabbrev gmm-utils mailheader sendmail dired-aux
mail-utils network-stream starttls cperl-mode misearch multi-isearch
json-mode json-reformat json-snatcher rx paredit js css-mode tern
url-http tls url-auth mail-parse rfc2231 rfc2047 rfc2045 ietf-drums
url-gw json js3-mode imenu js3-parse js3-browse js3-highlight js3-ast
js3-messages js3-scan js3-util js3-vars cc-langs js3-externs autoconf
autoconf-mode sh-script smie vc-git make-mode flymake window-margin
org-element avl-tree org-indent org-rmail org-mhe org-irc org-info
org-gnus org-docview doc-view jka-compr image-mode org-bibtex bibtex
org-bbdb org-w3m face-remap flyspell ispell goto-addr smart-quotes
vlf-autoloads ff-paths uniquify paren server savehist minibuf-eldef
icomplete autorevert cus-start cus-load iimage org org-macro
org-footnote org-pcomplete org-list org-faces org-entities noutline
outline org-version ob-emacs-lisp ob ob-tangle org-src ob-ref ob-lob
ob-table ob-keys ob-exp ob-comint ob-core ob-eval org-compat org-macs
find-func cal-menu calendar cal-loaddefs go-mode url url-proxy
url-privacy url-expand url-methods url-history url-cookie url-domsuf
mailcap ffap dired-x desktop undo-tree diff whitespace url-util tex dbus
xml crm locate yasnippet derived quack cmuscheme scheme po-mode php-mode
etags cc-mode cc-fonts cc-guess cc-menus cc-cmds cc-styles cc-align
cc-engine speedbar sb-image ezimage dframe org-loaddefs init-paredit
ido-hacks magit-autoloads geiser-load geiser frame-restore flymake-point
filladapt dtrt-indent warnings init-eldoc eldoc-extension
auto-complete-config auto-complete edmacro kmacro popup preview-latex
tex-site auto-loads .loaddefs el-get el-get-autoloads
el-get-list-packages el-get-dependencies el-get-build el-get-status pp
el-get-methods el-get-fossil el-get-svn el-get-pacman el-get-github-zip
el-get-github-tar el-get-http-zip el-get-http-tar el-get-hg el-get-go
el-get-git-svn el-get-fink el-get-emacswiki el-get-http el-get-notify
help-mode el-get-emacsmirror el-get-github el-get-git url-parse
auth-source eieio byte-opt gnus-util mm-util mail-prsvr password-cache
url-vars el-get-elpa package cl-macs gv el-get-darcs el-get-cvs
el-get-bzr el-get-brew el-get-builtin el-get-apt-get el-get-recipes
el-get-byte-compile el-get-custom el-get-core autoload bytecomp
byte-compile cconv cl dired user-site-loaddefs ido ess-toolbar ess-mouse
mouseme thingatpt browse-url ess-menu ess-swv ess-noweb
ess-noweb-font-lock-mode ess-bugs-l essd-els ess-sas-d ess-sas-l
ess-sas-a shell pcomplete ess-sta-d ess-sta-l cc-vars cc-defs
make-regexp ess-sp6-d ess-sp3-d ess-julia ess-r-d compile ess-tracebug
format-spec ess-roxy advice cl-lib advice-preload hideshow ess-help
ess-developer ess-r-args eldoc help-fns ess-s-l ess ess-inf comint
ansi-color ring ess-mode ess-noweb-mode ess-utils ess-custom executable
easymenu ess-compat ess-site emacs-goodies-el emacs-goodies-custom
emacs-goodies-loaddefs easy-mmode devhelp time-date tooltip ediff-hook
vc-hooks lisp-float-type mwheel x-win x-dnd tool-bar dnd fontset image
regexp-opt fringe tabulated-list newcomment lisp-mode register page
menu-bar rfn-eshadow timer select scroll-bar mouse jit-lock font-lock
syntax facemenu font-core frame cham georgian utf-8-lang misc-lang
vietnamese tibetan thai tai-viet lao korean japanese hebrew greek
romanian slovak czech european ethiopic indian cyrillic chinese
case-table epa-hook jka-cmpr-hook help simple abbrev minibuffer loaddefs
button faces cus-face macroexp files text-properties overlay sha1 md5
base64 format env code-pages mule custom widget hashtable-print-readable
backquote make-network-process dbusbind dynamic-setting
system-font-setting font-render-setting move-toolbar gtk x-toolkit x
multi-tty emacs)
--
http://rrt.sc3d.org/
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Tue, 14 Oct 2014 23:42:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 18716 <at> debbugs.gnu.org (full text, mbox):
Is COPYING.LIB a file that contains the LGPL license?
Why name it so weirdly?
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Tue, 14 Oct 2014 23:52:03 GMT)
Full text and
rfc822 format available.
Message #11 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 15 October 2014 00:41, Stefan Monnier <monnier <at> iro.umontreal.ca> wrote:
> Is COPYING.LIB a file that contains the LGPL license?
>
Yes.
> Why name it so weirdly?
I don't know, but this seems to be a common name for it. In my case, it was
installed in a source tree by gettext.
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 07:57:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 18716 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> Is COPYING.LIB a file that contains the LGPL license?
> Why name it so weirdly?
L used to stand for Library.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab <at> suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 14:22:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 18716 <at> debbugs.gnu.org (full text, mbox):
>> Is COPYING.LIB a file that contains the LGPL license?
>> Why name it so weirdly?
> L used to stand for Library.
Doesn't explain the need for an extension.
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 14:27:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 15 October 2014 15:21, Stefan Monnier <monnier <at> iro.umontreal.ca> wrote:
> >> Is COPYING.LIB a file that contains the LGPL license?
> >> Why name it so weirdly?
> > L used to stand for Library.
>
> Doesn't explain the need for an extension.
This isn't really the forum for discussing the naming of a GNU license
file. dired-omit-mode deals sub-optimally with this particular name, and
even if the standard name were changed tomorrow, it would continue to occur
in the wild for years; so the real issue is: does it matter enough to fix
Emacs's treatment of it?
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 14:27:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 18716 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
>>> Is COPYING.LIB a file that contains the LGPL license?
>>> Why name it so weirdly?
>> L used to stand for Library.
>
> Doesn't explain the need for an extension.
How else would you distinguish it from the GPL?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab <at> suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 14:28:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 15 October 2014 15:26, Reuben Thomas <rrt <at> sc3d.org> wrote:
>
> so the real issue is
>
Sorry, should've said "the issue at hand". The naming issue may well be the
more important one outside the context of Emacs development.
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 17:58:01 GMT)
Full text and
rfc822 format available.
Message #29 received at 18716 <at> debbugs.gnu.org (full text, mbox):
>>>> Is COPYING.LIB a file that contains the LGPL license?
>>>> Why name it so weirdly?
>>> L used to stand for Library.
>> Doesn't explain the need for an extension.
> How else would you distinguish it from the GPL?
How 'bout: you look inside the file?
I think "COPYING" should not be synonymous with "GPL". It should just
mean "this is the file that contains the terms under which copying (and
related activities) can take place". So it can contain the GPLv2, the
GPLv3, the LGPL, or whatever else applies to your software (tho I prefer
if you stick to one of those ;-).
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 18:00:03 GMT)
Full text and
rfc822 format available.
Message #32 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> This isn't really the forum for discussing the naming of a GNU license
> file. dired-omit-mode deals sub-optimally with this particular name, and
> even if the standard name were changed tomorrow, it would continue to occur
> in the wild for years; so the real issue is: does it matter enough to fix
> Emacs's treatment of it?
I think the problem is in the naming of the file, rather than in Emacs's
treatment of files that end in ".LIB".
We could add a special ad-hoc rule for files called COPYING.LIB, but I'd
rather we fix the original problem instead.
"For years" is actually not that long ;-)
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 19:06:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 15 October 2014 18:59, Stefan Monnier <monnier <at> iro.umontreal.ca> wrote:
> > This isn't really the forum for discussing the naming of a GNU license
> > file. dired-omit-mode deals sub-optimally with this particular name, and
> > even if the standard name were changed tomorrow, it would continue to
> occur
> > in the wild for years; so the real issue is: does it matter enough to fix
> > Emacs's treatment of it?
>
> I think the problem is in the naming of the file, rather than in Emacs's
> treatment of files that end in ".LIB".
>
Although no-one has yet answered my question why Emacs takes these patterns
to be case-insensitive even on case-sensitive filing systems.
> We could add a special ad-hoc rule for files called COPYING.LIB, but I'd
> rather we fix the original problem instead.
> "For years" is actually not that long ;-)
>
My repeated experience over the decades is that absent considerable effort,
"for years" rapidly becomes "for decades". Given that we're dealing not
just with future but also with past software releases in this case, I'm not
optimistic.
Nor however do I suggest adding special ad-hoc rules if it's possible to
avoid them, hence my question about case.
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 20:58:02 GMT)
Full text and
rfc822 format available.
Message #38 received at 18716 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> I think "COPYING" should not be synonymous with "GPL". It should just
> mean "this is the file that contains the terms under which copying (and
> related activities) can take place". So it can contain the GPLv2, the
> GPLv3, the LGPL, or whatever else applies to your software (tho I prefer
> if you stick to one of those ;-).
That doesn't work. You cannot have two files with the same name.
Andreas.
--
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 22:43:02 GMT)
Full text and
rfc822 format available.
Message #41 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> Although no-one has yet answered my question why Emacs takes these patterns
> to be case-insensitive even on case-sensitive filing systems.
I don't actually know.
Maybe because the existence of case-insensitive filesystems cause the
existence of files with "weird" extensions like ".JPG" and it's easier
to just say "match case-insensitively" than to handle the known cases
where case is sometimes "messed up".
At least, that's the reason for the existence of auto-mode-case-fold.
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 22:45:01 GMT)
Full text and
rfc822 format available.
Message #44 received at 18716 <at> debbugs.gnu.org (full text, mbox):
>> I think "COPYING" should not be synonymous with "GPL". It should just
>> mean "this is the file that contains the terms under which copying (and
>> related activities) can take place". So it can contain the GPLv2, the
>> GPLv3, the LGPL, or whatever else applies to your software (tho I prefer
>> if you stick to one of those ;-).
> That doesn't work. You cannot have two files with the same name.
If your package is distributed under 2 different licenses, then you'll
either have to put both licenses in the same file or use two different
file names, but I see no reason why those two file names have to be
"COPYING" and "COPYING.LIB".
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 22:55:01 GMT)
Full text and
rfc822 format available.
Message #47 received at 18716 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier wrote:
> If your package is distributed under 2 different licenses, then you'll
> either have to put both licenses in the same file or use two different
> file names, but I see no reason why those two file names have to be
> "COPYING" and "COPYING.LIB".
You are arguing with the GNU coding standards, all hope is lost! ;)
http://www.gnu.org/prep/standards/html_node/Releases.html
The GNU GPL, if used, should be in a file called COPYING. If the GNU
LGPL is used, it should be in a file called COPYING.LESSER.
BTW, guess what they used to say instead of COPYING.LESSER...
http://cvs.savannah.gnu.org/viewvc/gnustandards/standards.texi?root=gnustandards&r1=1.185&r2=1.186
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 15 Oct 2014 23:01:02 GMT)
Full text and
rfc822 format available.
Message #50 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 15 October 2014 23:42, Stefan Monnier <monnier <at> iro.umontreal.ca> wrote:
> > Although no-one has yet answered my question why Emacs takes these
> patterns
> > to be case-insensitive even on case-sensitive filing systems.
>
> I don't actually know.
>
> Maybe because the existence of case-insensitive filesystems cause the
> existence of files with "weird" extensions like ".JPG" and it's easier
> to just say "match case-insensitively" than to handle the known cases
> where case is sometimes "messed up".
>
> At least, that's the reason for the existence of auto-mode-case-fold.
>
Maybe this is a good place to start, then? Wouldn't the user prefer to know
about oddly-named files on a case-sensitive file system, rather than have
them automagically hidden? How about (at least optionally) matching
case-sensitively? That would solve the COPYING.LIB problem too.
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 16 Oct 2014 02:02:02 GMT)
Full text and
rfc822 format available.
Message #53 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Is COPYING.LIB a file that contains the LGPL license?
Why name it so weirdly?
It's the convention I set up 25 years ago -- like COPYING, but it's
for libraries. That was when "LGPL" meant "GNU Library General Public
License".
Perhaps it should be COPYING.LESSER.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 16 Oct 2014 03:07:01 GMT)
Full text and
rfc822 format available.
Message #56 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> LGPL is used, it should be in a file called COPYING.LESSER.
Duh! ".LESSER" is also a completely silly extension.
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 16 Oct 2014 03:10:02 GMT)
Full text and
rfc822 format available.
Message #59 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> Perhaps it should be COPYING.LESSER.
Why? If your software uses the LGPL, surely the file that holds the
copying rules should be called "COPYING" or "LICENSE" but not some name
with a funny ".LESSER" extension (which luckily corresponds to no known
format yet). IF you want a different name depending on which license is
in use, it seems that "GPL-LICENSE" and "LGPL-LICENSE" would be better
choices. Of course, I'd also argue in favor of a proper extension
(e.g. ".txt") and against the use of allcaps.
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 16 Oct 2014 03:11:02 GMT)
Full text and
rfc822 format available.
Message #62 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> them automagically hidden? How about (at least optionally) matching
> case-sensitively?
Fine by me. It could even just reuse the existing auto-mode-case-fold.
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 16 Oct 2014 07:14:03 GMT)
Full text and
rfc822 format available.
Message #65 received at 18716 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
>> LGPL is used, it should be in a file called COPYING.LESSER.
>
> Duh! ".LESSER" is also a completely silly extension.
It's a name, not an extension.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab <at> suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 16 Oct 2014 13:16:01 GMT)
Full text and
rfc822 format available.
Message #68 received at 18716 <at> debbugs.gnu.org (full text, mbox):
>>> LGPL is used, it should be in a file called COPYING.LESSER.
>> Duh! ".LESSER" is also a completely silly extension.
> It's a name, not an extension.
Hmm... let's see
M-: (file-name-extension "COPYING.LESSER") RET
=>
"LESSER"
Nope, sorry. And in case you'd argue that Elisp is biased in my favor:
Python 2.7.7 (default, Jun 3 2014, 23:36:29)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> fileName, fileExtension = os.path.splitext('COPYING.LESSER')
>>> fileExtension
'.LESSER'
>>>
It looks like an extension to me, to Elisp, and to Python. Feel free to
check with other tools.
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 16 Oct 2014 18:15:01 GMT)
Full text and
rfc822 format available.
Message #71 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Perhaps it should be COPYING.LESSER.
Why?
It is a consistent series of names.
COPYING - GNU GPL
COPYING.LESSER - GNU Lesser GPL
We traditionally use names in all caps for files of basic information
that accompany programs. This custom started with README and TODO.
COPYING-LESSER would be just as good as COPYING.LESSER.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 16 Oct 2014 20:18:02 GMT)
Full text and
rfc822 format available.
Message #74 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> COPYING-LESSER would be just as good as COPYING.LESSER.
^^^^^^^^^^^^
better
-- Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Tue, 08 Nov 2016 17:52:02 GMT)
Full text and
rfc822 format available.
Message #77 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I attach a patch for this bug.
It makes dired-mark-unmarked-files act case-insensitively. This seems
reasonable, as there's nothing to suggest it does otherwise.
Also, it is better than Stefan's suggestion to use auto-mode-case-fold, as
when visiting files, the user will quickly see if a file has been e.g.
visited in the wrong major mode owing to an uppercase filename being
treated as a lowercase one; whereas in dired-omit-mode, files can be hidden
counter to the user's expectation, as happened to me with COPYING.LIB, yet
it is not obvious (because the file is hidden!).
Is this OK to install?
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
[0001-Match-files-case-insensitively-in-dired-x.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Tue, 08 Nov 2016 20:05:02 GMT)
Full text and
rfc822 format available.
Message #80 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> From: Reuben Thomas <rrt <at> sc3d.org>
> Date: Tue, 8 Nov 2016 17:51:26 +0000
>
> It makes dired-mark-unmarked-files act case-insensitively.
You meant case-sensitively, I presume.
> Also, it is better than Stefan's suggestion to use auto-mode-case-fold, as when visiting files, the user will
> quickly see if a file has been e.g. visited in the wrong major mode owing to an uppercase filename being
> treated as a lowercase one; whereas in dired-omit-mode, files can be hidden counter to the user's
> expectation, as happened to me with COPYING.LIB, yet it is not obvious (because the file is hidden!).
I don't understand what happened to the comment about *.JPG files on
case-sensitive filesystems, and how does this patch do TRT on
case-insensitive filesystems.
IOW, it sounds like the right solution cannot be so simple, because
this will most probably cause user complaints of the opposite kind.
No?
Btw, if the problem is only with COPYING.LIB, maybe a better
heuristics would be to remove .lib from completion-ignored-extensions,
as it is no longer so widespread where Emacs users dwell?
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Tue, 08 Nov 2016 22:17:02 GMT)
Full text and
rfc822 format available.
Message #83 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 8 November 2016 at 20:04, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Reuben Thomas <rrt <at> sc3d.org>
> > Date: Tue, 8 Nov 2016 17:51:26 +0000
> >
> > It makes dired-mark-unmarked-files act case-insensitively.
>
> You meant case-sensitively, I presume.
>
That's right, sorry. Fixed.
I don't understand what happened to the comment about *.JPG files on
> case-sensitive filesystems,
I took it into account. My experience is that on a case-insensitive system
(e.g. a GNU system), one finds occasional files like this, typically copied
from other systems or extracted from archives. These are not a problem for
dired-omit-mode. For visiting such files, treating auto-mode-alist and
similar case-insensitively is no problem.
> and how does this patch do TRT on
> case-insensitive filesystems.
>
It doesn't, I've fixed it in the same way as the usage of auto-mode-alist,
by testing the system type.
> IOW, it sounds like the right solution cannot be so simple, because
> this will most probably cause user complaints of the opposite kind.
> No?
See above. The only people I can see complaining are users of
case-insensitive file systems on case-sensitive systems. The correct fix
there is in any case to use the case-sensitivity of the file system, rather
than using the operating system as an indicator of that. (The same applies
to auto-mode-alist.)
Btw, if the problem is only with COPYING.LIB, maybe a better
> heuristics would be to remove .lib from completion-ignored-extensions,
> as it is no longer so widespread where Emacs users dwell?
>
I don't think special cases are a good idea. There are other examples,
e.g. CVS is a pattern, which will also match "cvs", which I have in e.g.
wiki CVS repositories.
I also added a couple of additional patches to tidy up obsolete
documentation, comments and code from dired-x.el.
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
[0001-Match-files-case-sensitively-in-dired-x.patch (text/x-patch, attachment)]
[0002-Remove-pre-customize-dired-x.el-documentation.patch (text/x-patch, attachment)]
[0003-Remove-obsolete-comments-and-commented-code-from-dir.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 09 Nov 2016 19:37:02 GMT)
Full text and
rfc822 format available.
Message #86 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> From: Reuben Thomas <rrt <at> sc3d.org>
> Date: Tue, 8 Nov 2016 22:16:45 +0000
> Cc: 18716 <at> debbugs.gnu.org
>
> I don't understand what happened to the comment about *.JPG files on
> case-sensitive filesystems,
>
> I took it into account. My experience is that on a case-insensitive system (e.g. a GNU system), one finds
> occasional files like this, typically copied from other systems or extracted from archives. These are not a
> problem for dired-omit-mode. For visiting such files, treating auto-mode-alist and similar case-insensitively is
> no problem.
Sorry, I don't understand what you mean by "these are not a problem".
With your change, *.JPG files will no longer be treated like *.jpg on
Posix systems. Won't people who want *.JPG hidden complain? IOW,
isn't this change backward-incompatible?
> + (case-fold-search (memq system-type '(windows-nt cygwin))))
The list should include ms-dos as well.
> * lisp/dired-x.el (Commentary): Remove USAGE section explaining how to
> use dired-x from .emacs. It is now fully customizable.
> * lisp/dired-x.el (dired-guess-shell-alist-user): Remove explanation of
> how to set this custom variable in .emacs. It should be customized.
Why remove these comments? The existence of Custom doesn't preclude
people from customizations in plain Lisp.
Thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 09 Nov 2016 22:01:02 GMT)
Full text and
rfc822 format available.
Message #89 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 9 November 2016 at 19:36, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Reuben Thomas <rrt <at> sc3d.org>
> > Date: Tue, 8 Nov 2016 22:16:45 +0000
> > Cc: 18716 <at> debbugs.gnu.org
> >
> > I don't understand what happened to the comment about *.JPG files on
> > case-sensitive filesystems,
> >
> > I took it into account. My experience is that on a case-insensitive
> system (e.g. a GNU system), one finds
> > occasional files like this, typically copied from other systems or
> extracted from archives. These are not a
> > problem for dired-omit-mode. For visiting such files, treating
> auto-mode-alist and similar case-insensitively is
> > no problem.
>
> Sorry, I don't understand what you mean by "these are not a problem".
> With your change, *.JPG files will no longer be treated like *.jpg on
> Posix systems. Won't people who want *.JPG hidden complain? IOW,
> isn't this change backward-incompatible?
>
I'm confused. I have not changed the behaviour of visiting files. When I
said "treating auto-mode-alist and similar case-insensitively is not a
problem", I meant that it is OK that auto-mode-alist is applied
case-insensitively.
When we talk about *.JPG files, we are not talking about dired-omit-mode,
because ".jpg" is not a suffix that would (normally) be omitted.
What I was trying to explain is that unexpected case-insensitivity in
auto-mode-alist is not a problem, because the user immediately sees the
effects. On the other hand, in dired-omit-mode it is a problem, because the
user might not see the effects (the effects are to hide things).
I double-checked, and the code I changed, dired-mark-unmarked-files, is
only called by dired-omit. However, it can also be called interactively, so
I have certainly changed the interactive behavior.
I could add a parameter to dired-mark-unmarked-files, case-fold-p,
defaulting to nil, which would be set by its current callers. But I think
you are saying that this change to the behavior of dired-omit-mode, which I
have suggested does not need a new preference, should indeed have a new
preference, so I can add that too. I think, though, that it should default
to `t', i.e. dired-omit-mode behaving case-sensitively by default.
If you'd say what you consider acceptable, I'll implement it.
> > + (case-fold-search (memq system-type '(windows-nt cygwin))))
>
> The list should include ms-dos as well.
>
OK, I will add a patch for files.el, since I got the list from there,
where it is used for the same purpose. Or perhaps there should be a global
variable defined in files.el containing the list?
> * lisp/dired-x.el (Commentary): Remove USAGE section explaining how to
> > use dired-x from .emacs. It is now fully customizable.
> > * lisp/dired-x.el (dired-guess-shell-alist-user): Remove explanation of
> > how to set this custom variable in .emacs. It should be customized.
>
> Why remove these comments? The existence of Custom doesn't preclude
> people from customizations in plain Lisp.
>
The documentation is a maintenance burden (since it is hand-written and
duplicate), few people will read it anyway, and further it is redundant,
since it can be customized in plain Lisp in the same way as any other
defcustom. (I presume you're not implying that we should add documentation
to every Lisp source file to show how to customize each defcustom?)
Further, the documentation as it is implies that these variables *should*
be customized in plain Lisp, since (unlike most cases), there is explicit
documentation about it.
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 09 Nov 2016 22:54:02 GMT)
Full text and
rfc822 format available.
Message #92 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> I double-checked, and the code I changed, dired-mark-unmarked-files, is
> only called by dired-omit. However, it can also be called interactively,
> so I have certainly changed the interactive behavior.
It can also be called from 3rd-party code.
(I don't understand the problem you are trying to solve, so I won't try
to comment further about the proposed solution.)
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Wed, 09 Nov 2016 23:31:01 GMT)
Full text and
rfc822 format available.
Message #95 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 9 November 2016 at 22:52, Drew Adams <drew.adams <at> oracle.com> wrote:
> > I double-checked, and the code I changed, dired-mark-unmarked-files, is
> > only called by dired-omit. However, it can also be called interactively,
> > so I have certainly changed the interactive behavior.
>
> It can also be called from 3rd-party code.
>
Quite right, and the suggestion I make retains the same behavior (as the
new argument I suggest is optional and its default value keeps the current
behavior).
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Thu, 10 Nov 2016 17:40:01 GMT)
Full text and
rfc822 format available.
Message #98 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> From: Reuben Thomas <rrt <at> sc3d.org>
> Date: Wed, 9 Nov 2016 22:00:22 +0000
> Cc: 18716 <at> debbugs.gnu.org
>
> Sorry, I don't understand what you mean by "these are not a problem".
> With your change, *.JPG files will no longer be treated like *.jpg on
> Posix systems. Won't people who want *.JPG hidden complain? IOW,
> isn't this change backward-incompatible?
>
> I'm confused.
So am I.
> I have not changed the behaviour of visiting files.
I wasn't talking about visiting files. I was talking about
dired-omit-mode and related Dired issues. I'm confused how visiting
files entered the scene, and why.
> When we talk about *.JPG files, we are not talking about dired-omit-mode, because ".jpg" is not a suffix that
> would (normally) be omitted.
I think it will be, if someone adds it to
completion-ignored-extensions, or some other variable used by
dired-omit-mode to set up its omitted files.
> What I was trying to explain is that unexpected case-insensitivity in auto-mode-alist is not a problem, because
> the user immediately sees the effects. On the other hand, in dired-omit-mode it is a problem, because the
> user might not see the effects (the effects are to hide things).
Yes, I understand. I was asking what do we tell users who have files
they want to omit that currently are only matched because of case
insensitivity.
> I could add a parameter to dired-mark-unmarked-files, case-fold-p, defaulting to nil, which would be set by its
> current callers. But I think you are saying that this change to the behavior of dired-omit-mode, which I have
> suggested does not need a new preference, should indeed have a new preference, so I can add that too. I
> think, though, that it should default to `t', i.e. dired-omit-mode behaving case-sensitively by default.
Sounds like a good compromise. I agree about the default, except that
it should default to case-insensitive matches on case-insensitive
filesystems (Windows etc.)
> > + (case-fold-search (memq system-type '(windows-nt cygwin))))
>
> The list should include ms-dos as well.
>
> OK, I will add a patch for files.el, since I got the list from there, where it is used for the same purpose.
If you mean set-auto-mode, then it doesn't need such a change. For
obscure historical reasons, the MS-DOS port wants to be case-sensitive
in that particular case (e.g., it wants to treat *.C files as C++, not
C). In other places in files.el, ms-dos is already mentioned where
case-insensitive file name comparison is needed.
> Or perhaps there should be a global variable defined in files.el containing the list?
I don't see the need.
> > * lisp/dired-x.el (Commentary): Remove USAGE section explaining how to
> > use dired-x from .emacs. It is now fully customizable.
> > * lisp/dired-x.el (dired-guess-shell-alist-user): Remove explanation of
> > how to set this custom variable in .emacs. It should be customized.
>
> Why remove these comments? The existence of Custom doesn't preclude
> people from customizations in plain Lisp.
>
> The documentation is a maintenance burden (since it is hand-written and duplicate), few people will read it
> anyway, and further it is redundant, since it can be customized in plain Lisp in the same way as any other
> defcustom. (I presume you're not implying that we should add documentation to every Lisp source file to show
> how to customize each defcustom?) Further, the documentation as it is implies that these variables *should*
> be customized in plain Lisp, since (unlike most cases), there is explicit documentation about it.
I don't share your interpretation of the presence of these comments,
but I'm not going to start a dispute about this.
Thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Sat, 26 Nov 2016 17:55:02 GMT)
Full text and
rfc822 format available.
Message #101 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 10 November 2016 at 17:38, Eli Zaretskii <eliz <at> gnu.org> wrote:
>
>> I could add a parameter to dired-mark-unmarked-files, case-fold-p, defaulting to nil, which would be set by its
>> current callers. But I think you are saying that this change to the behavior of dired-omit-mode, which I have
>> suggested does not need a new preference, should indeed have a new preference, so I can add that too. I
>> think, though, that it should default to `t', i.e. dired-omit-mode behaving case-sensitively by default.
>
> Sounds like a good compromise. I agree about the default, except that
> it should default to case-insensitive matches on case-insensitive
> filesystems (Windows etc.)
I have now implemented this (apologies for the delay). I attach revised patches.
--
http://rrt.sc3d.org
[0002-Allow-files-to-be-matched-case-sensitively-in-dired-.patch (text/x-patch, attachment)]
[0003-Remove-pre-customize-dired-x.el-documentation.patch (text/x-patch, attachment)]
[0004-Remove-obsolete-comments-and-commented-code-from-dir.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Sat, 26 Nov 2016 18:30:01 GMT)
Full text and
rfc822 format available.
Message #104 received at 18716 <at> debbugs.gnu.org (full text, mbox):
On 11/26/2016 12:54 PM, Reuben Thomas wrote:
>> Sounds like a good compromise. I agree about the default, except that
>> it should default to case-insensitive matches on case-insensitive
>> filesystems (Windows etc.)
> I have now implemented this (apologies for the delay). I attach revised patches.
As of commit 2809012 we have a new primitive,
file-name-case-insensitive-p, that can be used to determine whether or
not a filesystem is case insensitive. This is better than relying on
system type. For example, on both Cygwin and macOS, it's possible that
some filesystems are case-insensitive and others aren't.
Ken
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Mon, 28 Nov 2016 21:33:01 GMT)
Full text and
rfc822 format available.
Message #107 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 26 November 2016 at 18:29, Ken Brown <kbrown <at> cornell.edu> wrote:
> On 11/26/2016 12:54 PM, Reuben Thomas wrote:
>
>> Sounds like a good compromise. I agree about the default, except that
>>> it should default to case-insensitive matches on case-insensitive
>>> filesystems (Windows etc.)
>>>
>> I have now implemented this (apologies for the delay). I attach revised
>> patches.
>>
>
> As of commit 2809012 we have a new primitive,
> file-name-case-insensitive-p, that can be used to determine whether or not
> a filesystem is case insensitive. This is better than relying on system
> type. For example, on both Cygwin and macOS, it's possible that some
> filesystems are case-insensitive and others aren't.
Thanks for the heads up, that's great news! It bothered me that there was
no easy way to do this previously.
I updated my patch so that dired-omit-case-fold is now a three-valued
variable which defaults to 'filesystem, and a helper function that checks
(filename-case-sensitive-p dired-directory) when this value is used.
I've added info and NEWS documentation for dired-omit-case-fold.
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
[0002-Allow-files-to-be-matched-case-sensitively-in-dired-.patch (text/x-patch, attachment)]
[0003-Remove-pre-customize-dired-x.el-documentation.patch (text/x-patch, attachment)]
[0004-Remove-obsolete-comments-and-commented-code-from-dir.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Fri, 02 Dec 2016 09:41:01 GMT)
Full text and
rfc822 format available.
Message #110 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> From: Reuben Thomas <rrt <at> sc3d.org>
> Date: Mon, 28 Nov 2016 21:32:03 +0000
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 18716 <at> debbugs.gnu.org
>
> Thanks for the heads up, that's great news! It bothered me that there was no easy way to do this previously.
>
> I updated my patch so that dired-omit-case-fold is now a three-valued variable which defaults to 'filesystem,
> and a helper function that checks (filename-case-sensitive-p dired-directory) when this value is used.
>
> I've added info and NEWS documentation for dired-omit-case-fold.
Thanks, a few comments below. With those fixed, please push to
master.
> +@vindex dired-omit-case-fold
> +@item dired-omit-case-fold
> +
> +Default: @code{filesystem}
Please mention this value in the text that follows.
> + Set to
> +@code{nil} to be always case-sensitive, and @code{t} to be always
> +case-sensitive.
So which is it? ;-)
> +++
> +** The new user variable 'dired-omit-case-fold' allows the
> +case-sensitivity of dired-omit-mode to be configured. It defaults to
^^^^^^^^^^
Our terminology is "customized".
Bonus points for avoiding passive tense altogether ("... allows
customization of case-sensitivity ...").
> +(defcustom dired-omit-case-fold 'filesystem
> + "Whether `dired-omit-mode' will use case-folding to match the
> +regexp of files to omit. When nil, always be case-sensitive; when
The first line of a doc string should be a complete sentence.
> +(defun dired-omit-case-fold-p (dir)
> + "Return t if, according to `dired-omit-case-fold',
> + `dired-omit-mode' should use case folding to interpret its
> + regexp in directory DIR."
Likewise.
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Fri, 02 Dec 2016 16:11:01 GMT)
Full text and
rfc822 format available.
Message #113 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2 December 2016 at 09:40, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Reuben Thomas <rrt <at> sc3d.org>
> > Date: Mon, 28 Nov 2016 21:32:03 +0000
> > Cc: Eli Zaretskii <eliz <at> gnu.org>, 18716 <at> debbugs.gnu.org
> >
> > Thanks for the heads up, that's great news! It bothered me that there
> was no easy way to do this previously.
> >
> > I updated my patch so that dired-omit-case-fold is now a three-valued
> variable which defaults to 'filesystem,
> > and a helper function that checks (filename-case-sensitive-p
> dired-directory) when this value is used.
> >
> > I've added info and NEWS documentation for dired-omit-case-fold.
>
> Thanks, a few comments below. With those fixed, please push to
> master.
>
Done; thanks for the review.
> + Set to
> > +@code{nil} to be always case-sensitive, and @code{t} to be always
> > +case-sensitive.
>
> So which is it? ;-)
>
I had quite a lot of struggles with these! Well spotted.
> Bonus points for avoiding passive tense altogether ("... allows
> customization of case-sensitivity ...").
>
Bonus points earned!
> > +(defcustom dired-omit-case-fold 'filesystem
> > + "Whether `dired-omit-mode' will use case-folding to match the
> > +regexp of files to omit. When nil, always be case-sensitive; when
>
> The first line of a doc string should be a complete sentence.
>
OK, I fixed this one.
> > +(defun dired-omit-case-fold-p (dir)
> > + "Return t if, according to `dired-omit-case-fold',
> > + `dired-omit-mode' should use case folding to interpret its
> > + regexp in directory DIR."
>
> Likewise.
>
I'm a bit puzzled here: this is a complete sentence. I wondered whether
you expected an "else" clause, so I added one: "…, or nil otherwise."
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Fri, 02 Dec 2016 16:17:01 GMT)
Full text and
rfc822 format available.
Message #116 received at 18716 <at> debbugs.gnu.org (full text, mbox):
> From: Reuben Thomas <rrt <at> sc3d.org>
> Date: Fri, 2 Dec 2016 16:10:01 +0000
> Cc: Ken Brown <kbrown <at> cornell.edu>, 18716 <at> debbugs.gnu.org
>
> > +(defun dired-omit-case-fold-p (dir)
> > + "Return t if, according to `dired-omit-case-fold',
> > + `dired-omit-mode' should use case folding to interpret its
> > + regexp in directory DIR."
>
> Likewise.
>
> I'm a bit puzzled here: this is a complete sentence.
It is a complete sentence, but it takes more than one line. The first
sentence should take one line, and the first line should be a complete
sentence.
Okay?
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#18716; Package
emacs.
(Fri, 02 Dec 2016 16:32:02 GMT)
Full text and
rfc822 format available.
Message #119 received at 18716 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2 December 2016 at 16:16, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Reuben Thomas <rrt <at> sc3d.org>
> > Date: Fri, 2 Dec 2016 16:10:01 +0000
> > Cc: Ken Brown <kbrown <at> cornell.edu>, 18716 <at> debbugs.gnu.org
> >
> > > +(defun dired-omit-case-fold-p (dir)
> > > + "Return t if, according to `dired-omit-case-fold',
> > > + `dired-omit-mode' should use case folding to interpret its
> > > + regexp in directory DIR."
> >
> > Likewise.
> >
> > I'm a bit puzzled here: this is a complete sentence.
>
> It is a complete sentence, but it takes more than one line. The first
> sentence should take one line, and the first line should be a complete
> sentence.
>
> Okay?
>
Sorry, I missed "the first line" somehow. I'll install a fix for both
docstrings.
--
http://rrt.sc3d.org
[Message part 2 (text/html, inline)]
Reply sent
to
Reuben Thomas <rrt <at> sc3d.org>:
You have taken responsibility.
(Sat, 03 Dec 2016 00:23:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Reuben Thomas <rrt <at> sc3d.org>:
bug acknowledged by developer.
(Sat, 03 Dec 2016 00:23:01 GMT)
Full text and
rfc822 format available.
Message #124 received at 18716-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
[Message part 2 (text/html, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org.
(Sat, 31 Dec 2016 12:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 8 years and 232 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.