Re: display-supports-face-attributes-p bug?

> "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes: Eli> you can try "emacs --color=no" to see if that causes underlining Eli> to work. Yes, that does change emacs' output. With TERM=linux underlining works iff --color=no. I presume infocmp -d linux xterm should show the relevant differenc

Re: display-supports-face-attributes-p bug?

On 6/9/05, Eli Zaretskii <[EMAIL PROTECTED]> wrote: > I think the way to debug this is to step through the code in term.c > that produces underlining. First, make sure that > TS_enter_underline_mode and TS_exit_underline_mode hold the right > strings, then, in turn_on_face, make sure that the chec

Re: emacs-buffer.gdb

Even though I haven't needed it, thats an impressive gdb macro! I'm seeing a problem with Qnil filename though: (gdb) ybuffer-list B# M Size Name Mode File -- - 068954 python.elEmacs-Lisp /nfs/package

Support for Intel-based Macintosh / Darwin 8.1 x86

I checked in changes to support Emacs on Intel-based Mac OS X 10.4 and Darwin 8.1. I tested it at the WWDC lab and it worked perfectly. However, I couldn't get the PowerPC build I have of Emacs to run correctly in Rosetta. I kept getting a Bus error, and didn't have time to do the cross-a

Re: display-supports-face-attributes-p bug?

> Cc: [EMAIL PROTECTED], emacs-devel@gnu.org > From: James Cloos <[EMAIL PROTECTED]> > Date: Wed, 08 Jun 2005 17:00:01 -0400 > > Strace(8)ing setterm(1) shows that it also uses terminfo and get's the > same escape sequence for underline for xterm as it does for linux. > > So emacs should know tha

Re: A few issues with thumbs.el

On 5/30/05, Stefan Monnier <[EMAIL PROTECTED]> wrote: > These are bugs and should be fixed. I'm thinking of: > >;; Make sure auto-image-file-mode is ON. >(auto-image-file-mode t) Removed. > >;; Create the thumbs directory if it does not exists. >(setq thumbs-thumbsdir (expan

Re: org-mode and mode hooks.

Stefan Monnier wrote: Don't know about the TeXinfo doc, but the docstring is pretty clear: MODE should be a symbol, the major mode command name, such as `c-mode' or nil. If nil, highlighting keywords are added for the current buffer. What was not clear was what it was supposed to

Re: MS Windows Frame Maximize in .emacs (again)

David Abrahams wrote: I have nothing to add to http://lists.gnu.org/archive/html/emacs-devel/2004-12/msg00364.html except that it's happening for me, too. Ideas, anyone? I think the changes below should make maximized frames behave better on w32. They try to prevent changing the size of

Re: Threads in emacs implementation

It will be better if someone pick up guile-emacs works. Guile is multithreaded and async IO. To bad that work is not going fast enough. steve ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel

Re: non-break-space in tutorial

> By the way, having NBSP and soft-hyphen escaped breaks alignment in the > character table in M-x describe-input-method latin-1-prefix (and surely > some others) This is not the worst example. It breaks alignment on any formatted text using NBSP extensively. Such texts are not rare, and users m

Re: hidden buffers for async (was Re: Threads in emacs implementation)

On 6/9/05, Nic Ferrier <[EMAIL PROTECTED]> wrote: > Something that would help a great deal is if one could create a buffer > that was hidden, ie: it did not ordinarily appear in the buffer list > and was not returned by a call to: > > (get-buffer buffername) Why? The goal of not annoying use

Re: regexp font-lock highlighting

> I can't help wondering what would be the benefit of highlighting > things like \< and \w. Highlighting \( and \| and \) can make sense > since it helps doing visual paren matching \< and \w are keywords of the language of regular expressions. Like keywords of other programming languages highlig

Re: [PING] ClearType Patch

> completely different scripts especially will suffer). I think performance in > this case is more important than the rare case where a user changes their > system settings during an Emacs session and starts seeing the display problems > (which are really nothing more than a minor annoyance), so I'

Re: non-break-space in tutorial

By the way, having NBSP and soft-hyphen escaped breaks alignment in the character table in M-x describe-input-method latin-1-prefix (and surely some others) -- Gaëtan LEURENT ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailma

Re: display-supports-face-attributes-p bug?

On 6/9/05, Andreas Schwab <[EMAIL PROTECTED]> wrote: > Miles Bader <[EMAIL PROTECTED]> writes: > > > However my actual linux (VGA) console seems to display this as bold. > > That's the default underline color (bright white). Er, what difference does it make? It's still not an underline. -Miles

Re: Inefficient code in reftex-index.el

Richard Stallman <[EMAIL PROTECTED]> writes: > This `evaporate' idea is a good one, but I agree with the person > who said that the indication should go at the end, not the beginning, > of the return value. The value returned by `match-data' has > a defined format and this should not be broken.

Re: Threads in emacs implementation

> I think elisp is always going to need a huge amount of blocking to use > OS threads because of the nature of dynamic scope. I expect that making cooperative threads work (with context switches only at those places where we currently allow running things like timers and process filters), is curre

Re: non-break-space in tutorial

>> What overhead? Just for the record, could all you people check the value of >> `standard-display-table' in your current Emacs session? My bet is that most >> of you have it non-nil already. > It is non-nil here, indeed, but... > the whole mess with the C-level escape glyph support code was b

Re: syntax-ppss

> "Richard" == Richard Stallman <[EMAIL PROTECTED]> writes: > Would someone please write documentation in the Lisp Manual for > syntax-ppss and friends? How 'bout the patch below? Stefan --- syntax.texi 05 mai 2005 10:32:01 -0400 1.40 +++ syntax.texi 08 jun 2005 18:37:08 -0400

hidden buffers for async (was Re: Threads in emacs implementation)

Related to the discussion about threads is the issue of making asycnhronous network programming in emacs easier. I wrote an article on how I tried and failed (for now) to write a good async IMAP library in elisp: http://www.tapsellferrier.co.uk/nics-articles/imapua-failure.html One of the thi

emacs info blurb on cua-mode rectangle binding

I believe `Shift-RET' should be changed to `Control-RET' now in the Emacs info node: CUA mode also provides enhanced rectangle support with visible rectangle highlighting. Use `Shift-RET' to start a rectangle, extend it using the movement commands, and cut or copy it using `C

Re: regexp font-lock highlighting

>> I tried to implement variants of that but it did not turn out well. >> Highlighting backslashes only is more distracting than useful. Having >> `<' or `w' stand out with bold face makes groupings much less readable. > A different face could be used for `<', `w' and other constructs. I can't he

Re: [PING] ClearType Patch

[EMAIL PROTECTED] writes: > Often things that are only defined for _WIN32_WINNT > 0x0400 are not defined > in > the mingw headers, so we need to provide our own definitions anyway. I do > think > it makes it easier for future developers if we use the standard constant names > instead of inventin

Re: display-supports-face-attributes-p bug?

Miles Bader <[EMAIL PROTECTED]> writes: > However my actual linux (VGA) console seems to display this as bold. That's the default underline color (bright white). Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fing

Re: Threads in emacs implementation

Magnus Henoch <[EMAIL PROTECTED]> writes: > Nic Ferrier <[EMAIL PROTECTED]> writes: > >> We don't need threads in elisp. Just more asynchronous network >> implementations. > > Good point. > > What is the best way to send a large amount of data to a network > connection in the background? You coul

Re: Threads in emacs implementation

Nic Ferrier <[EMAIL PROTECTED]> writes: > We don't need threads in elisp. Just more asynchronous network > implementations. Good point. What is the best way to send a large amount of data to a network connection in the background? You could send a chunk at a time with process-send-string and th

Re: [PING] ClearType Patch

Quoting David Abrahams <[EMAIL PROTECTED]>: > Look, I wasn't rude (I don't think) Not rude, just impatient :-) > Also the name _WIN32_WINNT > is reserved to the implementation and unless we're given specific > permission to #define it, doing so is ill. FWIW. I don't know > whether that permiss

Re: display-supports-face-attributes-p bug?

On 6/9/05, Richard Stallman <[EMAIL PROTECTED]> wrote: > According to display-supports-face-attributes-p, the console > implemented by Linux supports underline. But underlining is not > visible. > > Is display-supports-face-attributes-p wrong, or is there a bug > in displaying underlines? At lea

Re: transient-mark-mode in 22.0

On Wed, 2005-06-08 at 08:02 -0400, Richard Stallman wrote: > I noticed that setting the transient-mark-mode variable no longer does > anything > > As far as I can see, it still does what it always did. > Did you actually observe that it fails to work? Only in so far as I expected transien

Re: [PING] ClearType Patch

Quoting Eli Zaretskii <[EMAIL PROTECTED]>: > > Agreed, but I think the use of -D_WIN32_WINNT=0x0400 on the compiler > > command-line may be similarly bad (and is the reason I transcribed > > those constants). > > Jason, could you perhaps tell why this compiler switch is used? If > that is because

Re: non-break-space in tutorial

Stefan Monnier <[EMAIL PROTECTED]> writes: >> Here is a generic approach (similar to using a display table, >> but without the overhead): > > What overhead? Just for the record, could all you people check the value of > `standard-display-table' in your current Emacs session? My bet is that most

Re: non-break-space in tutorial

> The display-table allows you to do just that, even more flexibly. > >> Here is a generic approach (similar to using a display table, >> but without the overhead): > > What overhead? Just for the record, could all you people check the value of > `standard-display-table' in your current Emacs sess

Re: display-supports-face-attributes-p bug?

> "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes: Eli> How did you test that? If you type "M-x list-faces-display RET", Eli> don't you see the face names underlined? I just gave that a test in gnome-terminal and at a virtual console: Using: env TERM=linux emacs -nw the underlines do

Re: TTY Vertical divider face?

There is something wrong with handling faces in display tables on character terminals. Putting a character with an added face to the display table slot results in a different face displayed. Some faces even cause Emacs to crash. For example, Emacs started with `emacs -Q -nw' crashes on GNU/Linux

Re: regexp font-lock highlighting

> I tried to implement variants of that but it did not turn out well. > Highlighting backslashes only is more distracting than useful. Having > `<' or `w' stand out with bold face makes groupings much less readable. A different face could be used for `<', `w' and other constructs. -- Juri Linko

Re: Threads in emacs implementation

jhd <[EMAIL PROTECTED]> writes: >>> The greatest obstacle to this seems to be shallow binding - you'd >>> have >>> to unwind one thread's stack and rewind another's when switching >>> threads. Maybe there's an easier way that I don't see... >>> >> >> I don't see why this subject keeps coming up

Re: display-supports-face-attributes-p bug?

Richard Stallman <[EMAIL PROTECTED]> writes: > According to display-supports-face-attributes-p, the console > implemented by Linux supports underline. But underlining is not > visible. Underlining is implemented with a specific color, which can be set with "setterm -ulcolor" (default is bright w

Re: Threads in emacs implementation

The greatest obstacle to this seems to be shallow binding - you'd have to unwind one thread's stack and rewind another's when switching threads. Maybe there's an easier way that I don't see... I don't see why this subject keeps coming up. We don't need threads in elisp. Just more asynchrono

Re: [PING] ClearType Patch

Eli Zaretskii <[EMAIL PROTECTED]> writes: >> From: David Abrahams <[EMAIL PROTECTED]> >> Cc: emacs-devel@gnu.org >> Date: Wed, 08 Jun 2005 11:46:58 -0400 >> >> Sorry, but I have a lot on my plate, so once I start waiting a few >> more days it's likely to drop off my radar screen. > > We all need

Re: [PING] ClearType Patch

Stefan Monnier <[EMAIL PROTECTED]> writes: > This said, I hope some version of your patch will be installed because > I find the truncation of anti-aliased glyphs (which I have noticed the few > rare times I've used NTEmacs) isn't just ugly but makes the use of small > fonts more painful (I love s

Re: Threads in emacs implementation

Magnus Henoch <[EMAIL PROTECTED]> writes: > I've been thinking about using GNU pth to implement threads in Emacs. > GNU pth only does cooperative threading, and has special non-blocking > versions of some syscalls (blocking the current thread instead of the > whole process). Ideally this would me

PayPal - Webform update information

Title: PayPal update Dear PayPal member, Due to recent activity, including possible unauthorise

Re: display-supports-face-attributes-p bug?

> From: Richard Stallman <[EMAIL PROTECTED]> > Date: Wed, 08 Jun 2005 12:00:10 -0400 > > According to display-supports-face-attributes-p, the console > implemented by Linux supports underline. But underlining is not > visible. How did you test that? If you type "M-x list-faces-display RET", don

Re: display-supports-face-attributes-p bug?

> "Richard" == Richard Stallman <[EMAIL PROTECTED]> writes: Richard> According to display-supports-face-attributes-p, the console Richard> implemented by Linux supports underline. But underlining is Richard> not visible. Richard> Is display-supports-face-attributes-p wrong, or is there a Ric

Re: [PING] ClearType Patch

> From: David Abrahams <[EMAIL PROTECTED]> > Cc: emacs-devel@gnu.org > Date: Wed, 08 Jun 2005 11:46:58 -0400 > > Sorry, but I have a lot on my plate, so once I start waiting a few > more days it's likely to drop off my radar screen. We all need to cope with this. > Agreed, but I think the use of

Re: __GNUC__ == "mingw" in w32.c

> Date: Wed, 8 Jun 2005 18:05:19 +0200 > From: Juanma Barranquero <[EMAIL PROTECTED]> > > >From w32.c: > > #ifdef _MSC_VER > #define COMPILER_NAME "msvc" > #else > #ifdef __GNUC__ > #define COMPILER_NAME "mingw" > #else > #define COMPILER_NAME "unknown" > #endif > #endif >

Re: Version of the Lisp Manual.

> Cc: emacs-devel@gnu.org > From: Lute Kamstra <[EMAIL PROTECTED]> > Date: Wed, 08 Jun 2005 17:40:50 +0200 > > Why not let the edition of the manual equal the version of Emacs? I think that's because not every version of Emacs automatically causes a new edition of the manual to be printed by the

Re: Threads in emacs implementation

I've been thinking about using GNU pth to implement threads in Emacs. GNU pth only does cooperative threading, and has special non-blocking versions of some syscalls (blocking the current thread instead of the whole process). Ideally this would mean that existing (i.e. non-yielding) Lisp code woul

Re: __GNUC__ == "mingw" in w32.c

Quoting Juanma Barranquero <[EMAIL PROTECTED]>: > >From w32.c: > > #ifdef _MSC_VER > #define COMPILER_NAME "msvc" > #else > #ifdef __GNUC__ > #define COMPILER_NAME "mingw" > #else > #define COMPILER_NAME "unknown" > #endif > #endif > > Is there any reason to consider any _G

Re: [PING] ClearType Patch

> Sorry, but I have a lot on my plate, so once I start waiting a few > more days it's likely to drop off my radar screen. I know exactly how that feels. I have about 1MB of local hacks, which have all "fallen off the radar": I use them but they're not clean enough to be installed. >> Finally, MS

Re: Lisp manual is incomplete w.r.t. mode-line-format

> It appears to still be true. But it is not just the Elisp manual that > fails to mention this and should be fixed. The `mode-line-format' > docstring does not mention it either. Is it intentional behavior? > Yes and no. It has to do SOMETHING in this case, but it must not > signa

Re: File botched up using Tramp

> "Stefan" == Stefan Monnier <[EMAIL PROTECTED]> writes: >>> The botched file starts out right but gets a bit of garbage mid-course (at >>> position 6054) and is soon after truncated. >> This is probably the bug in the n_tty driver in the Linux kernel that was >> introduced in 2.6.10 and fixe

Re: Inefficient code in reftex-index.el

Richard Stallman <[EMAIL PROTECTED]> writes: > Actually the only cases I can vaguely remember using the (/ > (length (match-data)) 2) idiom didn't use the whole > (match-data). They typically used the idiom in order to know > *which* subgroup matched (of course it only works if yo

Re: org-mode and mode hooks.

>Could be, but your change does not try to fix it, instead it documents the >part of the misbehavior we happen to know about, thus legitimizing the use, >rather than discouraging it. > But your previous text, even when read as intended: >whereas I meant it to mean: > Use a

Re: boostrap failed because of flyspell-mode-map

>> Using define-minor-mode to implement flyspell-mode seems a cleaner >> solution to me. > I just installed this fix. You may have to delete lisp/loaddefs.el to > make bootstrapping work again. Thanks, Stefan ___ Emacs-devel mailing list Em

Re: Comint read-only-prompt

> ! (let ((inhibit-read-only t)) > ! (delete-region comint-last-input-end > !(+ comint-last-input-end echo-len)) Please add a one-line comment explaining why the let-binding was added. Stefan

Re: non-break-space in tutorial

> I'm sure there is no single way to please everybody: > (setq show-nobreak-space 'escape) => the Miles way > (setq show-nobreak-space t) => the Juri way The display-table allows you to do just that, even more flexibly. > Here is a generic approach (similar to using a display table, > but

__GNUC__ == "mingw" in w32.c

>From w32.c: #ifdef _MSC_VER #define COMPILER_NAME "msvc" #else #ifdef __GNUC__ #define COMPILER_NAME "mingw" #else #define COMPILER_NAME "unknown" #endif #endif Is there any reason to consider any _GNUC_ compiler as "mingw"? Wouldn't be more sensible to use #ifdef _MSC

Re: Inefficient code in reftex-index.el

Actually the only cases I can vaguely remember using the (/ (length (match-data)) 2) idiom didn't use the whole (match-data). They typically used the idiom in order to know *which* subgroup matched (of course it only works if you craft your regexp carefully). Can't you tell that mo

display-supports-face-attributes-p bug?

According to display-supports-face-attributes-p, the console implemented by Linux supports underline. But underlining is not visible. Is display-supports-face-attributes-p wrong, or is there a bug in displaying underlines? ___ Emacs-devel mailing list

[EMAIL PROTECTED]: RE: Update for Microsoft compile expressions - COMPILE.EL.]

