[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [AUCTeX] Preparing new AUCTeX version and comments about more freque
From: |
Ikumi Keita |
Subject: |
Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases |
Date: |
Fri, 21 Jul 2017 16:13:29 +0900 |
Hi all,
>>>>> Mosè Giordano <address@hidden> writes:
> Dear all,
> the latest stable release of AUCTeX doesn't include the fix for the
> parsing of TeX Live 2017 logs (see
> https://lists.gnu.org/archive/html/auctex/2017-04/msg00007.html), so
> now that TeX Live 2017 has been release it's a good idea to release
> AUCTeX 11.91. Is there any other quick change that you would like to
> see into this version?
Attached is a patch to make AUCTeX conform to elisp coding conventions,
quoted below from emacs lisp reference. (This issue is not in hurry at
all, so I don't mind whether it gets into 11.91 release or not.)
* When you mention a default value in a minibuffer prompt, put it and
the word `default' inside parentheses. It should look like this:
Enter the answer (default 42):
* Many commands that take a long time to execute display a message
that says something like `Operating...' when they start, and change
it to `Operating...done' when they finish. Please keep the style
of these messages uniform: _no_ space around the ellipsis, and _no_
period after `done'. *Note Progress::, for an easy way to generate
such messages.
conform-elisp-convention.gz
Description: fixing coding style
Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases,
Ikumi Keita <=