http://blog.gmane.org/gmane.emacs.bugs hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.emacs.bugs/60346 <pre>Hi, I recently switched from Emacs 23 to the current version on the emacs-24 branch (r108014) and bumped into a strange behaviour of bury-buffer at the start of a session. I'm using desktop.el and (global-set-key "\C-xy" 'bury-buffer) in .emacs (because I have a bad memory and like to bury stuff ;-). Every time I start Emacs, I see the correct buffer, i.e. the one I used before I closed Emacs previously. I edit that buffer a bit and bury it. In my case, bury-buffer switches to the wrong buffer. Instead of switching to the buffer next in line (so to speak), bury-buffer switches to what seems to be the last buffer in the list of all buffers. Here's a little example in form of a "emacs -Q" recipe: 3 C-x C-s 3 RET C-x b 2 RET 2 C-x C-s 2 RET C-x b 1 RET 1 C-x C-s 1 RET M-x desktop-save &lt;filename&gt; This should leave you with with three saved buffers in the order 1-2-3 and a desktop file. C-x C-b should be able to confirm the buffer order. Now close Emacs, start a fresh one and M-x desktop-read your desktop file. You should see buffer 1. So far, so good. Now M-x bury-buffer. I'd expect to see buffer 2 now, instead Emacs switched to buffer 3. If you C-x C-b now, you'll see that the buffer list says that buffer 2 is up front, although you're staring at buffer 3. This bug hits you only at the very beginning of a session. I can continue to bury buffers using C-x y and end up with buffers apparently from the end of the buffer list, instead of from the top. But some actions fix this, like switching a buffer once using C-x b. Afterwards the bug is nowhere to be found. The last few days I started work with a strange I-could-swear-that-wasnt-the-file-I-was-working-on-yesterday-before-I-went-home feeling :-D. Any ideas on how to get rid of that feeling are very welcome :-). Kind regards, Tobias --- In GNU Emacs 24.0.97.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.20.1) of 2012-05-25 on pen-bld-274apcl Windowing system distributor `The X.Org Foundation', version 11.0.10706000 Configured using: `configure '--prefix=...'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: POSIX value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: de_DE.utf8 value of $LANG: en_US.utf8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default enable-multibyte-characters: t Major mode: Lisp Interaction Minor modes in effect: tooltip-mode: t mouse-wheel-mode: t tool-bar-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Load-path shadows: None found. Features: (shadow sort gnus-util mail-extr emacsbug message format-spec rfc822 mml easymenu mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail regexp-opt rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils time-date tooltip ediff-hook vc-hooks lisp-float-type mwheel x-win x-dnd tool-bar dnd fontset image fringe lisp-mode register page menu-bar rfn-eshadow timer select scroll-bar mouse jit-lock font-lock syntax facemenu font-core frame cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean japanese hebrew greek romanian slovak czech european ethiopic indian cyrillic chinese case-table epa-hook jka-cmpr-hook help simple abbrev minibuffer loaddefs button faces cus-face files text-properties overlay sha1 md5 base64 format env code-pages mule custom widget hashtable-print-readable backquote make-network-process dbusbind dynamic-setting system-font-setting font-render-setting move-toolbar gtk x-toolkit x multi-tty emacs) </pre> Tobias Bading 2012-05-25T08:50:47 http://permalink.gmane.org/gmane.emacs.bugs/60345 <pre>Tags: patch This follows up on our two conversations last year on this topic. === modified file 'ChangeLog' --- ChangeLog2012-05-22 16:20:27 +0000 +++ ChangeLog2012-05-25 07:14:25 +0000 &lt; at &gt;&lt; at &gt; -1,3 +1,13 &lt; at &gt;&lt; at &gt; +2012-05-25 Paul Eggert &lt;eggert&lt; at &gt;cs.ucla.edu&gt; + +Remove the --disable-maintainer-mode option from 'configure'. +It is confusingly named and rarely useful. See, for example, +&lt;http://lists.gnu.org/archive/html/emacs-devel/2011-12/msg00089.html&gt;. +* INSTALL.BZR: Don't mention --disable-maintainer-mode. +* Makefile.in (MAINTAINER_MODE_FLAG): Remove; all uses removed. +* configure.in: Remove --disable-maintainer-mode. +(USE_MAINTAINER_MODE, MAINT): Remove. + 2012-05-22 Paul Eggert &lt;eggert&lt; at &gt;cs.ucla.edu&gt; Remove src/m/*. === modified file 'INSTALL.BZR' --- INSTALL.BZR2012-01-19 07:21:25 +0000 +++ INSTALL.BZR2012-05-25 07:14:25 +0000 &lt; at &gt;&lt; at &gt; -30,7 +30,7 &lt; at &gt;&lt; at &gt; If you want later builds to go faster, at the expense of sometimes doing the wrong thing if you update the build procedure, you can -invoke "./configure -C --disable-maintainer-mode" instead. +invoke "./configure -C" instead. Some of the files that are included in the Emacs tarball, such as byte-compiled Lisp files, are not stored in Bazaar. Therefore, to === modified file 'Makefile.in' --- Makefile.in2012-05-22 01:19:43 +0000 +++ Makefile.in2012-05-25 07:14:25 +0000 &lt; at &gt;&lt; at &gt; -66,10 +66,8 &lt; at &gt;&lt; at &gt; # ==================== Things `configure' Might Edit ==================== -MAINTAINER_MODE_FLAG = --disable-maintainer-mode -&lt; at &gt;MAINT&lt; at &gt;MAINTAINER_MODE_FLAG = --enable-maintainer-mode cache_file = &lt; at &gt;cache_file&lt; at &gt; -CONFIGURE_FLAGS = --cache-file=$(cache_file) $(MAINTAINER_MODE_FLAG) +CONFIGURE_FLAGS = --cache-file=$(cache_file) CC=&lt; at &gt;CC&lt; at &gt; CFLAGS=&lt; at &gt;CFLAGS&lt; at &gt; &lt; at &gt;&lt; at &gt; -360,16 +358,17 &lt; at &gt;&lt; at &gt; ./configure $(CONFIGURE_FLAGS); \ fi -AUTOCONF_INPUTS = &lt; at &gt;MAINT&lt; at &gt; $(srcdir)/configure.in $(srcdir)/aclocal.m4 +AUTOCONF_INPUTS = $(srcdir)/configure.in $(srcdir)/aclocal.m4 $(srcdir)/configure: $(AUTOCONF_INPUTS) cd ${srcdir} &amp;&amp; autoconf -ACLOCAL_INPUTS = &lt; at &gt;MAINT&lt; at &gt; $(srcdir)/m4/gnulib-comp.m4 +ACLOCAL_INPUTS = $(srcdir)/m4/gnulib-comp.m4 $(srcdir)/aclocal.m4: $(ACLOCAL_INPUTS) cd $(srcdir) &amp;&amp; aclocal -I m4 -AUTOMAKE_INPUTS = &lt; at &gt;MAINT&lt; at &gt; $(srcdir)/aclocal.m4 $(srcdir)/lib/Makefile.am $(srcdir)/lib/gnulib.mk +AUTOMAKE_INPUTS = $(srcdir)/aclocal.m4 $(srcdir)/lib/Makefile.am \ + $(srcdir)/lib/gnulib.mk $(srcdir)/lib/Makefile.in: $(AUTOMAKE_INPUTS) cd $(srcdir) &amp;&amp; automake --gnu -a -c lib/Makefile am--refresh: $(srcdir)/aclocal.m4 $(srcdir)/configure $(srcdir)/src/config.in === modified file 'admin/ChangeLog' --- admin/ChangeLog2012-05-22 16:20:27 +0000 +++ admin/ChangeLog2012-05-25 07:14:25 +0000 &lt; at &gt;&lt; at &gt; -1,3 +1,8 &lt; at &gt;&lt; at &gt; +2012-05-25 Paul Eggert &lt;eggert&lt; at &gt;cs.ucla.edu&gt; + +Remove the --disable-maintainer-mode option from 'configure'. +* make-tarball.txt: Don't worry about maintainer mode. + 2012-05-22 Paul Eggert &lt;eggert&lt; at &gt;cs.ucla.edu&gt; Remove src/m/*. === modified file 'admin/make-tarball.txt' --- admin/make-tarball.txt2012-02-04 22:12:14 +0000 +++ admin/make-tarball.txt2012-05-25 07:14:25 +0000 &lt; at &gt;&lt; at &gt; -28,13 +28,7 &lt; at &gt;&lt; at &gt; refer to a newer release of Emacs. (This is probably needed only when preparing a major Emacs release, or branching for it.) -5. Edit configure.in so that maintainer-mode is off by default. - (FIXME - need to find a better way of dealing with this. - Or maybe it's fine and indeed correct to leave it on? - See http://lists.gnu.org/archive/html/emacs-devel/2011-03/msg00859.html - and subsequent.) - - autoreconf -i -I m4 --force +5. autoreconf -i -I m4 --force make bootstrap 6. Commit etc/AUTHORS, all the files changed by M-x set-version, and === modified file 'configure.in' --- configure.in2012-05-22 16:20:27 +0000 +++ configure.in2012-05-25 07:14:25 +0000 &lt; at &gt;&lt; at &gt; -235,19 +235,6 &lt; at &gt;&lt; at &gt; USE_XASSERTS=$enableval, USE_XASSERTS=no) -AC_ARG_ENABLE(maintainer-mode, -[AS_HELP_STRING([--disable-maintainer-mode], - [disable make rules and dependencies not useful (and sometimes - confusing) to the casual installer])], - USE_MAINTAINER_MODE=$enableval, - USE_MAINTAINER_MODE=yes) -if test $USE_MAINTAINER_MODE = yes; then - MAINT= -else - MAINT=# -fi -AC_SUBST(MAINT) - AC_ARG_ENABLE(locallisppath, [AS_HELP_STRING([--enable-locallisppath=PATH], [directories Emacs should search for lisp files specific === modified file 'etc/ChangeLog' --- etc/ChangeLog2012-05-07 22:53:17 +0000 +++ etc/ChangeLog2012-05-25 07:14:25 +0000 &lt; at &gt;&lt; at &gt; -1,3 +1,8 &lt; at &gt;&lt; at &gt; +2012-05-25 Paul Eggert &lt;eggert&lt; at &gt;cs.ucla.edu&gt; + +Remove the --disable-maintainer-mode option from 'configure'. +* NEWS: Mention this. + 2012-05-07 Glenn Morris &lt;rgm&lt; at &gt;gnu.org&gt; * forms/forms-d2.el, forms/forms-pass.el: Move here from ../lisp. === modified file 'etc/NEWS' --- etc/NEWS2012-05-25 00:55:40 +0000 +++ etc/NEWS2012-05-25 07:14:25 +0000 &lt; at &gt;&lt; at &gt; -29,6 +29,9 &lt; at &gt;&lt; at &gt; no warnings; on older and on non-GNU systems the generated warnings may be useful. +** The configure option '--disable-maintainer-mode' has been removed, +as it was confusingly-named and rarely useful. + --- ** Emacs uses libtinfo in preference to libncurses, if available. </pre> Paul Eggert 2012-05-25T07:51:45 http://permalink.gmane.org/gmane.emacs.bugs/60344 <pre>I think the comments are very good. I wonder if it is possible for you write the patch directly? Thanks. Leo </pre> Leo 2012-05-25T02:14:50 http://permalink.gmane.org/gmane.emacs.bugs/60343 <pre> So I added this condition to the defvar. Installed, with face adjustments in diff-mode, smerge and ediff. I tested all face changes in different environments: high-color X11 with light/dark background and 8-color xterm with light/dark background. During testing I noticed that `C-M-x' doesn't work anymore on `defface'. It doesn't re-evaluate the face definition because `eval-sexp-add-defvars' in `eval-defun-2' produces an expression that can't be macroexpanded. For instance: (setq form (eval-sexp-add-defvars (read (current-buffer)))) =&gt; (progn (defvar add-log-buffer-file-name-function) (defface diff-removed (quote ((((class color)) :background "red"))) "...")) (macroexpand form) =&gt; (progn (defvar add-log-buffer-file-name-function) (defface diff-removed (quote ((((class color)) :background "red"))) "...")) The problem is that `eval-sexp-add-defvars' adds `progn' that prevents defface macro expansion. `macroexpand' can't expand `defface' to `custom-declare-face' (this is expected in `eval-defun-1'). Without `progn', `macroexpand' works correctly, e.g.: (macroexpand '(defface diff-removed (quote ((((class color)) :background "red"))) "...")) =&gt; (custom-declare-face (quote diff-removed) (quote ((((class color)) :background "red"))) "...") </pre> Juri Linkov 2012-05-25T00:57:49 http://permalink.gmane.org/gmane.emacs.bugs/60342 <pre>Sorry, that should be OS X 10.7.4, somehow didn't realize there was an OS release. </pre> Florian Ebeling 2012-05-24T22:08:29 http://permalink.gmane.org/gmane.emacs.bugs/60341 <pre> 1. (setq nxml-auto-insert-xml-declaration-flag t) 2. Visit the attached test.zip M Filemode Length Date Time File - ---------- -------- ----------- -------- ---------- drwx------ 0 25-May-2012 00:29:06 test/ -rwx------ 40 25-May-2012 00:29:06 test/a.xml - ---------- -------- ----------- -------- ---------- 40 2 files 3. Visit a.xml. Note the multiple XML declarations. &lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;?xml version="1.0" encoding="utf-8"?&gt; The original file has just a single XML declaration. The second declaration is the gratuitous declaration added due to (1). Why is nxml mode tampering with an existing XML file? 4. The problem surfaces with XML files in a ZIP archive (for example ODT files) and not with standalone XML files. In GNU Emacs 24.0.97.1 (i386-mingw-nt5.1.2600) of 2012-05-17 on MARVIN Windowing system distributor `Microsoft Corp.', version 5.1.2600 Configured using: `configure --with-gcc (4.6) --no-opt --enable-checking --cflags -ID:/devel/emacs/libs/libXpm-3.5.8/include -ID:/devel/emacs/libs/libXpm-3.5.8/src -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include -ID:/devel/emacs/libs/giflib-4.1.4-1/include -ID:/devel/emacs/libs/jpeg-6b-4/include -ID:/devel/emacs/libs/tiff-3.8.2-1/include -ID:/devel/emacs/libs/gnutls-3.0.9/include' </pre> Jambunathan K 2012-05-24T19:16:57 http://permalink.gmane.org/gmane.emacs.bugs/60340 <pre> Things are even worse than I thought. The doc string of `dired-mark-prompt' punts just as pitifully as that for `dired-mark-read-string' - the wording is even the same. What should be said about ARG and FILES for `dired-mark-prompt': "If ARG is nil then prompt to act on the number of files in FILES. If non-nil then prompt to act on the next N files, where N is the `prefix-numeric-value' of ARG." "FILES is the same as in `dired-mark-pop-up'." (or repeat the definition of FILES from `dired-mark-pop-up') </pre> Drew Adams 2012-05-24T18:39:34 http://permalink.gmane.org/gmane.emacs.bugs/60339 <pre>The doc string includes this: 1. "ARG is normally the prefix argument for the calling command." So what? That doesn't tell you anything useful. What is ARG for? What does it do? Just say that it is passed to `dired-mark-prompt'. 2. "FILES should be a list of file names." No. That kind of help is no help at all. FILES is the list of _marked_ files. 3. "DEFAULT-VALUE, if non-nil, should be a "standard" value or list of such values, available via history commands. Note that if the user enters empty input, this function returns the empty string, not DEFAULT-VALUE." The first sentence: Does it say anything useful? If so, it's not clear to me. It seems to be saying only that DEFAULT-VALUE is a default value or list of default values. It would be far clearer and actually helpful if you just said that DEFAULT-VALUE is passed to `completing-read'. IOW, do what you did for COLLECTION. Just say that INITIAL, DEFAULT-VALUE, and COLLECTION are passed to `completing-read'. That will provide a link to `completing-read', whose doc provides complete and accurate descriptions of these arguments. In GNU Emacs 24.0.97.1 (i386-mingw-nt5.1.2600) of 2012-05-16 on MARVIN Windowing system distributor `Microsoft Corp.', version 5.1.2600 Configured using: `configure --with-gcc (4.6) --no-opt --enable-checking --cflags -ID:/devel/emacs/libs/libXpm-3.5.8/include -ID:/devel/emacs/libs/libXpm-3.5.8/src -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include -ID:/devel/emacs/libs/giflib-4.1.4-1/include -ID:/devel/emacs/libs/jpeg-6b-4/include -ID:/devel/emacs/libs/tiff-3.8.2-1/include -ID:/devel/emacs/libs/gnutls-3.0.9/include' </pre> Drew Adams 2012-05-24T18:27:28 http://permalink.gmane.org/gmane.emacs.bugs/60338 <pre> My guess (based on no information) would be that this is somehow related to Unity, like http://debbugs.gnu.org/10954 </pre> Glenn Morris 2012-05-24T16:25:23 http://permalink.gmane.org/gmane.emacs.bugs/60337 <pre> No, FETCH_* macros are safe, because they accept buffer positions, fetch only one character at a time, and call STRING_CHAR_* _after_ they access the buffer. I didn't mean STRING_CHAR_*. I agree that they should be fixed not to have such unexpected side effect. They should be read-only operations. As a temporary band-aid for Emacs 24.1, I suggest the change below. What I meant is the code besides STRING_CHAR_* macros. I don't think you will find code that manipulates C pointers to buffer text and calls functions that can allocate memory. I asked Gerd Möllmann, who wrote the mmap-based buffer allocation code, about this. That code originally resided on ralloc.c and was meant to replace the sbrk-based implementation. So I would expect that the issue of relocation was considered back then, and I hope Gerd will remember why the mmap-based code was considered good enough to replace ralloc.c. This has nothing to do with Windows APIs, so you are well equipped to reason about this ;-) You said "malloc", so I took an issue with the MS C runtime implementation of malloc. Since all the other implementations suffer from fragmentation, there's no reason to believe that the MS implementation avoids that danger. A general-purpose function that cannot move buffers behind the scenes cannot possibly avoid that. Doing better was the original reason for writing ralloc.c. If you meant to bypass malloc and use the Windows memory-allocation APIs, such as VirtualAlloc, directly, then that's what we already do in w32heap.c, which implements an emulation of sbrk that is good enough for Emacs. The fact that gmalloc and ralloc are used on top of that are simply to avoid reinventing the wheel. We could easily turn off buffer relocation in ralloc.c for good, by fixing the value of use_relocatable_buffers at zero. But I'm worried that this would cause Emacs on Windows run out of memory (or act as if it were) faster. For example, in an Emacs session that runs for 2 weeks and has a 200MB working set, I just visited a 1.3GB file, went to its middle and typed "C-u 30000 d" to insert 30K characters. Emacs had no problems enlarging the buffer, although it has only 1.9GB of reserved memory space on that machine, so if it needed to allocate another 1.3GB+30KB buffer (due to fragmentation, which is a certainty after such a long time), it would have failed, I presume. Yet another alternative is to emulate mmap on Windows using the equivalent Windows API. But that requires a research comparing mmap features we need and use on Posix platforms with the features offered by Windows, to make sure this is at all feasible. Such a research would need to be done by someone who knows enough about mmap and is willing to do the job. Do we have such a person on board? And then there's the implementation and testing. Doesn't sound like an efficient use of our time and energy. Are there other alternatives? Here's the band-aid I propose for emacs-24, to make the STRING_CHAR_* macros safe: === modified file 'src/charset.c' --- src/charset.c2012-01-19 07:21:25 +0000 +++ src/charset.c2012-05-24 16:14:05 +0000 &lt; at &gt;&lt; at &gt; -1641,6 +1641,12 &lt; at &gt;&lt; at &gt; maybe_unify_char (int c, Lisp_Object val return c; CHECK_CHARSET_GET_CHARSET (val, charset); +#ifdef REL_ALLOC + /* The call to load_charset below can allocate memory, whcih screws + callers of this function through STRING_CHAR_* macros that hold C + pointers to buffer text, if REL_ALLOC is used. */ + r_alloc_inhibit_buffer_relocation (1); +#endif load_charset (charset, 1); if (! inhibit_load_charset_map) { &lt; at &gt;&lt; at &gt; -1656,6 +1662,9 &lt; at &gt;&lt; at &gt; maybe_unify_char (int c, Lisp_Object val if (unified &gt; 0) c = unified; } +#ifdef REL_ALLOC + r_alloc_inhibit_buffer_relocation (0); +#endif return c; } === modified file 'src/ralloc.c' --- src/ralloc.c2012-05-23 17:32:28 +0000 +++ src/ralloc.c2012-05-24 16:16:14 +0000 &lt; at &gt;&lt; at &gt; -1204,7 +1204,12 &lt; at &gt;&lt; at &gt; r_alloc_reset_variable (POINTER *old, PO void r_alloc_inhibit_buffer_relocation (int inhibit) { - use_relocatable_buffers = !inhibit; + if (use_relocatable_buffers &lt; 0) + use_relocatable_buffers = 0; + if (inhibit) + use_relocatable_buffers++; + else if (use_relocatable_buffers &gt; 0) + use_relocatable_buffers--; } </pre> Eli Zaretskii 2012-05-24T16:22:46 http://permalink.gmane.org/gmane.emacs.bugs/60336 <pre> The same happens for me. On the other hand the doc string for lower-frame does not say that the frame should loose focus. </pre> Lennart Borgman 2012-05-24T16:01:41 http://permalink.gmane.org/gmane.emacs.bugs/60335 <pre> Installed as bzr revision 108013 on the emacs-24 branch; I'm closing the bug. Ken </pre> Ken Brown 2012-05-24T11:24:36 http://permalink.gmane.org/gmane.emacs.bugs/60334 <pre>Please keep CCing to 11544&lt; at &gt;debbugs.gnu.org so the information you provide does not get lost. &gt; On this bug, after typing the ? first the window grows to normal size and &gt; then the window's left edge stays in place But when you type "?" on your Windows Emacs the left edge moves? Could you try comparing the return values of the function `ediff-make-frame-position' on GNU/Linux and Windows respectively? &gt; and the width decreases to about &gt; a characters width in a fairly continuous movement. So it looks like an animated variant of bug#11480. &gt; I tried emacs 23 and &gt; it does the same thing on Ubuntu precise. I use emacs on windows and have &gt; never seen this problem using ediff there if that helps. I don't have the slightest idea what's going on so I can only suggest to try the following: Locate the file ediff-wind.el (in the lisp/vc subdirectory) and try to apply the patch I attached. At least this way we should be able to find out whether doing two separate calls of `modify-frame-parameters' confuses your window manager. Thanks, martin *** lisp/vc/ediff-wind.el2012-04-26 03:04:36 +0000 --- lisp/vc/ediff-wind.el2012-05-24 08:41:17 +0000 *************** *** 1004,1010 **** (goto-char (point-min)) ! (modify-frame-parameters ctl-frame adjusted-parameters) (make-frame-visible ctl-frame) ;; This works around a bug in 19.25 and earlier. There, if frame gets --- 1004,1013 ---- (goto-char (point-min)) ! (modify-frame-parameters ! ctl-frame ! (append adjusted-parameters ! (funcall ediff-control-frame-position-function ctl-buffer fwidth fheight))) (make-frame-visible ctl-frame) ;; This works around a bug in 19.25 and earlier. There, if frame gets *************** *** 1024,1032 **** ;; Now move the frame. We must do it separately due to an obscure bug in ;; XEmacs ! (modify-frame-parameters ! ctl-frame ! (funcall ediff-control-frame-position-function ctl-buffer fwidth fheight)) ;; synchronize so the cursor will move to control frame ;; per RMS suggestion --- 1027,1035 ---- ;; Now move the frame. We must do it separately due to an obscure bug in ;; XEmacs ! ;; (modify-frame-parameters ! ;; ctl-frame ! ;; (funcall ediff-control-frame-position-function ctl-buffer fwidth fheight)) ;; synchronize so the cursor will move to control frame ;; per RMS suggestion </pre> martin rudalics 2012-05-24T09:01:45 http://permalink.gmane.org/gmane.emacs.bugs/60333 <pre> Please go ahead and install it on the emacs-24 branch (only: not on the trunk). Stefan </pre> Stefan Monnier 2012-05-24T07:01:21 http://permalink.gmane.org/gmane.emacs.bugs/60332 <pre> When I run lower-frame function in Emacs frame interactively, Emacs frame is brought behind of other application window(s) but has focus. Key inputs are passed to lowered frame. I tested 4 Windows PC, and all PCs show the same behavior. </pre> Kazuhiro Ito 2012-05-24T06:04:59 http://permalink.gmane.org/gmane.emacs.bugs/60331 <pre> You are right. I was resisting based on the idea of maintaining some sort of "purity" of the build machine, but "brew install autoconf automake" is not out of line. I've gone ahead and done it, thanks for the push. </pre> David Caldwell 2012-05-24T02:25:28 http://permalink.gmane.org/gmane.emacs.bugs/60330 <pre> It's very easy to install autoconf/automake, then you won't have this kind of issue again... </pre> Glenn Morris 2012-05-24T02:06:03 http://permalink.gmane.org/gmane.emacs.bugs/60329 <pre> Yes you are right, my build machine pulled from the repo at midnight so it hadn't caught your commit: revno: 108346 committer: Glenn Morris &lt;rgm&lt; at &gt;gnu.org&gt; branch nick: trunk timestamp: Wed 2012-05-23 06:17:31 -0400 message: Auto-commit of generated files. The machine I was testing with locally on *had* that commit so it worked. All the OS stuff was a red herring. So this bug is already fixed. Sorry for the false alarm! -David </pre> David Caldwell 2012-05-24T01:58:27 http://permalink.gmane.org/gmane.emacs.bugs/60328 <pre>With the esc-face.1 below, (woman-find-file "esc-face.1") produces bold \ backslash with the "\" not in bold, where I expected it would be (man-db+groff makes it bold). I think woman.el.esc-face.diff below could correct this. 2012-05-24 Kevin Ryde &lt;user42&lt; at &gt;zip.com.au&gt; * woman.el (woman-decode-region): Replace escaped-escapes using `subst-char-in-region' so bold or underline on \e is preserved. I struck this in some perl pod2man output. It uses \e for backslashes in "verbatim" output paragraphs (bits of sample code usually). Those parts are in ".ft CW" font, which comes out of woman.el as woman-unknown face (which is red). But the face wasn't on the backslashes. .TH FOO 1 .SH NAME .B bold \e backslash In GNU Emacs 23.4.1 (i486-pc-linux-gnu, GTK+ Version 2.24.10) of 2012-04-08 on biber, modified by Debian Windowing system distributor `The X.Org Foundation', version 11.0.10707000 configured using `configure '--build' 'i486-linux-gnu' '--build' 'i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var/lib' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' '--enable-locallisppath=/etc/emacs23:/etc/emacs:/usr/local/share/emacs/23.4/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.4/site-lisp:/usr/share/emacs/site-lisp' '--with-crt-dir=/usr/lib/i386-linux-gnu' '--with-x=yes' '--with-x-toolkit=gtk' '--with-toolkit-scroll-bars' 'build_alias=i486-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DDEBIAN -O2' 'CPPFLAGS=-D_FORTIFY_SOURCE=2'' </pre> Kevin Ryde 2012-05-24T01:32:54 http://permalink.gmane.org/gmane.emacs.bugs/60327 <pre> Just add it to the `elpa' branch in the Emacs Bzr repository (in the `packages' subdirectory). Stefan </pre> Stefan Monnier 2012-05-24T01:36:43 http://permalink.gmane.org/gmane.emacs.bugs/60326 <pre>With the ds-quote.1 below, (woman-find-file "ds-quote.1") produces Expands to "ABC where I expected it not to have the ", so Expands to ABC I think woman.el.ds-quote.diff below can correct this. (Diff against the bazaar emacs-24, if that's the right branch. I've been having connection troubles lately so not sure what's supposed to be what.) 2012-05-19 Kevin Ryde &lt;user42&lt; at &gt;zip.com.au&gt; * woman.el (woman-strings): .ds foo "ABC don't include the leading " in the string value. Fixes definitions like .ds xx "" which should be a single " char, as described in the groff manual and used by perl pod2man. The commented out bit about a "hack" for CGI.man was on the right track, but it's more general than just "". The groff manual "Strings" node describes how a leading " in a .ds request begins the string and is not part of it .ds sign " Yours in a white wine sauce, As per this example there's no closing quote, and I don't think there's any backslashing or further quoting to interpret at the .ds definition stage. The bit in the groff manual reading To put a single double quote character into a string, use two consecutive double quote characters. I believe is trying to say .ds xx "" makes xx equal to a single " character. From a bit of experimenting I believe it doesn't mean "" -&gt; " or anything like that in the rest of the line. I struck this from perl pod2man which uses a .ds xx "" to produce a double-quote varying between nroff and troff. woman.el on pod2man output wrongly doubles the double-quotes giving things like See ""FUNCTIONS"" in Blah::Blah ... .TH FOO 1 .ds xx "ABC .SH NAME Expands to \*(xx In GNU Emacs 23.4.1 (i486-pc-linux-gnu, GTK+ Version 2.24.10) of 2012-04-08 on biber, modified by Debian Windowing system distributor `The X.Org Foundation', version 11.0.10707000 configured using `configure '--build' 'i486-linux-gnu' '--build' 'i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var/lib' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' '--enable-locallisppath=/etc/emacs23:/etc/emacs:/usr/local/share/emacs/23.4/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.4/site-lisp:/usr/share/emacs/site-lisp' '--with-crt-dir=/usr/lib/i386-linux-gnu' '--with-x=yes' '--with-x-toolkit=gtk' '--with-toolkit-scroll-bars' 'build_alias=i486-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DDEBIAN -O2' 'CPPFLAGS=-D_FORTIFY_SOURCE=2'' </pre> Kevin Ryde 2012-05-24T01:28:44 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.emacs.bugs