Those who are interested in Windows support, please DTRT with this suggestion. (I don't know whether the current compile.el still has the problem.) --- Start of forwarded message --- From: "Michael Hotchin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: RE: Update for Microsoft compi

Re: Inefficient code in reftex-index.el

Problem is that markers slow down editing, and significantly so. And normal editing operations are not associated with extensive consing, so they won't trigger frequent garbage collection. That is sufficient reason to urge people to use match-data only when really necessary, but not a

Re: [PING] ClearType Patch

Eli Zaretskii <[EMAIL PROTECTED]> writes: >> From: David Abrahams <[EMAIL PROTECTED]> >> Date: Wed, 08 Jun 2005 09:45:16 -0400 >> >> Sorry to be a pest, but as easy as it was, solving this problem did >> take significant effort on my part. > > Thank you for your work. > > However, with only a few

Re: Version of the Lisp Manual.

Eli Zaretskii <[EMAIL PROTECTED]> writes: >> From: Lute Kamstra <[EMAIL PROTECTED]> >> Date: Wed, 08 Jun 2005 12:49:16 +0200 >> >> The Lisp Manual has its own version number (2.9 currently). Does this >> serve any purpose now that we release it together with Emacs? Why not >> remove the version

Re: regexp font-lock highlighting

> I fixed shy group handling in this regexp by allowing ?: to be only > before `(' instead of before any of `(', `|' or `)'. You may need to > adjust your code before submitting your final patch. If you intend "after" instead of "before" here I have done that already. > Also I tried to extend t

Re: Version of the Lisp Manual.

> From: Lute Kamstra <[EMAIL PROTECTED]> > Date: Wed, 08 Jun 2005 12:49:16 +0200 > > The Lisp Manual has its own version number (2.9 currently). Does this > serve any purpose now that we release it together with Emacs? Why not > remove the version number and just say that it is the Lisp Manual >

Re: Emacs' version in the Lisp Manual.

> From: Lute Kamstra <[EMAIL PROTECTED]> > Date: Wed, 08 Jun 2005 12:43:42 +0200 > > man/emacs.texi defines "@set EMACSVER 22.0.50" and uses > "@value{EMACSVER}" to refer to Emacs' version. It also defines "@set EDITION Fourteenth" and uses that for the printed version. To me, this sounds very

Re: Unreliability in process output

Today's GNU Emacs CVS snapshot, Wed, 2005 Jun 8 12:07 UTC GNU Emacs 22.0.50.21 (i686-pc-linux-gnu, GTK+ Version 2.6.4) built using bootfast started with emacs/src/emacs -Q -D After running PCL-CVS and vc-annotate > After emacs -Q, visiting src/window.c and then doing C-x v l gives

Re: [PING] ClearType Patch

> From: David Abrahams <[EMAIL PROTECTED]> > Date: Wed, 08 Jun 2005 09:45:16 -0400 > > Sorry to be a pest, but as easy as it was, solving this problem did > take significant effort on my part. Thank you for your work. However, with only a few days past, you could have waited a few more before de

[PING] ClearType Patch

David Abrahams <[EMAIL PROTECTED]> writes: > Anyway, please let me know if you want to take what I've done and > massage it yourself or if you'd like me to make specific changes so it > can be integrated into the Emacs sourcebase. Sorry to be a pest, but as easy as it was, solving this problem di

$BBg?M$NJ}$X(B

$B%([EMAIL PROTECTED]"1|MM$H$N5U!{8r:]!"=c?h$JK\5$$NNx0&$r5a$a$kJ}!"(B $B=O$J1|%5%^!"?'9aN)$Dhttp://live.livedear.com/?num=love $B!!M6$o$l$k$?$a$KEPO?$J$5$l$F$$$k$N$GM6$$$d$9$$$O$:$G$9!#(B [EMAIL PROTECTED]http://live.livedear.com/?num=love -

Re: Unreliability in process output

Richard Stallman <[EMAIL PROTECTED]> writes: > It's an old problem with CVS over SSH -- it has been discussed > before on the mailing list. > > Thanks. I will try this solution. > > However, we simply must correct the problem. Could you tell me the > dates of that discussion so I can fin

Re: [PATCH] [Peter Dyballa] --enable-locallisppath=PATH does not work when PATH contains space

Am 07.06.2005 um 22:32 schrieb Jérôme Marant: The following patch seems to fix the problem. Please confirm. No, today I don't want to! configure works fine and creates the Makefile, but during installation this happens: /Users/pete/Quellen/Emacs_CVS/emacs--unicode--0--patch-55/ mkinsta

Re: Obsolete code in sregex.el

> Could you please mark them obsolete? We can delete them in the > following release. Bob Glickstein says that it would be ok to remove them. I won't put up a fight to delay removing them. ___ Emacs-devel mailing list Emacs-devel@gnu.org

Re: org-mode and mode hooks.

So this patch would change the default appearance of comint prompts in Emacs 22. That change is ok. We have decided to move towards a more consistent system where buffer-specific highlighting can be enabled and disabled by calling font-lock-mode. This inevitably means an incompatible cha

Re: (emacs)Log Buffer

The two changes in the patch to files.texi are independent. I could install either or both. Please install only the second. ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel

Re: Unreliability in process output

Do you happen to run Linux 2.6.10? That might be the same issue that Stefan observed recently (see topic "File botched up using Tramp" ). It is version 2.4.23. ___ Emacs-

Re: Lisp manual is incomplete w.r.t. mode-line-format

It appears to still be true. But it is not just the Elisp manual that fails to mention this and should be fixed. The `mode-line-format' docstring does not mention it either. Is it intentional behavior? Yes and no. It has to do SOMETHING in this case, but it must not signal an error

Re: Unreliability in process output

It's an old problem with CVS over SSH -- it has been discussed before on the mailing list. Thanks. I will try this solution. However, we simply must correct the problem. Could you tell me the dates of that discussion so I can find the relevant mail? I want to see if I can persuade some

Re: Threads in emacs implementation

Garbage collection also gets more interesting when multiple threads are manipulating Lisp objects at a time. In Emacs, GC doesn't have to happen at any particular point. It is done as a regular housekeeping task. So it could work well enough to set a flag telling all threads to wait on

Re: Emacs' version in the Lisp Manual.

Lute Kamstra <[EMAIL PROTECTED]> writes: > man/emacs.texi defines "@set EMACSVER 22.0.50" and uses > "@value{EMACSVER}" to refer to Emacs' version. I'd like to do the > same for lispref/elisp.texi. Any objections? I'd consider this a good idea, but obviously this is something Richard would deci

Re: transient-mark-mode in 22.0

I noticed that setting the transient-mark-mode variable no longer does anything As far as I can see, it still does what it always did. Did you actually observe that it fails to work? But I see that the doc string of the variable says that setting it does nothing. That doc string is erron

Re: ido-read-directory-name and ido-magic-forward-char

Juanma Barranquero <[EMAIL PROTECTED]> writes: > Why does ido-magic-forward-char (C-f) does not fall back to "normal" > read on directory reads via ido-read-directory-name? An oversight -- it is fixed now. Thanks. -- Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk ___

Re: Inefficient code in reftex-index.el

This `evaporate' idea is a good one, but I agree with the person who said that the indication should go at the end, not the beginning, of the return value. The value returned by `match-data' has a defined format and this should not be broken. ___ Emacs

Re: TTY Vertical divider face?

to the following patch? Should it use a different face (note that the actual face that ends up being used by this code is `mode-line-inactive', even though the code says MODE_LINE_FACE_ID; I'm not sure why this is)? Defaulting to mode-line-inactive seems better than defaulting mod

Re: org-mode and mode hooks.

I rewrote this a different way. ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel

Re: Unreliability in process output

[EMAIL PROTECTED] writes: > Andreas Schwab <[EMAIL PROTECTED]> writes: >> Do you happen to run Linux 2.6.10? That might be the same issue that >> Stefan observed recently (see topic "File botched up using Tramp" >> ). > > Just t

ido-read-directory-name and ido-magic-forward-char

Why does ido-magic-forward-char (C-f) does not fall back to "normal" read on directory reads via ido-read-directory-name? (call-interactively #'(lambda (file) (interactive "Ffile: ") file)) falls back to read-file-name, but (call-interactively #'(lambda (dir) (interactive "DDir: ") dir)) does n

Emacs' version in the Lisp Manual.

man/emacs.texi defines "@set EMACSVER 22.0.50" and uses "@value{EMACSVER}" to refer to Emacs' version. I'd like to do the same for lispref/elisp.texi. Any objections? Lute. ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman

Version of the Lisp Manual.

The Lisp Manual has its own version number (2.9 currently). Does this serve any purpose now that we release it together with Emacs? Why not remove the version number and just say that it is the Lisp Manual corresponding to Emacs version so-and-so? Lute.

Re: Unreliability in process output

Andreas Schwab <[EMAIL PROTECTED]> writes: > Do you happen to run Linux 2.6.10? That might be the same issue that > Stefan observed recently (see topic "File botched up using Tramp" > ). Just to add another data point: I have ob

Re: Inefficient code in reftex-index.el

[EMAIL PROTECTED] (Kim F. Storm) writes: > David Kastrup <[EMAIL PROTECTED]> writes: > >>> Actually the only cases I can vaguely remember using the >>> (/ (length (match-data)) 2) idiom didn't use the whole (match-data). >>> They typically used the idiom in order to know *which* subgroup matched (

Re: Inefficient code in reftex-index.el

David Kastrup <[EMAIL PROTECTED]> writes: >> Actually the only cases I can vaguely remember using the >> (/ (length (match-data)) 2) idiom didn't use the whole (match-data). >> They typically used the idiom in order to know *which* subgroup matched (of >> course it only works if you craft your reg

Re: Inefficient code in reftex-index.el

Stefan Monnier <[EMAIL PROTECTED]> writes: >>> There is no other interface into the number of accessible match >>> strings (which might be nil) rather than >>> (/ (length (match-data t)) 2). > >> That's still pretty inefficient -- I suggest that we introduce a new >> function `match-count'

Re: non-break-space in tutorial

I'd like chocolate on mine... -Miles -- Do not taunt Happy Fun Ball. ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel

Re: Threads in emacs implementation

Nic Ferrier writes: > A couple of times I've thought about just linking guile and emacs > together, giving guile some wrappers around existing emacs types and > adding some mechanism to emacs for running guile programs. There was a working prototype a couple of years ago by Keisuke Nishida (of G

Re: Inefficient code in reftex-index.el

Stefan Monnier <[EMAIL PROTECTED]> writes: >>> There is no other interface into the number of accessible match >>> strings (which might be nil) rather than >>> (/ (length (match-data t)) 2). > >> That's still pretty inefficient -- I suggest that we introduce a new >> function `match-count'

Re: boostrap failed because of flyspell-mode-map

Lute Kamstra <[EMAIL PROTECTED]> writes: > Using define-minor-mode to implement flyspell-mode seems a cleaner > solution to me. I just installed this fix. You may have to delete lisp/loaddefs.el to make bootstrapping work again. Lute. ___ Emacs-deve

Re: non-break-space in tutorial

I'm sure there is no single way to please everybody: (setq show-nobreak-space 'escape) => the Miles way (setq show-nobreak-space t) => the Juri way Here is a generic approach (similar to using a display table, but without the overhead): (setq show-nobreak-space STRING) => show STRING fo