Ar an seachtú lá déag de mí Meitheamh, scríobh Eli Zaretskii:
Is it to trigger an Invalid character message, or is something else
going on here?
It doesn't actually trigger a message, it displays a character to be
interpreted as ``the character couldn't be interpreted.''
From: Drew Adams [EMAIL PROTECTED]
Date: Sun, 18 Jun 2006 12:38:36 -0700
Dired a directory with both uppercase and lowercase file names. The
uppercase names all appear before any lowercase names. MS Windows is
case-insensitive for file and directory names, so Dired should respect
that, by
From: Aidan Kehoe [EMAIL PROTECTED]
Date: Sun, 18 Jun 2006 18:11:06 +0200
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Coding systems already replace unsupported characters with `?' (other
applications behave like that as well), so perhaps we should use some
more conventional
Jorgen Schaefer [EMAIL PROTECTED] writes:
I'm sorry for the miserable bug report. I'll try to better myself
:-)
Don't worry. Your report got us going in the right direction!!
It does fix all the reproducible problems I found, too. Thanks a
lot!
Thanks for testing.
--
Kim F. Storm
I don't use appt.el anymore, but I ran across this while testing
something else.
emacs -Q
M-x load-library appt
M-x customize-variable appt-display-format
The standard value is `ignore', and this is a mismatch (`ignore' is
not a valid value). No value menu is available to pick a value.
In
emacs -Q
M-x customize-variable RET
Get customize buffer with this:
Nil: Hide Value nil
State: NO CUSTOMIZATION DATA; not intended to be customized.
A simple error message would be better - there is no sense sending
someone to Customize unless s?he can customize something.
In GNU Emacs
Dired a directory with both uppercase and lowercase file names. The
uppercase names all appear before any lowercase names. MS Windows is
case-insensitive for file and directory names, so Dired should respect
that, by default: an alphabetic listing should pay no attention to
emacs -Q
M-x customize-variable ad-default-compilation-action
Click mouse-2 on button Value Menu. The menu opens. Try to click
mouse-2 on a menu item - the action is unrecognized.
Mouse-2 can be used to click any links and buttons. However, if you
use it to open the Value Menu, then you cannot
From: Drew Adams [EMAIL PROTECTED]
Date: Sun, 18 Jun 2006 13:11:05 -0700
I think that the default behavior for MS Windows users should be
case-insensitive. People who have other habits (;-)) or special needs such
as you describe can use `ls-lisp-ignore-case' to adjust.
When this came up
Please describe exactly what actions triggered the bug and the
precise symptoms of the bug:
Dear Emacs maintainers and/or Mr. Zenitani,
Here is the entire contents of my .emacs file:
(setq minibuffer-frame-alist
'((font . -apple-arial-medium-r-normal--18-*-*-*-*-*-mac-
roman))
Hello!
When using a prompt in a buffer with a field property,
`move-beginning-of-line' will move to the end of the prompt, not
the beginning of the line - unless the line before the field is
made invisible by an overlay.
To reproduce (tested in emacs -D -Q):
(with-current-buffer
I think that the default behavior for MS Windows users should be
case-insensitive. People who have other habits (;-)) or
special needs such as you describe can use `ls-lisp-ignore-case'
to adjust.
When this came up here, most Windows users on this list disagreed with
Drew Adams wrote:
M-x customize-variable appt-display-format
The standard value is `ignore', and this is a mismatch (`ignore' is
not a valid value).
This is by design. ignore is a special value, meaning fall back on the
previous (now obsolete) way of doing it, which used different
variables.
M-x customize-variable appt-display-format
The standard value is `ignore', and this is a mismatch (`ignore' is
not a valid value).
This is by design. ignore is a special value, meaning fall back on the
previous (now obsolete) way of doing it, which used different
I don't claim that this *should* be the case, but we *might* want to make
the default (i.e. empty input) customize all variables. That would
consistent with what customize-face does.
In any case, users should not see a Customize buffer for nil.
___
Sorry, I did not read carefully enough the first time. I see custom
barfs if I have a default value which is not in the allowed value
list. I guess I will have to add 'ignore to the allowed value list. I
wanted to avoid this because I specifically wanted people to have to
choose any of the other
From: Drew Adams [EMAIL PROTECTED]
Date: Sun, 18 Jun 2006 14:34:49 -0700
I think that the default behavior for MS Windows users should be
case-insensitive. People who have other habits (;-)) or
special needs such as you describe can use `ls-lisp-ignore-case'
to adjust.
Sorry, I did not read carefully enough the first time. I see custom
barfs if I have a default value which is not in the allowed value
list. I guess I will have to add 'ignore to the allowed value list. I
wanted to avoid this because I specifically wanted people to have to
On Fri, 16 Jun 2006 18:34:08 -0500, Pablo Barros [EMAIL PROTECTED] said:
Crashes randomly on MacOS X. Seems to be related to usage time;
works fine right after installation, then gets unstable after around
a week.
I'm afraid the above information is not too useful for debugging. I
think the
On Fri, 16 Jun 2006 13:52:47 +0200, [EMAIL PROTECTED] (Kim F. Storm) said:
Please continue testing!!!
Yes, thanks. Here are two cases:
* Case 1: The before-string is shown twice.
; emacs -Q -D
(setq overlay (make-overlay 1 3))
(overlay-put overlay 'before-string (propertize BE 'face 'bold))
20 matches
Mail list logo
