Rob Browning | 21 Oct 16:31 2014

Origin of IVD_Sequences.txt


What's the upstream source for this file?

I ask because the license is included by URL reference, and from a
preliminary look, the applicable terms of that license appear to vary
depending on the original source (path) of the file.

Thanks
--

-- 
Rob Browning
rlb  <at> defaultvalue.org and  <at> debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Dima Kogan | 21 Oct 08:01 2014
Picon

Clarification about auto-revert-mode and inotify

Hi.

I'm running an emacs recently built from source, and the
auto-revert-mode functionality is confusing to me.

I configured with --with-file-notification=inotify. With this I would
expect auto-revert-mode buffers to be updated immediately, possibly with
some throttling. I do not observe this; it still takes ~5 seconds for
the buffers to update.

Ltrace tells me that inotify_...() functions ARE being called. It also
tells me that inotify_callback() is called immediately after a file
update, but the buffer is not updated immediately. Is this intended
behavior or a bug? The recent 24.4 release touts inotify support in its
NEWS; does this mean simply that auto-revert is more efficient?

dima

Ulrich Mueller | 21 Oct 11:07 2014
Picon

Version number in emacs-24 branch

Could the version number in the emacs-24 branch be updated please
(to 24.4.50, I guess)? Otherwise, installing the live version along
with the released Emacs 24.4 will not be possible.

Ulrich

Dima Kogan | 21 Oct 09:00 2014
Picon

Clarification about auto-revert-mode and inotify

Hi.

I'm running an emacs recently built from source, and the
auto-revert-mode functionality is confusing to me.

I configured with --with-file-notification=inotify. With this I would
expect auto-revert-mode buffers to be updated immediately, possibly with
some throttling. I do not observe this; it still takes ~5 seconds for
the buffers to update.

Ltrace tells me that inotify_...() functions ARE being called. It also
tells me that inotify_callback() is called immediately after a file
update, but the buffer is not updated immediately. Is this intended
behavior or a bug? The recent 24.4 release touts inotify support in its
NEWS; does this mean simply that auto-revert is more efficient?

dima

Dima Kogan | 21 Oct 07:03 2014
Picon

Clarification about auto-revert-mode and inotify

Hi.

I'm running an emacs recently built from source, and the
auto-revert-mode functionality is confusing to me.

I configured with --with-file-notification=inotify. With this I would
expect auto-revert-mode buffers to be updated immediately, possibly with
some throttling. I do not observe this; it still takes ~5 seconds for
the buffers to update.

Ltrace tells me that inotify_...() functions ARE being called. It also
tells me that inotify_callback() is called immediately after a file
update, but the buffer is not updated immediately. Is this intended
behavior or a bug? The recent 24.4 release touts inotify support in its
NEWS; does this mean simply that auto-revert is more efficient?

dima

covici | 21 Oct 00:37 2014

cl-macro-expandall symbol definition is void

Hi.  I am getting this immediately upon starting emacs 24.4-rc1.  How do
I even troubleshoot as it seems to be something in my .emacs file?

Thanks in advance for any suggestions.

--

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici <at> ccs.covici.com

covici | 21 Oct 00:35 2014

bug 17059 still present

Hi.  I am still having the problem of bug 17059 cannot view extracted
text from pdf in at least 24.4-rc1.  I wonder if someone could take a
look at this?

Thanks in advance for any ideas.

--

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici <at> ccs.covici.com

Glenn Morris | 20 Oct 21:54 2014
Picon

emacs-24 branch policy


The emacs-24 branch is now available for any safe bug fixes that you
think should go into a 24.5 release (if there is one).
If you've committed any such things to the trunk, please consider
backporting them to emacs-24 (please put the word "backport" in the
commit log). 

Glenn Morris | 20 Oct 21:32 2014
Picon

Emacs 24.4 released


Version 24.4 of the Emacs text editor is now available.

For more information on Emacs, see:
  http://www.gnu.org/software/emacs/

You can retrieve the source from your nearest GNU mirror by using one
of the following links:
  http://ftpmirror.gnu.org/emacs/emacs-24.4.tar.xz
  http://ftpmirror.gnu.org/emacs/emacs-24.4.tar.gz

Or choose a mirror explicitly from the list at:
  http://www.gnu.org/prep/ftp.html

Mirrors may take some time to update; the main GNU ftp server is at:
  http://ftp.gnu.org/gnu/emacs/

Highlights of this release include:

  - A built-in web browser (M-x eww)

  - Improved multi-monitor and fullscreen support

  - "Electric" indentation is enabled by default

  - Support for saving and restoring the state of frames and windows

  - Emacs Lisp packages can now be digitally signed

  - A new "advice" mechanism for Emacs Lisp
(Continue reading)

Alan Mackenzie | 19 Oct 16:17 2014
Picon

Aborting display. Is this possible?

Hello, Emacs.

A lisp program can influence an ongoing display operation by setting
redisplay-dont-pause to nil.  When input arrives, the displaying is
immediately paused.

However, at the next opportunity, the displaying carries on where it
left off, rather than being aborted.  It would be nice to arrange for
such abortion to happen, leaving the partly completed display visible on
the user's video.

Why?  Better to handle a user auto-repeating on the PageDown key.  On my
system, auto-repeat is around 35-40 characters per second, on a window
with 65 lines.  In my favourite mode, display can not keep up.  If I set
redisplay-dont-pause to nil and hold down PageDown, what the user sees
is frozen for several seconds whilst display determines the display of
every intermediate buffer position (which isn't going to get displayed
anyway) before finally reaching point.

Would it be possible to enhance display such that incoming input would
abort the current display operation?

--

-- 
Alan Mackenzie (Nuremberg, Germany).

Jan Djärv | 19 Oct 13:49 2014
Picon

Re: Bidi reordering engine upgraded

Den 2014-10-18 15:13, Eli Zaretskii skrev:
>> Date: Sat, 18 Oct 2014 15:54:15 +0300
>> From: Eli Zaretskii <eliz <at> gnu.org>
>> Cc: dmantipov <at> yandex.ru, emacs-devel <at> gnu.org
>>
>>> I suggest you check it in so we can test it.
>>
>> OK, will do.
>>
>>> Do we have a test case?
>>
>> Yes, the one posted by Dmitry here:
>>
>>    http://lists.gnu.org/archive/html/emacs-devel/2014-10/msg00518.html
>
> OK, committed as trunk revision 118149.
>
> Note that I also asked about similar problems with hbar cursor, see
> http://lists.gnu.org/archive/html/emacs-devel/2014-10/msg00555.html.
>

Missed this.  In this case, the cusor is not seen.  Both on trunk and 24.4. 
No display artifacts on 24.4 as with normal cursor.

	Jan D.


Gmane