Richard Stallman <[EMAIL PROTECTED]> writes:
> I would like some of you to look at this package, and tell me if you
> think it would be a good thing to add to Emacs. Is it well written?
> Does it follow the usual conventions and thus fit in well with the
> rest of Emacs?
I tried graphviz-dot-mod
[CVS 2005-Feb-09]
Please call base64-decode-region on this mail snippet:
SGVsbG8sDQogICBJIHdhbnQgdG8gYW5kIEdCMjMxMiB0byBhIGZvbnQgZmlsZSAuQnV0IEl0IGNh
biBiZSB1c2VkIGJ5IHRoZSBmcmVldHlwZSAuSXQgcmV0dXJuIG1lIGEgNiB3aGVuIEkgdXNlIFNl
bGVjdF9DaGFybWFwLiAgTWF5YmUgdGhlcmUgYXJlIHRoZSBvdGhlciByZWFzb24gLkNv
> From: "Lennart Borgman" <[EMAIL PROTECTED]>
> Date: Sun, 27 Feb 2005 01:25:20 +0100
>
> 1) There is a function start_hourglass. This starts a timer that turns on
> the hourglass. The function start_hourglass begins with cancel_hourglass
> which cancels the timer if it is already active and remov
The idea of using capitalized keywords is good, but you've shortened
some of the messages too much. I don't like these:
! EDITED, but not set." "\
What about:
EDITED, shown value does not take effect until you set or save it.
! SET, but not saved." "\
What about:
SET for curr
> The example of keyboard-translate-table relates to terminal flow
> control, which I believe is essentially obsolete. Can anyone think
> of a non-obsolete use for keyboard-translate-table, to put in
> the example?
It's used in normal-erase-is-backspace-mode (when running on a tty).
> Or is keyb
> IIRC, you were the one to propose _not_ following a link in a
> non-selected window, and I initially said it made sense (so I
> implemented it unconditionally).
I meant "frame", sorry.
Stefan
___
Emacs-devel mailing list
Emacs-devel@gnu.org
I got a bit irritated that Emacs did not stop to show an hourglass after an
operation ended so I looked into the code. However while trying to find the
code for this I first stumbled on some other problems. I have some
difficulties to understand the code for starting the hourglass cursor:
1) There
We need to know what compilation-directory-properties does.
Would you please write a doc string for it?
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
In lisp/button.el, function make-button sets the type of the button to a
default value if the user doesn't supply a :type property, but function
make-text-button does not.
This patch makes function make-text-button set the type of the button if
the user does not supply a :type property.
--
Francis
Given the extensive changes to compile.el and grep.el, I'm
surprised that the documentation has changed so little.
This may not be incorrect. The changes mostly affect aspects not
described in the manual--for instance, to get better results when the
user edits the buffer and then tries to
a) a double-click on a location that has no double-click binding, but
a local mouse-2 binding, will execute the mouse-2 binding. This
will make double-clicks, where not overriden, follow links without
further code changes compared to 21.4
This means two different modes of
The idea of using capitalized keywords is good, but you've shortened
some of the messages too much. I don't like these:
! EDITED, but not set." "\
you have edited something in this group, but not set anything yet.")
(set "+" custom-set-face "\
! SET, but not saved." "\
An
The example of keyboard-translate-table relates to terminal flow
control, which I believe is essentially obsolete. Can anyone think
of a non-obsolete use for keyboard-translate-table, to put in
the example?
Or is keyboard-translate-table itself obsolete nowadays?
___
Tak Ota <[EMAIL PROTECTED]> writes:
> Hi Kim,
>
> Sorry I neglected having my homework done before reporting the
> incident. Now I've narrowed it to a specific case. Here is the
> recipe.
>
> 1. Start emacs with emacs -Q
> 2. Evaluate this:
>
> (progn
>(setq w32-bdf-filename-alist
>
David Kastrup <[EMAIL PROTECTED]> writes:
> Richard Stallman <[EMAIL PROTECTED]> writes:
>
>> In order not to confuse people too much, I really would want to
>> suggest strongly that we remap double-click to mouse-2 unconditionally
>> by default (where a "stronger" mouse-2 binding exis
> From: Nick Roberts <[EMAIL PROTECTED]>
> Date: Sun, 27 Feb 2005 10:20:29 +1300
> Cc: emacs-devel@gnu.org
>
> > Some of these are mentioned in etc/NEWS, and they are not marked with
> > a "+++', which means the documentation was not yet updated to reflect
> > that change. Someone will do that
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> I have added a new option mouse-1-click-in-non-selected-windows
>> that controls whether mouse-1 click in non-selected windows
>> will follow links. Default is t.
>
> I think it should be purely and simply removed.
> It addresses the "click to focus w
> > In reality it seems to say `exit' when the compiler process terminates
> > followed
> > by the exit code in square brackets e.g [0] for normal, [1] for abnormal.
>
> It could _also_ say `signal' if the subprocess was interrupted by a
> signal. But the text you cited is incorrect as it
> David Kastrup <[EMAIL PROTECTED]> (DK) wrote:
>DK> Romain Francoise <[EMAIL PROTECTED]> writes:
>>> David Kastrup <[EMAIL PROTECTED]> writes:
>>>
I have quite often used `find-grep-dired' and it has been a
nuisance that the more often needed `find-grep' is not available.
I on
Ar an sÃà là is fiche de mà Feabhra, scrÃobh Romain Francoise:
> David Kastrup <[EMAIL PROTECTED]> writes:
>
> > The name "grep-find" is quite counterintuitive and probably only
> > chosen because it is in the grep package, and so the "grep-" prefix
> > somewhat suggested itself.
>
> I
"Jan D." <[EMAIL PROTECTED]> writes:
> 2005-02-26 kl. 15.47 skrev David Kastrup:
>
>>
>> Throwing a signal restores interrupt_input_blocked to the state of
>> the recording of the stack frame.
>
> How does it do that? I can't find that in the code.
Neither can I. I said that I don't have a clue
2005-02-26 kl. 15.47 skrev David Kastrup:
Throwing a signal restores interrupt_input_blocked to the state of the
recording of the stack frame.
How does it do that? I can't find that in the code. I assumed
record_unwind_protect did just that, recorded one unwind action to
take.
In xfns.c, li
xselect.c line 752, also 1419
I am not versed enough in the matter, but since signals restore the
setting of interrupt_input_blocked, those would appear to be bugs.
They appear to me as bugs leaving the blockage count too high, so I
don't see how they could be responsible for the underrun that i
Eli Zaretskii wrote:
When tex-mode.el from current CVS is compiled, it produces the
following warning:
In tex-mode:
tex-mode.el:818:8:Warning: function `tex-mode' defined multiple times in
this
file
Is this okay?
There is the following comment:
(define-derived-mode
When tex-mode.el from current CVS is compiled, it produces the
following warning:
In tex-mode:
tex-mode.el:818:8:Warning: function `tex-mode' defined multiple times in this
file
Is this okay?
___
Emacs-devel mailing list
Emacs-devel@gnu.org
Throwing a signal restores interrupt_input_blocked to the state of the
recording of the stack frame. In xfns.c, line 5207, we have a
BLOCK_INPUT. In line 5283 we have
record_unwind_protect (clean_up_file_dialog, make_save_value (dialog, 0));
That means that clean_up_file_dialog will get called
On Fri, Feb 25 2005, David Kastrup wrote:
> I would recommend not making any behavior by default dependent on the
> single-click length, nor on the focus situation: both approaches are
> completely obfuscate and confusing.
>
> So the change to 21.4 behavior would be the following:
>
> a) a double-
> From: Nick Roberts <[EMAIL PROTECTED]>
> Date: Sat, 26 Feb 2005 16:43:33 +1300
>
> building.texi says:
>
> >When the compiler process terminates, for whatever reason, the mode
> > line of the `*compilation*' buffer changes to say `signal' instead of
> > `run'.
>
> In reality it seems to sa
Hello, in keyboard.c there is the following code:
DEFUN ("top-level", Ftop_level, Stop_level, 0, 0, "",
doc: /* Exit all recursive editing levels. */)
()
{
#ifdef HAVE_X_WINDOWS
if (display_hourglass_p)
cancel_hourglass ();
#endif
/* Unblock input if we enter with input bloc
David Kastrup <[EMAIL PROTECTED]> writes:
> The name "grep-find" is quite counterintuitive and probably only
> chosen because it is in the grep package, and so the "grep-" prefix
> somewhat suggested itself.
It's not counterintuitive. It's an extension to `grep', but it uses
find to find files r
Romain Francoise <[EMAIL PROTECTED]> writes:
> David Kastrup <[EMAIL PROTECTED]> writes:
>
>> I have quite often used `find-grep-dired' and it has been a
>> nuisance that the more often needed `find-grep' is not available.
>> I only discovered by accident that it _does_ exist, but only under
>> th
David Kastrup <[EMAIL PROTECTED]> writes:
> I have quite often used `find-grep-dired' and it has been a nuisance
> that the more often needed `find-grep' is not available. I only
> discovered by accident that it _does_ exist, but only under the name
> `grep-find'.
How about adding a `grep-find-d
32 matches
Mail list logo
