I tried looking in Customize by browsing groups. Starting at the top, I
didn't see anything about "mouse", so I tried group "convenience" - to no
avail.
It should be somewhere under the group hypermedia. (It could be in
other places too.)
After I searched my emacs-devel email and
Thanks. I wrote to him.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
What about obsolete\*.el? Does it make sense? Being in obsolete\ does
not mean they're gonna be used with older releases, does it?
Nothing in the Emacs distribution is meant for use with older
releases. If you want to fix those files, please do.
Any comment whether these can/should/m
I will install this with some changes. Thanks.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
> From: "Jan D." <[EMAIL PROTECTED]>
> Date: Fri, 6 May 2005 06:51:38 +0200
> Cc: emacs-devel@gnu.org
>
> gcc -E can expand the macros just fine, it just needs the same input
> (-I -D and -U) as gcc got when creating the executable. As others
> pointed out, it is impractical to set this up if
> On Thu, 05 May 2005 15:56:58 +0900, YAMAMOTO Mitsuharu <[EMAIL
> PROTECTED]> said:
> With the attached patch, Carbon Emacs generates Lisp-level events as
> it were using X toolkit scroll bars. So the scroll bar handlers at
> the Lisp level can be used as they are. Now auto-repeat work
Jason Rumney <[EMAIL PROTECTED]> writes:
> Perhaps a better approach is to start a timer on load, and if appt is
> not "activated" within a few seconds, then warn the user that loading
> the package no longer activates it, and tell them the prefered way of
> activating appt (usually via an autoloa
If a minor mode is defined via define-minor-mode, then the status
message "FOO Mode enabled" is not displayed if toggling the mode
autoloads some package.
This happens because define-minor-mode has this fragment:
(if (called-interactively-p)
(progn
,(if global
> From: Nick Roberts <[EMAIL PROTECTED]>
> Date: Fri, 6 May 2005 09:02:51 +1200
> Cc: Eli Zaretskii <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
> emacs-devel@gnu.org
>
> Stefan Monnier writes:
> > >> ((not (file-executable-p "/lib/cpp")) "gcc -E -C -")
> >
> > > Right, but please amend this
> From: Nick Roberts <[EMAIL PROTECTED]>
> Date: Fri, 6 May 2005 09:02:51 +1200
> Cc: Eli Zaretskii <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
> emacs-devel@gnu.org
>
> Also could you please DTRT for gdb-cpp-define-alist-program.
Done. (The test for ms-dos was redundant.)
Btw, byte-compiling
Nick Roberts wrote:
> (defvar var1 "DOC1")
> (defvar var2 "DOC2")
> (defvaralias 'var1 'var2)
I think if an alias is made only then only one of the variables needs to be
declared.
So the idea of the present behavior would be to do a
(defvaralias 'var1 'var2) with a defvar f
> ... Can you go to the RMAIL buffer and try something like
>
> (length (save-restriction (widen) (overlays-in (point-min) (point-max
> 6128
How many did you expect?
Under 1000. Now my RMAIL has slowed even more and I have 13604 overlays.
I will follow RMS' suggestion,
Nick Roberts wrote:
As Stefan has pointed out defvaralias has a symmetry in its arguments
Looking at the old message, I believe that what Stefan said is that in
defvaralias (unlike in `define-obsolete-variable-alias'), there are no
"old" and "new" variables or "obsolete" and "updated" variable
Drew Adams wrote:
> I fired up GNU Emacs 21.3.50.1 (i386-mingw-nt5.1.2600) of 2005-01-30 on
> NONIQPC and discovered that mouse-1 was now following links. Not
remembering
> the email thread about this, I looked in Emacs itself for how to turn
this
> new behavior off.
>
> I didn't find anything ab
>> ... Can you go to the RMAIL buffer and try something like
>> (length (save-restriction (widen) (overlays-in (point-min) (point-max
>> 6128
> How many did you expect?
> Under 1000. Now my RMAIL has slowed even more and I have 13604 overlays.
Looks like it may be the culprit. Could you
In 2004/04/05 we started a thread about highlighting grep buffer, the
code mentioned there uses the ansi codes of grep and activates the
`ansi-color-apply-on-region'.
This solution is partially acceptable, will work for most of the users,
but will fail for non GNU Grep, I cannot customize it in Em
Stefan Monnier <[EMAIL PROTECTED]> writes:
> The version of Speedbar in the tree is very old. The author of Speedbar has
> made many more releases of it, distributed as part of the Semantic
> package IIRC. We should upgrade to the latest version.
>
> I contacted the author (Eric Ludlam) about th
(length (save-restriction (widen) (overlays-in (point-min)
(point-max
to see how many overlays are in the buffer?
6128
Please look at the value of rmail-overlay-list.
Are most of these overlays in that list?
___
Emacs-devel ma
This solves enough problems that I think it can be installed now.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
With an even newer instance of Emacs and the `goto-address' hook
commented out
(pp
(save-restriction
(widen)
(overlays-in (point-min)
(point-max)))
(get-buffer-create "*overlays*"))
tells me
(#
#
#)
But rmai
* calendar/appt.el: Only activate appt if in an interactive
session. This stops appt from prompting during Emacs bootstrap.
Just loading appt.el probably should not activate the feature.
In the 90s it was not unusual for packages to work that way,
but when Custom was added
As the comment says, it's necessary for backwards compatibility, and I
wasn't particularly happy about having to do it.
Backwards compatibility is not sufficient reason for this.
Loading appt.el used to activate the appointment package (in a
convoluted way, I think; can't remember
Stefan Monnier <[EMAIL PROTECTED]> suggested
If you just
(pp
(save-restriction
(widen)
(overlays-in (point-min)
(point-max)))
(get-buffer-create "*overlays*"))
and then look at the *overlays* buffer, you should be ab
Perhaps a better approach is to start a timer on load, and if appt is
not "activated" within a few seconds, then warn the user that loading
the package no longer activates it, and tell them the prefered way of
activating appt (usually via an autoloaded function).
This could be a go
This is a conundrum: Any value that lets the compilation proceed will
(necessarily) produce wrong results. Any value that stops the calculation
if
the latitude/longitude/zone are not set will stop compilation. Silly.
The value should not be used at compile time.
[I just sent a message saying I first had
(add-hook 'rmail-show-message-hook 'goto-address)
in my .emacs file. I got many overlapping overlays. Then I commented
that line out and started a new instance of Emacs. I got only two
overlays, neither overlapping.]
Now I have uncommented the li
There are two solutions for the variable case. Document the fact in
the docstring and Elisp documentation of defvaralias, or make
defvaralias behave exactly like defalias and get rid of the "unless"
behavior. I prefer the latter.
I think that is cleaner, but it is also an incompa
YAMAMOTO Mitsuharu writes:
> With the attached patch, Carbon Emacs generates Lisp-level events as
> it were using X toolkit scroll bars. So the scroll bar handlers at
> the Lisp level can be used as they are. Now auto-repeat works, and
> changing the pressed part (e.g., pressing the up arrow and
Richard Stallman wrote:
> He will just have to change his init file. Please take this out now.
Okay. Separately, I'll see if I can achieve backwards compatibility
some other way.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/m
> and then look at the *overlays* buffer, you should be able to see
> the start/end points of those overlays, so you can at least see if
> they're empty. You maybe also want to check whether some/many of
> them seem to be piled up one of top of the other.
> Here is part of what I
Let me just say that I find this new "feature" dubious.
- it makes things even more "angry fruit salad" and thus requires
yet more tweaking to make the text legible again.
- it's unclear that these specific chars are particular sources of errors.
- why not have a more generic name like font-lock
Richard Stallman wrote:
I think that is cleaner, but it is also an incompatible change.
I'd rather warn people we will change this after version 22.
But the function is new in 22.1, so if we change this in 23, we have
aberrant behavior for just one single release. All current
documentation
Marcelo Toledo <[EMAIL PROTECTED]> writes:
> Create a convention that it will not be activated when loaded
That convention already exists.
> Warning the user after loading the package doesn't seem
> correct, imagine if he loads 10 packages that warn him of something.
I didn't mean to do that fo
Richard Stallman <[EMAIL PROTECTED]> writes:
> Perhaps a better approach is to start a timer on load, and if appt is
> not "activated" within a few seconds, then warn the user that loading
> the package no longer activates it, and tell them the prefered way of
> activating appt (us
> > Also could you please DTRT for gdb-cpp-define-alist-program.
>
> Done. (The test for ms-dos was redundant.)
Thanks.
> Btw, byte-compiling gdb-ui.el emits these two warnings which I think
> should be taken care of:
>
> In gdb-info-locals-handler:
> gdb-ui.el:1944:8:Warning: func
In article <[EMAIL PROTECTED]>, Richard Stallman <[EMAIL PROTECTED]> writes:
>> Can people please volunteer to do this for parts of the distribution?
>> For instance, you could pick a subdir of lisp and do that subdir.
> I'll do that for lisp/international and lisp/language.
> Thank you.
> This solves enough problems that I think it can be installed now.
I've installed these changes. I've added an entry in NEWS and partly updated
the Emacs manual.
GUD tooltips are now toggled by the minor mode gud-tooltip-mode independenttly
of normal tooltips. However, in the manual it may sti
Nick Roberts wrote:
I mean:
(defvar var2 "DOC2")
(defvaralias 'var1 'var2)
Of course, but I did a prior (defvar var1 "DOC1") to give var1 a
docstring. Apart from that the (defvar var1 "DOC1") is really bad. A
defvaralias form, like a defalias form, constitutes a definition and
one sho
Luc Teirlinck writes:
> Nick Roberts wrote:
>
> > (defvar var1 "DOC1")
> > (defvar var2 "DOC2")
> > (defvaralias 'var1 'var2)
>
>I think if an alias is made only then only one of the variables needs to
> be
>declared.
>
> So the idea of the present behavior wo
Apologies for coming late to this thread ...
On 2005-04-28, Kim F. Storm <[EMAIL PROTECTED]> wrote:
>
> Currently cua-mode uses S-return to toggle rectangle marking.
>
> This works nicely most of the time, but it is just too easy to
> accidentally hit it after another shifted key, e.g. an upp
The docstring and Elisp documentation of `read-directory-name' conflict.
Docstring:
Default name to default-dirname if user exits with the same
non-empty string that was inserted by this function.
(If default-dirname is omitted, dir combined with initial is used,
or just dir if initial is
Richard Stallman wrote:
- Shouldn't this option be described in the Emacs manual?
It is.
But in a not very clear way. It says: "The variable
@code{mouse-1-click-follows-link} controls whether @kbd{Mouse-1} has
this behavior." after talking about all kinds of details, short clicks
vs
>From my previous reply:
Sorry, that was wrong. It should have been:
! (if initial (concat dir initial) dir default-directory)))
Obviously, that was even _more_ wrong.
It should have been the following, as in Juri's original patch:
- (if initial (concat dir initial)
>From my prior message:
>From the following ielm run it appears that the Elisp documentation is
still correct, even though the code and docstring have changed (on
April 23) since I checked all of this quite a while ago:
ELISP> default-directory
"~/"
ELISP> (read-directory-name "
Is the behavior implemented by the following patch what was really
intended by the April 23 change? One could, in addition to the patch
below, also change the `(concat dir initial)' into
`(expand-file-name initial dir)' which is probably more portable.
Note however that the _old_ (in fact _still
> This can't be done completely mechanically, since one has to check
> when the last copyrightable changes (and not all changes are
> copyrightable) have been, correct?
>
> That's correct, aside from one subtle point. It's not that "not all
> changes are copyrightable" but rathe
>From my previous patch:
! (if initial (concat dir initial) dir)))
Sorry, that was wrong. It should have been:
! (if initial (concat dir initial) dir default-directory)))
But I saw that Juri already earlier proposed that exact same
(corrected as above) patch. Since it was not
>From my previous message:
If both initial and default-dirname are nil, the second unless-form
default-dirname to default-directory.
Of course, meant was:
the second unless-form sets default-dirname
(I accidentally enabled Overwite mode again, without noticing it.)
Sincerely,
Luc.
___
> On Thu, 05 May 2005 15:56:58 +0900, YAMAMOTO Mitsuharu <[EMAIL
> PROTECTED]> said:
> For example, you'll see only a part of screen is updated when
> scrolling on slower machines if redisplay-dont-pause is nil. This
> problem is related to the following issue, which was about mouse
> mo
Nick Roberts <[EMAIL PROTECTED]> writes:
> > This can't be done completely mechanically, since one has to check
> > when the last copyrightable changes (and not all changes are
> > copyrightable) have been, correct?
> >
> > That's correct, aside from one subtle point. It's not t
David Kastrup writes:
> > Trying to reduce it to a formula for files whose history that we're
> > not familiar with:
> >
> > e.g choosing cmacexp.el at random
> >
> > cvs annotate cmacexp.el > files.ann
I mean cvs annotate cmacexp.el > cmacexp.ann
> >
> > grep "..-...-05" cmacexp.ann |
51 matches
Mail list logo
