gmane.emacs.devel

dhruva | 20 Aug 05:31

Requesting bzr repository of emacs on savannah

Hello,
 I have been using the bzr repository of emacs from: http://bzr.notengoamigos.org/emacs/trunk/. I am
using the development version of bzr and things have improved in terms of performance. I have also been
lurking on the #bzr IRC channel and see a lot of positive vibes and focus on improving performance.
 At this juncture, I request (once again) to the emacs maintainers to request savannah hackers to setup a
read only bzr repository for emacs. I did chat on the #savannah on IRC and was told that the project
maintainers need to make a request and they can easily do it.
 The main reason I am making this request is that connectivity to "bzr.notengoamigos.org" is slow and
affects the perception of bzr user. From 2 days, my connection is breaking mid way and prevents me from
pulling changes. I am looking for something more reliable.

with best regards,
dhruva

      Cricket on your mind? Visit the ultimate cricket website. Enter http://in..sports.yahoo.com/cricket/

headers

Kim F. Storm | 20 Aug 01:28

New word-wrap feature and continuation fringe bitmaps


I wondered whether it is by design or mistake that when the word-wrap
feature is enable, and a word is too wide (and thus has to be split
in the middle) the continuation fringe bitmaps (typically -> and <-)
are not shown.

E.g. do C-h C-n and turn on word-wrap in the buffer, and narrow it
down to 10 columns or so...

--

-- 
Kim F. Storm <storm <at> cua.dk> http://www.cua.dk

headers

