Having line number and column in messages from bytecomp.el is a great
help. When they are correct, that is. Otherwise they are very confusing.
If one compiles a file foo.el with the lines
1: (defun foo (l)
2: (mapc (lambda (elm)
3: (consp elm))
4: l)
5: (message "foo: %s" elm
Reiner Steib wrote:
>The following patch fixed it. Okay to install?
>
>
Yes. I just installed it. Thanks!
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Luc Teirlinck wrote:
> I have done that and checked that bootstrapping now works OK.
Thanks
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Juanma Barranquero wrote:
>Anyway, I'd prefer not to make many changes to desktop.el (even quite
>non-intrusive changes like these) until Lars returns from holidays, as
>he said he would take a look at some questions I posed. I'll post a
>patch as soon as I've got it ready, and wait for him.
>
>
I wrote:
>I agree. I will change that.
>
>
Now I remember that I added `desktop-clear-preserve-buffers-regexp' to
obtain backwards compatibility. If `desktop-clear-preserve-buffers' is
changed to accept regexps, strings like "*Messages*" get another
meaning, so they must be changed.
But it's me
Juanma Barranquero wrote:
> - Why is desktop-locals-to-save automatically buffer local? I can
>understand why should it be buffer-local, but automatically? I'd think
>that most users/modes are simply going to add to the default value of
>the variable. Or am I missing something?
>
>
I guess it do
Juanma Barranquero wrote:
>It is really necessary to delete the file prior to `write-region' it?
>
>
I don't know of any reason why it should be necessary. To me it looks bad.
My patch (included in a prior post) deletes the deletion :-)
___
Emacs-de
Juanma Barranquero wrote:
>In fact, I'm not sure what criterion is used to decide the default
>value of `desktop-locals-to-save'.
>
I guess it should include variables set directly or indirectly by the
user to control
some kind of customization, minor modes excluded. But that's not exactly
a preci
Juanma Barranquero wrote:
>I'm having a few problems with highlight-changes-mode, which is a
>not-very-standard minor mode.
>
>
Yes, the desktop module expects minor modes to follow the conventions.
The only mechanism
to deal with non-conventional minor modes is `desktop-minor-mode-table'
that a
Juanma Barranquero wrote:
> (These questions are mainly for Lars Hansen, who did most of the
> recent cleanup work on desktop.el)
I am just about to go to Greece on vacation, far away form e-mail. But I
will be glad to use a bit of time to look into your questions (I bring a
laptop). When I
Kim F. Storm wrote:
> I suggtest that we install my (imperfect) patch, and add a note to
> TODO, that we need to address this issue after the release.
Has this been forgotten?
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailm
Kim F. Storm wrote:
>I suggtest that we install my (imperfect) patch, and add a note to
>TODO, that we need to address this issue after the release.
>
>
I agree. In my test your patch makes CVS Emacs work like Emacs 21, so at
least there is no regression.
__
Start todays emacs with -Q and set scroll-conservatively to some
non-zero number, say 1.
Then type eg. M-x ABC. Now the minibuffer shows "M-x ABC" as expected.
But if you type the Danish character A-ring (a capital A with a ring
above) everything seems to disappear from the minibuffer.
I am sorry
>That is not what the display property is for.
>
You may argue so, but it is a bug anyway.
If empty strings are not allowed, it should be stated in the manual and
an error should be signaled. Now emacs just silently malfunctions.
___
Emacs-devel mailin
An empty string as display property has the advantage over the invisible
property that it can be made conditional. However, an empty string as
display property does not work. Try this:
(defun test ()
(interactive)
(select-window (display-buffer (get-buffer-create "*test*")))
(erase-buffer)
Stephan Stahl wrote:
However as others have pointed out, (desktop-read) at a later time
should reenable desktop-save-mode which it does not right now.
I disagree. The command desktop-read is supposed to reload a saved
desktop and nothing else, it should never change desktop-save-mode. We
have the
David Kastrup wrote:
However, when calling desktop-read explicitly in a --no-desktop
session, desktop-save-mode should probably be reset to the customized
default. At least I think that is more or less what people would
expect.
I think it would be confusing if desktop-read behaved differently i
Stephan Stahl wrote:
Maybe --no-desktop should disable desktop-save-mode?
I just installed a change to make --no-desktop switch off desktop-save mode.
BTW, I now see that RMS have proposed essentially the same patch.
___
Emacs-devel mailing list
Emacs
Stephan Stahl wrote:
Specify the option `--no-desktop' on the command line when you don't
want it to reload any saved desktop.
IMHO this describes clearly what the --no-desktop flag does. But you may
be right the the flag should do something different.
I can make --no-desktop disabel desktop
Richard Stallman wrote:
Can anyone think of a non-obsolete use for keyboard-translate-table,
> to put in the example?
If you want C-x, C-c and C-v do cut, copy and paste without the IMHO
confusing overloading done by CUA-mode, you can simply do
(keyboard-translate ?\C-x 'control-x)
(keyboard-tran
20 matches
Mail list logo
