Richard M. Stallman | 1 Jan 03:14 2006
Picon
Picon

Re: GtkPlug patch

    XEmbed is a protocol that uses basic X mechanisms such as client
    messages and reparenting windows to provide embedding of a control from
    one application into another application.

    So, theoretically, there is nothing that stops it from being adapted the
    other X variants.

Does anyone know what we need to do
to make the Xt versions of Emacs handle XEmbed?
Richard M. Stallman | 1 Jan 03:15 2006
Picon
Picon

Re: mouse.el patch for region tracking

I have not checked it carefully, but the general idea seems ok.
If someone verifies this is correct, then please install it.
Richard M. Stallman | 1 Jan 03:15 2006
Picon
Picon

Re: TNT not working reliably in Emacs

      I've not yet tried a proxy to see if the server is responding
    in the unsuccessful cases.

It would be very useful to find a way of determining exactly
what the server sends back.  Then we would know for certain
whether the data is lost inside Emacs.

If it is, we could add some debugging code to log everything inside
the relevant asynchronous Emacs code, and that way we could fix the
bug.
Lennart Borgman | 1 Jan 03:29 2006
Picon
Picon

A happy new year with a good new release!

I wish you all that. And a lot of good things in your personal lifes of 
course!
Jan Djärv | 1 Jan 16:57 2006
Picon

Re: GtkPlug patch

Richard M. Stallman wrote:
>     XEmbed is a protocol that uses basic X mechanisms such as client
>     messages and reparenting windows to provide embedding of a control from
>     one application into another application.
> 
>     So, theoretically, there is nothing that stops it from being adapted the
>     other X variants.
> 
> Does anyone know what we need to do
> to make the Xt versions of Emacs handle XEmbed?

Since Emacs has its own event loop, the implementation for non-Xt (i.e. pure 
Xlib) would be the same as for Xt.  Like the drop part of drag and drop is now.

	Jan D.
Richard M. Stallman | 1 Jan 17:10 2006
Picon
Picon

Re: Customizing faces with `defcustom'

      I'm not sure which is better.  Since `previous-buffer' and
    `next-buffer' (that use the frame-local buffer list) currently are unfinished
    (they require more changes in C after the release) they don't work reliably,
    so maybe mouse-1 and mouse-3 in the mode line should use the global buffer
    list.  Even though it is not convenient, it exhibits predictable behavior.

I agree.  Could you fix that?
Richard M. Stallman | 1 Jan 17:10 2006
Picon
Picon

Re: Popup when buffer file is changed on disk

I am answering old mail that got forgotten during the year.

    Following Lennart's idea, I added a flag to the buffer struct
    (leaveBufferAlone) which persists the state of whether the user chose to ignore
    that the buffer file was changed on disk or not. When working with an IDE, the
    popup provides a symmetric editing experience in that emacs and the IDE notify
    the user whenever the file is changed on disk and give him/her the chance to
    ignore or revert.

This could be a useful feature, but the implementation has two flaws:

1. It is done at the C level.

2. It only works on Windows.

Our goal is to replace proprietary operating systems, not to enhance
them; therefore, we don't want to have any Emacs features that only
work on Windows.

If you or someone implements such a feature that works on the GNU
system and is mostly implemented in Lisp, then we could install it
(after the coming release).
David Reitter | 1 Jan 18:48 2006
Picon

url-cache - (require 'url)

I think url-cache.el needs a (require 'url) to define url- 
configuration-directory which is (now) needed to define url-cache- 
directory. Otherwise, a simple (require 'url-cache) fails unless url  
isn't loaded beforehand.

--Lisp error: (void-variable url-configuration-directory)
   (expand-file-name "cache" url-configuration-directory)
   eval((expand-file-name "cache" url-configuration-directory))
   custom-initialize-reset(url-cache-directory (expand-file-name  
"cache" url-configuration-directory))
   custom-declare-variable(url-cache-directory (expand-file-name  
"cache" url-configuration-directory) ("/Applications/Aquamacs  
Emacs.app/Contents/Resources/lisp/url/url-cache.elc" . -662) :type  
directory :group url-file)
   require(url-cache)
Paul Pogonyshev | 1 Jan 20:18 2006
Picon
Picon

Re: Mode_switch and LEIM

Stefan Monnier wrote:
> > b) a way to switch input methods using the same key as is used for switching
> >    XIM input methods (but this is probably way too difficult and cannot be
> >    done without hacking external software).
> 
> How does it work in XIM?

Uh, actually, I don't know.  I use KDE as desktop environment and it handles
layouts itself.  Layout switching is bound to a key combination (by default
it is Ctrl+K, but I use Win+Space) and each time the combination is pressed,
the current layout is switched to the next one from a predefined set (I have
only English and Russian in this set.)

I assume KDE just calls `setxkbmap' each time the layout is changed, at
least it shows command line for it in the `Keyboard Layout' Control Center
page.  For me it shows these two command lines:

	setxkbmap -model pc104 -layout us -variant basic
	setxkbmap -model pc104 -layout us,ru -variant ,winkeys

The first is for U.S. English, the second is for Russian.

Paul
Reiner Steib | 1 Jan 19:13 2006
X-Face

savehist-mode: invalid-read-syntax "#"

Hi,

`savehist-mode' is a very nice new feature in Emacs 22.  I like it
very much.  Thanks, Hrvoje!

Alas, from time to time `savehist-mode' saves entries containing "#"
like...

  (setq command-history '((describe-key '[(mouse-6 (#<window 14 on
  site-start.el> 41046 (293 . 354) 5470111 nil 41046 (48 . 27)
  nil (221 . 3) (6 . 13)))] 1 nil)))

... to `~/.emacs.d/history'.  The mouse-6 entry came from using `C-h
k'.  I've also seen offending entries after using "#" in with `M-!'
(shell-command-history).  When starting Emacs next, I got...

Debugger entered--Lisp error: (invalid-read-syntax "#")
  signal(invalid-read-syntax ("#"))
  byte-code("STRIPPED" [savehist-mode errvar nil savehist-uninstall signal] 3)
  savehist-mode(nil)
  call-interactively(savehist-mode)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)

Probably `savehist-mode' shouldn't try to save describe-key entries in
the first place.  And it should try to make sure that the history file
is syntactically correct.

Bye, Reiner.

(Continue reading)


Gmane