Lennart Borgman (gmail | 19 Aug 23:24

Bug report about server-ensure-safe-dir

I got a bug report on about server-ensure-safe-dir which I think might
reflect a general problem on w32. It looks like file ownership and
roaming profiles are involved.

Could someone who knows more about roaming profiles than me please have
a look at this? The bug report is here:

http://www.emacswiki.org/cgi-bin/wiki?action=browse;diff=2;id=EmacsW32#toc39

Scroll down to the end of it, just before the "Problems" header.

headers

Chong Yidong | 19 Aug 23:02

Re: 23.0.60; substitute-command-keys incorrect for self-insert-command

> emacs -Q
> In *scratch* buffer, type this, then use C-x C-e after it:
> (princ (substitute-command-keys "\\{global-map}") (current-buffer))
> 
> You will see this:
> 
> key             binding
> ---             -------
> 
> \200 .. \377 self-insert-command
> 
> The bug is that the \200 and the \377 are treated differently. The \200
> is a single octal character; the \377 is four characters, \, 3, 7, 7.

I believe this is simply how the Lisp printer behaves.  Note that
string_count_byte8 is zero for \200, but one for \377; hence \200 is
printed literally, while \377 is converted into an escaped string.

Using `insert' rather than `princ' probably gives the result you want.

I'm no expert on this area, though, so maybe someone else could comment
more authoritatively.

headers

T. V. Raman | 19 Aug 15:26

lazy-completion-table: info documentation incomplete?

The * basic completion: node in the info manual appears to end
rather abruptly for the example of lazy-completion-table.

Also, grepping in the sources for lazy-completion-table in
emacs/lisp shows places in vc-cvs.el and vc-git.el  
where a completion var is defined using lazy-completion-table,
but that var doesn't appear to get used anywhere.

--

-- 
Best Regards,
--raman

      
Email:  raman <at> users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv <at> gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs

headers

İsmail Dönmez | 19 Aug 12:18

[PATCH] XCloseDisplay already calls XrmDestroyDatabase

Hi,

Running on Ubuntu's upcoming Intrepid release I experienced X crashes
when I quit emacsclient. The gdb log shows XrmDestroyDatabase() is the
failing line. Looking at

src/xterm.c lines around about 10514:

#ifndef USE_X_TOOLKIT   /* I'm told Xt does this itself.  */
#ifndef AIX            /* On AIX, XCloseDisplay calls this.  */
  XrmDestroyDatabase (dpyinfo->xrdb);
#endif
#endif

So this code assumes only on AIX XCloseDisplay itself calls
XrmDestroyDatabase but this doesn't seem to be the case, looking at
libX11 1.1.4 source code,

src/OpenDis.c starting line 832:

    822     /* if RM database was allocated by XGetDefault() free it */
    823     if (dpy->db && (dpy->flags & XlibDisplayDfltRMDB))
    824         XrmDestroyDatabase(dpy->db);

this is from the _XFreeDisplayStructure() function and the function
documentation says:

 /* XFreeDisplayStructure frees all the storage associated with a
  * Display.  It is used by XOpenDisplay if it runs out of memory,
  * and also by XCloseDisplay.

(Continue reading)

headers

Ivan Kanis | 19 Aug 09:45

Proposal for a new API to fullscreen

Hello,

By fullscreen I mean no taskbar, emacs take all the screen estate.

The current way to switch to this mode is 

(set-frame-parameter nil 'fullscreen 'fullboth)

However this is very ambiguous, it does fullscreen on Gnome and
maximise on Mac and Windows.

I propose a new API to solve the ambiguity:

(fullscreen-mode 1)

Turns on fullscreen mode. We can set a variable of the same name to
check the state. Remove the hook mode in Gnome that should not really
be there.

What do people think? I am willing to spend time coding it.

Thank you in advance for your comments.
--

-- 
Ivan
http://kanis.fr

To live is so startling it leaves little time for anything else.
    -- Emily Dickinson

(Continue reading)

headers

Miles Bader | 19 Aug 07:24

more default-fonts-with-multiple-frames brokenness

(1) start emacs -Q

(2) select menu item: options > set default font

(3) select some other font, e.g. "courier new" (the exact font doesn't
    seem to matter) and hit "OK"

(4) create a new frame with: C-x 5 2

On my system, this always results in the new frame's default font being
bold+italic (the original frame had a normal non-italic, non-bold font,
both before and after using "options > set default font").  If I then
try to use "options > set default font" again in the new frame to fix
it, I can't (I can select a new non-italic, non-bold font and hit OK,
but it has no effect).

The behavior only seems to happen after I've changed the default font in
the original frame (if I make a new frame without doing that, there's no
problem).  It doesn't seem to depend on the exact font either; the same
thing seems to happen with all the fonts I've tried.

Thanks,

-Miles

--

-- 
Would you like fries with that?

headers

T. V. Raman | 19 Aug 05:20

docfix: minibuffer.el line 133

The documentation for function completion-table-dynamic in file
minibuffer.el 
still refers to the older dynamic-completion-table on line 133. 

--

-- 
Best Regards,
--raman

      
Email:  raman <at> users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv <at> gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs

headers

Paul Michael Reilly | 19 Aug 02:34

Rmail, IMAP and movemail.mailutils

I suspect there is a sordid history here but Google is not revealing it. 
  I want to access my IMAP server to process my mail and according to 
the documentation for Emacs movemail, it only handles POP whereas Gnu 
Mailutils has a version of movemail that does handle IMAP.  Now why 
would we not want to provide IMAP access for Rmail out of the box?  I 
certainly do.  Is there some history here I should be aware of?  I'm 
inclined to figure out what is necessary to add to Emacs movemail so 
that it can fetch IMAP mail.  I do realize that adding IMAP support to 
Rmail is more complex than the initial fetch, but it certainly is a good 
place to start.  No?

-pmr

headers

Kim F. Storm | 18 Aug 23:09

Misc problems with INSTALL file


I noticed the following stuff in INSTALL which should be fixed:

> To take proper advantage of Emacs 21's mule-unicode charsets, you need
> a suitable font.  For `Unicode' (ISO 10646) fonts for X, see

Emacs 21 should be just Emacs.

Do we still speak of "mule-unicode" ?

> (This is for a Unix or Unix-like system.  For MS-DOS and Windows 3.X,
> see below; search for MSDOG.  For Windows 9X, Windows ME, Windows NT,

There is no MS-DOS or W3x support in Emacs 23 - right?

> Installation on MSDOG (a.k.a. MSDOS)
>
> [...]

Ditto - so this whole section should be removed - right ?

I know that Eli does not want to kill MSDOG support, but IIUC
in the current state [feature freeze - release just around the corner],
Emacs 23 does not run on MSDOG. 

That needs to be announced in NEWS too.

--

-- 
Kim F. Storm <storm <at> cua.dk> http://www.cua.dk

(Continue reading)

Mon	Tue	Wed	Thu	Fri	Sat	Sun

				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30	31