From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.50; Middle ``wŽŽ in of permissions in dired-mode is red and bold: dired-warning
Date: Sat, 13 Oct 2007 20:41:24 +0200 [thread overview]
Message-ID: <71FB6B13-9301-445B-85F7-8DE8240D68C0@Freenet.DE> (raw)
In-Reply-To: <47110CF1.7090805@gmx.at>
Am 13.10.2007 um 20:22 schrieb martin rudalics:
>> Since an update from CVS this noon (UTC) dired shows in case of
>> files or directories like these
>> .../emacs:
>> total used in directory 9248 available 22772200
>> drwxrwxr-x 66 pete admin 2244 13 Okt 19:25 .
>> drwxrwxr-x 20 pete admin 680 27 Sep 13:15 ..
>> -rw-rw-r-- 1 pete admin 210 4 Mär 2005 .arch-inventory
>> -rw-rw-r-- 1 pete admin 500 22 Mär 2007 .cvsignore
>> -rw-rw-r-- 1 pete admin 34 14 Aug 2006 .gdb_history
>> -rw-rw-r-- 1 pete admin 1044 28 Apr 2004 BUGS
>> ^
>> |
>> the ``wŽŽ in the marked column in red and bold in the dired-
>> warning face. Even when launched as 'emacs -Q.'
>>
>
> See http://lists.gnu.org/archive/html/emacs-devel/2007-10/
> msg00588.html
>
Why are security holes now distributed with GNU Emacs from CVS?
--
Greetings
Pete
_o o o o
_<< \\_/\_, \\_ \\_/\_,
(*)/(*) (*) (*) (*) `- (*)
next prev parent reply other threads:[~2007-10-13 18:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 18:02 23.0.50; Middle ``w´´ in of permissions in dired-mode is red and bold: dired-warning Peter Dyballa
2007-10-13 18:22 ` 23.0.50; Middle ``wŽŽ " martin rudalics
2007-10-13 18:41 ` Peter Dyballa [this message]
2007-10-13 19:44 ` 23.0.50; Middle ``w▌▌ " Glenn Morris
2007-10-13 20:37 ` Re: 23.0.50; Middle ``wŽŽ " Eli Zaretskii
2007-10-13 21:30 ` Peter Dyballa
2007-10-13 23:24 ` Miles Bader
2007-10-14 4:10 ` Eli Zaretskii
2007-10-14 4:03 ` Eli Zaretskii
2007-10-14 5:40 ` Re: 23.0.50; Middle ``wZZ " Drew Adams
2007-10-14 20:24 ` Eli Zaretskii
2007-10-14 20:54 ` Drew Adams
2007-10-14 21:20 ` Eli Zaretskii
2007-10-14 21:21 ` 23.0.50; Middle w " Juri Linkov
2007-10-14 22:20 ` Eli Zaretskii
2008-03-13 2:19 ` Juri Linkov
2008-03-13 4:21 ` Eli Zaretskii
2008-03-13 10:37 ` Juri Linkov
2008-03-13 20:16 ` Eli Zaretskii
2008-03-14 1:07 ` Juri Linkov
[not found] ` <f7ccd24b0803140146m22e5305dy704d7415bc00f8cd@mail.gmail.com>
2008-03-14 8:48 ` Juanma Barranquero
2008-03-14 21:30 ` Juri Linkov
2008-03-14 23:37 ` Juanma Barranquero
2008-03-15 0:17 ` Juri Linkov
2008-03-15 0:26 ` Juanma Barranquero
2008-03-14 12:12 ` Eli Zaretskii
2008-03-14 22:45 ` Chong Yidong
2008-03-15 0:16 ` Juri Linkov
2008-03-15 14:27 ` Eli Zaretskii
2008-03-15 16:20 ` Juri Linkov
2008-03-15 18:30 ` Eli Zaretskii
2008-03-15 14:10 ` Eli Zaretskii
2008-03-15 16:20 ` Juri Linkov
2008-03-15 20:44 ` Stefan Monnier
2008-03-16 14:26 ` martin rudalics
2008-03-16 16:29 ` Juri Linkov
2007-10-15 0:49 ` 23.0.50; Middle ``wZZ " Stefan Monnier
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=71FB6B13-9301-445B-85F7-8DE8240D68C0@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=emacs-pretest-bug@gnu.org \
--cc=rudalics@gmx.at \
/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).