David Hansen <[EMAIL PROTECTED]> writes:
> 2007-03-01 Lennart Borgman <[EMAIL PROTECTED]>
>
> * isearch.el (isearch-message-prefix):
> Use minibuffer-prompt-properties.
>
Thanks. I have reverted the change.
--
Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk
The value for mode-line face seems to be taken from the window manager or
theme. This is inconvenient when that is close to mode-line-inactive, as is
the case for the defalut theme for Fedora Core 5. Would it be possible to
uncouple this relationship, as appears to be the case for mode-line-inac
Katsumi Yamaoka <[EMAIL PROTECTED]> writes:
>> In the gmane.emacs.diffs newsgroup, Kim F. Storm wrote:
>
>> Index: isearch.el
>> ===
>> RCS file: /cvsroot/emacs/emacs/lisp/isearch.el,v
>> retrieving revision 1.294
>> retrieving re
Kim F. Storm wrote:
Katsumi Yamaoka <[EMAIL PROTECTED]> writes:
In the gmane.emacs.diffs newsgroup, Kim F. Storm wrote:
Index: isearch.el
===
RCS file: /cvsroot/emacs/emacs/lisp/isearch.el,v
retrieving revision 1.294
retrieving re
Hello, list!
To reproduce:
1. emacs -Q -l ml.el (ml.el is attached)
2. C-x 5 2
You can see the unwanted change of the mode-line face.
ml.el
Description: ml.el
Regards,
--
Leo (GPG Key: 9283AA3F)
___
emacs-pretest-bug mai
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.
Please describe exactly what actions triggered the bug
and the precise symptoms of th
> In <[EMAIL PROTECTED]> Kim F. Storm wrote:
> Thanks. I have reverted the patch.
Thank you for fixing it so quickly.
> In <[EMAIL PROTECTED]> Lennart Borgman wrote:
> Thanks Kim. Emacs is full of surprises. I would be glad for an
> explanation of what happens with non-ASCII text.
> A
Andrea Russo skrev:
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.
Please describe exactly what actions triggered the bug
and the
Katsumi Yamaoka wrote:
In <[EMAIL PROTECTED]> Kim F. Storm wrote:
Thanks. I have reverted the patch.
Thank you for fixing it so quickly.
In <[EMAIL PROTECTED]> Lennart Borgman wrote:
Thanks Kim. Emacs is full of surprises. I would be glad for an
explanation of what happens with non-ASC
Richard Stallman writes:
> I tried to compile the latest pretest on my SPARC workstation running
> Solaris post-10 ("Nevada b57"), using this configuration
> What was the last pretest (or CVS Emacs version) that did build?
Hm, hard to say. I did try 22.0.91, and I don't think I had that
> Debugger entered--Lisp error: (text-read-only)
> read-from-minibuffer(#("Search: " 0 8 (read-only t face
> minibuffer-prompt))...
> byte-code(...
> isearch-edit-string()
> isearch-exit()
> call-interactively(isearch-exit)
This seems to indicate a bug elsewhere.
This backtrace is not e
>> I fixed the bug in the custom type, I think.
>>
>> I also find (and I'm not quite sure whether it's a real bug or just
>> something I haven't understood about regexps or re-builder) that
>> expressions such as "\\>" and "$" in the re-builder buffer don't work
>> (and are flagged as "*invalid*"
> From: Nick Roberts <[EMAIL PROTECTED]>
> Date: Tue, 6 Mar 2007 22:36:11 +1300
>
> The value for mode-line face seems to be taken from the window manager or
> theme.
How do you see this? I see the following in faces.el:
(defface mode-line
'class color) (min-colors 88))
:
>> * isearch.el (isearch-message-prefix):
>> Use minibuffer-prompt-properties.
> Thanks. I have reverted the change.
Right, the problem is that the output of isearch-message-prefix is sometimes
passed to `message' and sometimes to `read-from-minibuffer'.
`read-from-minibuffer' adds minibuffer-pro
Eli Zaretskii writes:
> > The value for mode-line face seems to be taken from the window manager or
> > theme.
>
> How do you see this? I see the following in faces.el:
>
> (defface mode-line
> 'class color) (min-colors 88))
> :box (:line-width -1 :style released-butt
Many words in Info, e.g, code, are quoted because the syntax table is
inherited from text-mode-syntax-table.
Frequently when I want to search for a another occurrence of a word I type
C-s C-s but this picks up the apostrophe (') at the end of the word. It
would make things easier if the syntax t
Eli Zaretskii writes:
> > From: Nick Roberts <[EMAIL PROTECTED]>
> > Date: Wed, 7 Mar 2007 09:51:47 +1300
> > Cc: emacs-pretest-bug@gnu.org
> > >
> > > Where's the coupling with the window manager or theme?
> >
> > That's my question really, presumably somewhere in the C code. If I chan
> From: Nick Roberts <[EMAIL PROTECTED]>
> Date: Wed, 7 Mar 2007 09:51:47 +1300
> Cc: emacs-pretest-bug@gnu.org
> >
> > Where's the coupling with the window manager or theme?
>
> That's my question really, presumably somewhere in the C code. If I change
> theme, the colour of the mode-line cha
I downloaded Seiji Zenitani's (very nice!) GNU emacs (version of 1/22/07) from
the
Apple 3rd party site for use on a fairly new Intel Macbook Pro with OS
X 10.4.8. The configuration is vanilla as downloaded.
The command "minibuffer-complete-word" is not working as expected *for files*.
Specifica
$ emacs -q
M-< C-s M-e b
Then emacs complaints that the minibuffer for isearch-edit-string is
read only. Changing the value for minibuffer-prompt-properties cures
the suffering.
Harald
In GNU Emacs 22.0.95.1 (powerpc-apple-darwin8.8.0, X toolkit)
of 2007-03-05 on gaia
X server distributo
In essence, Jan's original change was to set LIB_X11_LIB to XFT_LIBS
when using xft. Now, in essence we append XFT_LIBS to the original
value of LIB_X11_LIB, rather than overwriting it. So we may have some
duplicate libraries, but that's ok.
Now I understand. Thanks.
___
M-x partial-completion-mode
open some c file:
M-TAB runs the command PC-lisp-complete-symbol
The problem is the fact that partial-completion-mode rebinds this
command. The clean way to do it would be by setting hooks. However,
I guess there is no suitable hook in lisp-complete-symb
> These doc changes are ok with me.
Does that mean someone should install them?
Yes.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
You can see the unwanted change of the mode-line face.
Your code specifies a change in the mode-line face.
Would you please be more specific in describing
the behavior you think is mistaken?
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gn
Stefan Monnier <[EMAIL PROTECTED]> writes:
> I'm not sure what's the best solution, but in any case I think that
> read-from-minibuffer shouldn't fail just because its prompt argument is
> read-only. So I suggest the patch below.
I think this patch is ok.
I'm still not comfortable with re-insta
Harald Maier <[EMAIL PROTECTED]> writes:
> $ emacs -q
> M-< C-s M-e b
>
> Then emacs complaints that the minibuffer for isearch-edit-string is
> read only. Changing the value for minibuffer-prompt-properties cures
> the suffering.
Thanks.
I already reverted the change which causes this.
Ca
Hello, Richard!
On 2007-03-06, Richard Stallman said:
> You can see the unwanted change of the mode-line face.
>
> Your code specifies a change in the mode-line face.
>
> Would you please be more specific in describing
> the behavior you think is mistaken?
I mean the mode-line face setting i
> In <[EMAIL PROTECTED]> Stefan Monnier wrote:
>> Debugger entered--Lisp error: (text-read-only)
>> read-from-minibuffer(#("Search: " 0 8 (read-only t face
>> minibuffer-prompt))...
>> byte-code(...
>> isearch-edit-string()
>> isearch-exit()
>> call-interactively(isearch-exit)
> Th
It's because re-builder declares as "invalid" any regexp that matches the
empty string.
Is there a way it could visibly but not annoyingly notify the user
about this, instead of rejecting such a regexp?
___
emacs-pretest-bug mailing list
emacs-
> The value for mode-line face seems to be taken from the window manager or
> theme.
How do you see this?
It happens because some window managers set up X resources to control
this face. It happens to me with GNOME. That is an intentional
feature, I think.
Frequently when I want to search for a another occurrence of a word I type
C-s C-s but this picks up the apostrophe (') at the end of the word. It
would make things easier if the syntax table in Info was modified so that
the apostrophe was regarded as punctuation rather than word.
So with the patch, we get "text is read-only" errors, and without the patch
we get some messages without the minibuffer-prompt-properties.
One possibility is to copy minibuffer-prompt-properties,
delete the read-only property, and install the rest.
__
> I downloaded Seiji Zenitani's (very nice!) GNU emacs (version of 1/22/07)
> from the Apple 3rd party site for use on a fairly new Intel Macbook Pro
> with OS X 10.4.8. The configuration is vanilla as downloaded.
> The command "minibuffer-complete-word" is not working as expected *for
> files*.
>> I'm not sure what's the best solution, but in any case I think that
>> read-from-minibuffer shouldn't fail just because its prompt argument is
>> read-only. So I suggest the patch below.
> I think this patch is ok.
> I'm still not comfortable with re-installing the change to isearch at
> this
> So with the patch, we get "text is read-only" errors, and without the
> patch we get some messages without the minibuffer-prompt-properties.
> One possibility is to copy minibuffer-prompt-properties,
> delete the read-only property, and install the rest.
With my patch to minibuf.c, we w
On Tue, 06 Mar 2007 17:36:42 -0500 Richard Stallman wrote:
> M-x partial-completion-mode
>
> open some c file:
>
> M-TAB runs the command PC-lisp-complete-symbol
>
> The problem is the fact that partial-completion-mode rebinds this
> command. The clean way to do it would be by setting
>>> Debugger entered--Lisp error: (text-read-only)
>>> read-from-minibuffer(#("Search: " 0 8 (read-only t face
>>> minibuffer-prompt))...
>>> byte-code(...
>>> isearch-edit-string()
>>> isearch-exit()
>>> call-interactively(isearch-exit)
>> This seems to indicate a bug elsewhere.
>> This backtrac
> In <[EMAIL PROTECTED]> Stefan Monnier wrote:
> Thanks I ended up with the same diagnostic and have installed a similar fix.
Thanks. So, Lennart, now you can apply this change safely. ;-)
2007-03-01 Lennart Borgman <[EMAIL PROTECTED]>
* isearch.el (isearch-message-prefix):
> > Thanks I ended up with the same diagnostic and have installed a similar
> > fix.
>
> Thanks. So, Lennart, now you can apply this change safely. ;-)
>
> 2007-03-01 Lennart Borgman <[EMAIL PROTECTED]>
>
> * isearch.el (isearch-message-prefix):
> Use minibuffer-prompt-prop
> Frequently when I want to search for a another occurrence of a word I
> type C-s C-s but this picks up the apostrophe (') at the end of the
> word. It would make things easier if the syntax table in Info was
> modified so that the apostrophe was regarded as punctuation rather
> > The value for mode-line face seems to be taken from the window manager
> > or theme.
>
> How do you see this?
>
> It happens because some window managers set up X resources to control
> this face. It happens to me with GNOME. That is an intentional
> feature, I think.
I
> From: Nick Roberts <[EMAIL PROTECTED]>
> Date: Wed, 7 Mar 2007 10:22:44 +1300
> Cc: emacs-pretest-bug@gnu.org
>
> Previously it didn't matter that the colour of the mode-line was tied to X
> resources, but my point is that now there is mode-line-inactive face, it's
> important that Emacs doesn't
> But mode-line has a 3D appearance of a released button, while
> mode-line-inactive does not. Doesn't this alone distinguish them
> enough?
Barely. You can see this by customising mode-line face the have the same
foreground value as mode-line-inactive.
--
Nick
> Barely. You can see this by customising mode-line face the have the same
> foreground value as mode-line-inactive.
I mean background, of course.
--
Nick http://www.inet.net.nz/~nickrob
___
emacs-pretest-
44 matches
Mail list logo