(expand-file-name "/..")
9 years
Marcus Harnisch
Marcus Harnisch
Evaluating the expression below leads to strange results that are
contradicting the doc-string which claims that "." and ".." would be
removed.
(expand-file-name "/..")
=> "/.."
The good news is that at least this is FSF compatible behavior. FSF
Emacs documents this weirdness saying:
“For technical reasons, this function can return correct but
non-intuitive results for the root directory; for instance,
(expand-file-name ".." "/") returns "/..". For this reason, use
(directory-file-name (file-name-directory dirname)) to traverse a
filesystem tree, not (expand-file-name ".." dirname).”
Their suggested workaround is of course not correct in cases where
`dirname' ends with `directory-sep-char':
(directory-file-name (file-name-directory "/foo/bar/../"))
=> "/foo/bar/.." <<<< WRONG
(expand-file-name "/foo/bar/../")
=> "/foo/" <<<< RIGHT
It doesn't occur to me why it would be difficult to return
(expand-file-name "/..")
=> "/"
and
(expand-file-name "/.")
=> "/"
respectively. History?
Looking at the code I find this comment:
/* `/../' is the "superroot" on certain file systems. */
Is there any file system still in use with this concept?
Thanks
Marcus
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 5 participants
- 15 comments
Summary of XEmacs Issue Tracking System Issues
9 years
XEmacs Issue Tracking System
XEmacs Issue Tracking System
ACTIVITY SUMMARY (2015-07-07 - 2015-07-14)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
570 open ( +0) / 317 closed ( +0) / 887 total ( +0)
Open issues with patches: 13
Average duration of open issues: 2129 days.
Median duration of open issues: 2316 days.
Open Issues Breakdown
new 262 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 58 ( +0)
assigned 145 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 15 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Question about font-lock
9 years
It's me FKtPp ;)
It's me FKtPp ;)
Hi all,
I am reading font-lock related code, doc, web, this days. And come out some
questions about History of font-lock in XEmacs and Gnu Emacs. Would you
please help give some light on it if possible?
1. From the doc, font-lock was implement by jwz. Do you know if font-lock
algorithm of GNU Emacs still the original jwz's one or had been totally
rewrote/refactor already?
2. I see from some web, doc that GNU Emacs jit-lock depends on C level
support, are there any detailed document about this dependency except the
source code? Do you see how difficult to import the jit-lock and its
dependency C support to XEmacs?
3. I find lazy-shot was also said to depends on C level support. I'd not
read its source yet. Are you able to describe the difference of jit-lock
and lazy-shot in high level?
Oh, lost some questions by disturb. will send out when I recall them.
Thanks,
Kai
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Summary of XEmacs Issue Tracking System Issues
9 years
XEmacs Issue Tracking System
XEmacs Issue Tracking System
ACTIVITY SUMMARY (2015-06-30 - 2015-07-07)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
570 open ( +0) / 317 closed ( +0) / 887 total ( +0)
Open issues with patches: 13
Average duration of open issues: 2122 days.
Median duration of open issues: 2309 days.
Open Issues Breakdown
new 262 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 58 ( +0)
assigned 145 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 15 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Some silly file permission in packages.
9 years
Steve Youngs
Steve Youngs
Hey Folks!
I updated my packages the other day via PUI (1st time in over a year) and
I've discovered that there is a bunch of files set to 600 (read/write
owner). I changed one or two locally before I realised how wide-spread
it is so I can't tell you exactly which files (pretty sure they were
mostly ChangeLogs). But a simple find will pick them up.
Can somebody with global access to where ever the packages are these days
please run...
find -perm 600 -exec chmod -v 644 {} \;
Then you'll need to tell Norbert (still the package guy, right?) to
release a bunch of packages.
Oh, and probably try to find out which of you is using a crazy
umask.:-)
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| SXEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<steve(a)sxemacs.org>---|
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments