In article <[EMAIL PROTECTED]>, Stefan Monnier <[EMAIL PROTECTED]> writes:
>> The very right way is to shift to emacs-unicode. As long as
>> we have multiple character codes for characters that user
>> don't want to distinguish, any fix is just a dirty work
>> around.
> I'm not sure about "w
Hi all
Here is updated version of Emacs tutorial (russian version). please install
it into CVS
TUTORIAL.ru.gz
Description: GNU Zip compressed data
--
With best wishes, Alex Ott
Jet Infosystems, http://www.jetinfosoft.ru/
+7 (095) 411 76 01
___
extand your tool now!
what hasn't been already said,
safe, simple and effective : 10 minutes and you've got yourself an enormous
tool,
and be sure reasults are permenent and no surgary is needed.
you'll get tired of banggin', for sure :)
come try now!
The new, bast Exttendder :
http://baptist.ja
Lute Kamstra <[EMAIL PROTECTED]> writes:
> David Kastrup <[EMAIL PROTECTED]> writes:
> If files do get reloaded often (for good reasons), then recording
> old values of functions and variables should probably be done only
> if require loads a file. That wouldn't happen twice.
Well, I still thin
David Kastrup <[EMAIL PROTECTED]> writes:
> Lute Kamstra <[EMAIL PROTECTED]> writes:
>
>> David Kastrup <[EMAIL PROTECTED]> writes:
>>
>>> Lute Kamstra <[EMAIL PROTECTED]> writes:
>>>
Consider the following situation:
function 'a is autoloaded: (autoload "blabla" ...).
function
Richard Stallman <[EMAIL PROTECTED]> writes:
> You shouldn't consider these [temporary] buffers a problem.
You're right, I really shouldn't. I'm mostly over it these days.
Midnight mode helps, too.
> Finding "the right way" to remove a temporary buffer from the screen
> is a very hard problem.
Lute Kamstra <[EMAIL PROTECTED]> writes:
> David Kastrup <[EMAIL PROTECTED]> writes:
>
>> Lute Kamstra <[EMAIL PROTECTED]> writes:
>>
>>> Consider the following situation:
>>>
>>> function 'a is autoloaded: (autoload "blabla" ...).
>>> function 'b is autoloaded: (autoload "other" ...).
>>> functio
> From: Thien-Thi Nguyen <[EMAIL PROTECTED]>
> Date: Sun, 24 Apr 2005 17:46:40 -0400
> Cc: emacs-devel@gnu.org
>
>From: Glenn Morris <[EMAIL PROTECTED]>
>Date: Sun, 24 Apr 2005 21:27:47 +0100
>
>2) should there be a new CVS branch for the release?
>
> that depends on the precise rele
> From: Richard Stallman <[EMAIL PROTECTED]>
> CC: emacs-devel@gnu.org
> Date: Sun, 24 Apr 2005 17:23:07 -0400
>
> It turns out that vertical-motion was fontifying all the text that
> it moved over. That seems to be easy to fix.
Did you try my suggestion of customizing jit-lock-defer-time? I th
David Kastrup <[EMAIL PROTECTED]> writes:
> Lute Kamstra <[EMAIL PROTECTED]> writes:
>
>> Consider the following situation:
>>
>> function 'a is autoloaded: (autoload "blabla" ...).
>> function 'b is autoloaded: (autoload "other" ...).
>> function 'c is defined.
>> function 'd is unbound.
>>
>> "b
From: Glenn Morris <[EMAIL PROTECTED]>
Date: Sun, 24 Apr 2005 21:27:47 +0100
2) should there be a new CVS branch for the release?
that depends on the precise release methodology, which hasn't been
captured under admin/ or admin/notes/, as far as i can tell. perhaps
that action (and even
> > Which of these do Lisp programmers need to use, and when?
>
> It seems like tooltip-mode is used in several files, so at least that
> function should be mentioned.
the line which begins with "Which of these do Lisp" has only the
second `>' character fontifi
I realize that you can't expect Emacs to know when you are done with a
window unless you actually tell when. The obvious way to tell when is
to type `C-x 1' or `C-x 0', but this leaves the temporary buffer
lingering, which makes me nervous.
You shouldn't consider these buffers a p
JIT lock is optimized for C-v and similar methods that page
by large chunks of text rather than by one line.
I am not sure what that means, in concrete terms of Lisp program
actions. I'm also not sure what you mean by "make text visible".
It turns out that vertical-motion was fontifyin
David Kastrup <[EMAIL PROTECTED]> writes:
> Lute Kamstra <[EMAIL PROTECTED]> writes:
>
>> David Kastrup <[EMAIL PROTECTED]> writes:
>>
>> [...]
>>
>>> Well, the idea explored a bit later later was that "load" will
>>> record autoloads, but not do anything with them by itself, instead
>>> letting "
Lute Kamstra <[EMAIL PROTECTED]> writes:
> Consider the following situation:
>
> function 'a is autoloaded: (autoload "blabla" ...).
> function 'b is autoloaded: (autoload "other" ...).
> function 'c is defined.
> function 'd is unbound.
>
> "blabla" defines 'a, 'b, 'c, and 'd as functions.
>
> Do
Lute Kamstra <[EMAIL PROTECTED]> writes:
> David Kastrup <[EMAIL PROTECTED]> writes:
>
> [...]
>
>> Well, the idea explored a bit later later was that "load" will
>> record autoloads, but not do anything with them by itself, instead
>> letting "provide" handle it.
>
> Ah, now I understand your pos
Stefan Monnier <[EMAIL PROTECTED]> writes:
[...]
> if I have function FOO autoloaded and (require 'blabla) replaces
> that with some other definition, than an immediately following
> (unload-feature 'blabla) should restore the autoload, no matter
> whether the autoload was pointing to blabla.el o
Kim F. Storm wrote:
> Feature freeze ?
[...]
> Can people please work on completing the release...
This prompts me to ask, when were the details of a feature freeze
agreed upon? I'm not trying to be provocative, but rather to suggest
that one reason for the continued delay is (IMO), lack of a cle
David Kastrup <[EMAIL PROTECTED]> writes:
[...]
> Well, the idea explored a bit later later was that "load" will record
> autoloads, but not do anything with them by itself, instead letting
> "provide" handle it.
Ah, now I understand your post. I think letting provide record
autoloads is a bad
> From: [EMAIL PROTECTED] (Kim F. Storm)
> Date: Sun, 24 Apr 2005 20:42:47 +0200
> Cc: Juri Linkov <[EMAIL PROTECTED]>, emacs-devel@gnu.org
>
> "Eli Zaretskii" <[EMAIL PROTECTED]> writes:
>
> > =>wd.c:5: warning: implicit declaration of function `bar'
>
> On text terminals, the overlay-arrow i
Masatake YAMATO <[EMAIL PROTECTED]> writes:
> I found a following line in the definition of `tags-search':
>
>(setq tags-loop-scan `(re-search-forward ',regexp nil t)
>
> Could you tell me why "'" is needed before "," ?
Because the form is passed to eval, which evaluates the function argument
"Eli Zaretskii" <[EMAIL PROTECTED]> writes:
> =>wd.c:5: warning: implicit declaration of function `bar'
> Notice the overlay arrow that covered part of the file name: this is a
> bug, IMHO. If we want to have an arrow pointing out the current line,
> we should indent the buffer text to the rig
Richard Stallman <[EMAIL PROTECTED]> writes:
> I introduced a new face, font-lock-comment-delimiter-face,
> to make it possible to customize separately the fontification
> of comment delimiters and comment text. I also set up Rmail
> and Sendmail modes to use this. However, lots of other modes
On Apr 22, 2005, at 10:36 PM, John Owens wrote:
Andrew Beekhof gmail.com> writes:
Hi All,
It appears that 10.4 has changed enough compared to 10.3.x to break
Emacs.
I can confirm this is a problem and wanted to detail my similar
workaround.
1) Comment out select_and_poll_event and sys_select fun
I found a following line in the definition of `tags-search':
(setq tags-loop-scan `(re-search-forward ',regexp nil t)
Could you tell me why "'" is needed before "," ?
Is there any strong reason?
I think it is easier to read next line:
(setq tags-loop-scan `(re-search-forward ,regexp nil t
On Sun, 24 Apr 2005, Robert J. Chassell wrote:
>On 24 Apr 2005, Daniel Brockman wrote,
>I've always found it annoying that Emacs seems to have a habit of
>leaving junk windows around whenever you invoke something ...
>Most often, I just want to bury the buffer, not delete it. Your two
>
I saw a strange behavior of emacs-21.3 on FreeBSD-ia64.
% uname -a
FreeBSD pluto2.freebsd.org 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Sun Apr 24
01:29:20 UTC 2005 [EMAIL PROTECTED]:/q/obj/q/6.x/src/sys/PLUTO2 ia64
(emacs-version)
=> "GNU Emacs 21.3.1 (ia64-unknown-freebsd6.0) of 2005-04-24 on
p
These recent changes:
(backup-buffer-copy, basic-save-buffer-2): Take care against
writing thru an unexpected existing symlink.
break saving of precious files (those for which file-precious-flag is
non-nil): Emacs always says that it cannot backup the file, and tries
to back it up
Ken Raeburn <[EMAIL PROTECTED]> writes:
> On Apr 23, 2005, at 13:37, Jérôme Marant wrote:
>> Hmm, one question though: why isn't it necessary to redefine constants
>> like BITS_PER_LONG, BITS_PER_EMACS_INT, EMACS_INT and so on, as done in
>> the (for instance) AMD64 port file?
>
> I don't think it
On 24 Apr 2005, Daniel Brockman wrote,
I've always found it annoying that Emacs seems to have a habit of
leaving junk windows around whenever you invoke something ...
Most often, I just want to bury the buffer, not delete it. Your two
examples of buffers you want to delete are buffers I
A couple of weeks ago, a change to compile.el introduced an overlay
arrow into buffers created by compile.el: the overlay arrow now marks
the current line in the compilation buffer. (Here, ``current line''
means the line whose locus is displayed in the other window;
next-error and mouse-1 change t
Here is a jumbo patch for the "clean up flymake.el" entry in
FOR-RELEASE.
It removes the `flymake-get-buffer-*' and `flymake-set-buffer-*'
helper functions, a pretty strange coding convention that flymake.el
uses for setting local variables. The trouble is that 99% of these
functions are called i
> From: Richard Stallman <[EMAIL PROTECTED]>
> Date: Sat, 23 Apr 2005 18:51:38 -0400
>
> I introduced a new face, font-lock-comment-delimiter-face,
> to make it possible to customize separately the fontification
> of comment delimiters and comment text. I also set up Rmail
> and Sendmail modes t
I didn't yet have time to try the version of RMAIL with separate faces
for comment delimiter and comment text, so what's below might not
happen there.
With the version of RMAIL from yesterday morning (GMT), fontification
of cited messages is wrong when more than one level of citations is
present.
35 matches
Mail list logo
