> 2005-04-26 Richard M. Stallman <[EMAIL PROTECTED]>
>
> * simple.el (line-move-1): Avoid using vertical-motion in easy cases.
I already fixed one or two other bugs related to that change
I guess there are no "easy cases" when it comes to line-move :-|
Although it is
Richard Stallman <[EMAIL PROTECTED]> writes:
> Thanks.
You missed one occurrence:
(hbar . HEIGHT) display a horizontal bar cursor with width HEIGHT
^^
--
Johan Bockgård
___
Emacs-pretest-bu
OK. Are you saying that it will remain as is (iconifies on exit), or will
you try to somehow allow for different behaviors: iconify, delete frame,
leave frame displayed?
If this is the way it will be, then I'll adapt locally; if you will change
things, then I'll wait - I just want to know.
Thanks
> It works fine for `c' not at the top level: in the middle of debugging it
> does not iconify or remove or flash the frame. Thanks.
Good.
> Did you provide some way for users to get a different behavior from `q' and
> `c' at top level, besides iconifying?
No, no time for it.
> I notice the new
Hi Stefan,
I finally got a chance to check your latest fix to debug.el.
It works fine for `c' not at the top level: in the middle of debugging it
does not iconify or remove or flash the frame. Thanks.
For `q', however, and for `c' at the top level, it still iconifies the
frame.
The curr
Thanks.
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Ralf Angeli <[EMAIL PROTECTED]> writes:
> * Ralf Angeli (2005-06-16) writes:
>
>> After executing the code move point upwards with `C-p'. After point
>> hit the top of the window further movement will scroll the buffer line
>> by line. This will make the overlays disappear occasionally,
>> i.e.
* Ralf Angeli (2005-06-16) writes:
> After executing the code move point upwards with `C-p'. After point
> hit the top of the window further movement will scroll the buffer line
> by line. This will make the overlays disappear occasionally,
> i.e. instead of the "XXX\nXXX" strings one will see t
C-c C-v (python-check), called with the default command, results in
an error:
call-interactively: Symbol's value as variable is void: compilation-
error-regexp-alist
pychecker is not installed in my path, so there should be a proper
error message.
In GNU Emacs 22.0.50.1 (powerpc-ap
> I think ps-spool-buffer-with-faces, which almost always does a superb
> job, fails at giving "#ifdef" with friends in c-files a proper
> colour. They get coloured in the buffer, but not in the printout.
Thanks for the report. ps-print doesn't print not only colours of
preprocessor directives, b
10 matches
Mail list logo
