[AUCTeX-diffs] GNU AUCTeX branch, master, updated. 01224b600d1ac47d787b2adfd88071b2a6a5f781

2017-08-26 Thread Ikumi Keita
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU AUCTeX".

The branch, master has been updated
   via  01224b600d1ac47d787b2adfd88071b2a6a5f781 (commit)
  from  f3180f82fb8b20915bb6bce50bad778e31529145 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
commit 01224b600d1ac47d787b2adfd88071b2a6a5f781
Author: Ikumi Keita 
Date:   Sun Aug 27 01:48:23 2017 +0900

Add test for my commit on Aug 18

* tests/japanese/parse-timing-test.tex:
* tests/japanese/parse-timing.el:
New file.

diff --git a/tests/japanese/parse-timing-test.tex 
b/tests/japanese/parse-timing-test.tex
new file mode 100644
index 000..c995cf5
--- /dev/null
+++ b/tests/japanese/parse-timing-test.tex
@@ -0,0 +1,2 @@
+\documentclass{jarticle}
+\usepackage{amsmath}
diff --git a/tests/japanese/parse-timing.el b/tests/japanese/parse-timing.el
new file mode 100644
index 000..c9f5243
--- /dev/null
+++ b/tests/japanese/parse-timing.el
@@ -0,0 +1,63 @@
+;;; parse-timing.el --- tests for parse timing
+
+;; Copyright (C) 2017 Free Software Foundation, Inc.
+
+;; This file is part of AUCTeX.
+
+;; AUCTeX is free software; you can redistribute it and/or modify it
+;; under the terms of the GNU General Public License as published by
+;; the Free Software Foundation; either version 3, or (at your option)
+;; any later version.
+
+;; AUCTeX is distributed in the hope that it will be useful, but
+;; WITHOUT ANY WARRANTY; without even the implied warranty of
+;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+;; General Public License for more details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with AUCTeX; see the file COPYING.  If not, write to the Free
+;; Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+;; 02110-1301, USA.
+
+;;; Commentary:
+;; In AUCTeX, style hooks must not be executed too early.  In
+;; particular, they should not be called within the major mode hook
+;; because the required settings are sometimes not ready at that
+;; timing.  A difficult point is that many AUCTeX functions implicitly
+;; call `TeX-update-style', which eventually calls style hooks.  Thus
+;; a complicated hook sometimes triggers style hooks unintentionally.
+;; Such cases suits for detection via regression tests.
+
+;;; Code:
+
+(require 'ert)
+(require 'tex-jp)
+
+(defun AUCTeX-set-ert-path ( sym-val)
+  "Set first element of SYM-VAL to the next one, and so on.
+
+The value is the path to the test file, make sure it is expanded
+in the right directory even when the ERT test from the command
+line and from another directory."
+  (while sym-val
+(set (pop sym-val)
+(expand-file-name (pop sym-val)
+  (when load-file-name
+(file-name-directory load-file-name))
+(AUCTeX-set-ert-path
+ 'parse-timing
+ "parse-timing-test.tex")
+
+(ert-deftest japanese-TeX-style-hook-timing ()
+  "Test style hooks are not called too early."
+  (let ((TeX-parse-self t)
+   (TeX-master t)
+   (LaTeX-mode-hook '(japanese-latex-mode-initialization
+  turn-on-reftex)))
+(find-file parse-timing)
+(should (memq 'AMSTeX
+ (get reftex-docstruct-symbol
+  'reftex-label-alist-style)))
+(kill-buffer)))
+
+;;; parse-timing.el ends here

---

Summary of changes:
 tests/japanese/parse-timing-test.tex   |  2 +
 .../context-test.el => japanese/parse-timing.el}   | 47 +-
 2 files changed, 29 insertions(+), 20 deletions(-)
 create mode 100644 tests/japanese/parse-timing-test.tex
 copy tests/{context/context-test.el => japanese/parse-timing.el} (56%)


hooks/post-receive
-- 
GNU AUCTeX

___
auctex-diffs mailing list
auctex-di...@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-diffs


[AUCTeX-commit] GNU AUCTeX branch, master, updated. 01224b600d1ac47d787b2adfd88071b2a6a5f781

2017-08-26 Thread Ikumi Keita
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU AUCTeX".

The branch, master has been updated
   via  01224b600d1ac47d787b2adfd88071b2a6a5f781 (commit)
  from  f3180f82fb8b20915bb6bce50bad778e31529145 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
commit 01224b600d1ac47d787b2adfd88071b2a6a5f781
Author: Ikumi Keita 
Date:   Sun Aug 27 01:48:23 2017 +0900

Add test for my commit on Aug 18

* tests/japanese/parse-timing-test.tex:
* tests/japanese/parse-timing.el:
New file.

---

Summary of changes:
 tests/japanese/parse-timing-test.tex   |  2 +
 .../context-test.el => japanese/parse-timing.el}   | 47 +-
 2 files changed, 29 insertions(+), 20 deletions(-)
 create mode 100644 tests/japanese/parse-timing-test.tex
 copy tests/{context/context-test.el => japanese/parse-timing.el} (56%)


hooks/post-receive
-- 
GNU AUCTeX

___
auctex-commit mailing list
auctex-com...@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-commit


Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

2017-08-26 Thread Colin Baxter
> gojjoe   writes:

> It's code but also and foremost a typographic tool. When finishing
> to latex-typeset a document – and "finishing" can take quite some
> time in itself – I think it's inevitable to alternately compile
> and check the output continuously, to see if some parts of text
> look better in a certain disposition or another, or to find the
> best position for that important figure. Especially if you know
> the text will be printed. Not even auctex's preview can help for
> this; its purpose is different. I'm sure this is the case for most
> latex users, or for many of them at least.


I'm sure you're right. As an old timer (TeX since 1980s) I'm probably
stuck in my ways :-(.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel


[AUCTeX-commit] GNU AUCTeX branch, master, updated. f3180f82fb8b20915bb6bce50bad778e31529145

2017-08-26 Thread Ikumi Keita
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU AUCTeX".

The branch, master has been updated
   via  f3180f82fb8b20915bb6bce50bad778e31529145 (commit)
  from  2ed9d9308fe35daaf3157aeb0500bdb20c0be68c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
commit f3180f82fb8b20915bb6bce50bad778e31529145
Author: Ikumi Keita 
Date:   Sat Aug 26 21:21:23 2017 +0900

Fix doc string and indent

* tex.el (TeX-PDF-from-DVI, TeX-insert-braces-alist)
(TeX-arg-literal, TeX-auto-add-type):
Fix doc string.
(TeX-auto-parse-region): Fix indent.

---

Summary of changes:
 tex.el | 107 -
 1 file changed, 53 insertions(+), 54 deletions(-)


hooks/post-receive
-- 
GNU AUCTeX

___
auctex-commit mailing list
auctex-com...@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-commit


[AUCTeX-diffs] GNU AUCTeX branch, master, updated. f3180f82fb8b20915bb6bce50bad778e31529145

2017-08-26 Thread Ikumi Keita
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU AUCTeX".

The branch, master has been updated
   via  f3180f82fb8b20915bb6bce50bad778e31529145 (commit)
  from  2ed9d9308fe35daaf3157aeb0500bdb20c0be68c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
commit f3180f82fb8b20915bb6bce50bad778e31529145
Author: Ikumi Keita 
Date:   Sat Aug 26 21:21:23 2017 +0900

Fix doc string and indent

* tex.el (TeX-PDF-from-DVI, TeX-insert-braces-alist)
(TeX-arg-literal, TeX-auto-add-type):
Fix doc string.
(TeX-auto-parse-region): Fix indent.

diff --git a/tex.el b/tex.el
index 972110b..8083fa0 100644
--- a/tex.el
+++ b/tex.el
@@ -2246,7 +2246,7 @@ Programs should not use this variable directly but the 
function
   "Return the value of variable `TeX-PDF-from-DVI'.
 
 If `TeX-PDF-from-DVI' is not set and obsolete option
-`TeX-PDF-via-dvips-ps2pdf' is non-nil, return \"dvips-ps2pdf\"
+`TeX-PDF-via-dvips-ps2pdf' is non-nil, return \"Dvips\"
 for backward compatibility."
   (cond
(TeX-PDF-from-DVI)
@@ -3297,7 +3297,7 @@ CDR is non-nil or nil, depending on whether a pair of 
braces
 should be, respectively, appended or not to the macro.
 
 If a macro has an element in this variable, `TeX-parse-macro'
-will use its value to decided what to do, whatever the value of
+will use its value to decide what to do, whatever the value of
 the variable `TeX-insert-braces'."
   :group 'TeX-macro
   :type '(repeat (cons (string :tag "Macro name")
@@ -3623,7 +3623,7 @@ Unless optional argument COMPLETE is non-nil, ``: '' will 
be appended."
 (defun TeX-arg-literal (optional  args)
   "Insert its arguments ARGS into the buffer.
 Used for specifying extra syntax for a macro.  The compatibility
-argument OPTION is ignored."
+argument OPTIONAL is ignored."
   (apply 'insert args))
 
 
@@ -3923,7 +3923,7 @@ The algorithm is as follows:
 (defmacro TeX-auto-add-type (name prefix  plural)
   "Add information about NAME to the parser using PREFIX.
 
-Optional third argument PLURAL is the plural form of TYPE.
+Optional third argument PLURAL is the plural form of NAME.
 By default just add an `s'.
 
 This macro creates a set of variables and functions to maintain a
@@ -4310,56 +4310,55 @@ you should not use something like `[\\(]' for a 
character range."
   "Parse TeX information according to REGEXP-LIST between BEG and END."
   (if (symbolp regexp-list)
   (setq regexp-list (and (boundp regexp-list) (symbol-value regexp-list
-   (if regexp-list
-   ;; Extract the information.
-   (let* (groups
- (count 1)
- (regexp (concat "\\("
- (mapconcat
-  (lambda(x)
-(push (cons count x) groups)
-(setq count
-  (+ 1 count
- (TeX-regexp-group-count (car x
-(car x))
-  regexp-list "\\)\\|\\(")
- "\\)"))
- syms
- lst)
-(setq count 0)
-(goto-char (if end (min end (point-max)) (point-max)))
-(while (re-search-backward regexp beg t)
-  (let* ((entry (cdr (TeX-member nil groups
- (lambda (a b)
-   (match-beginning (car b))
- (symbol (nth 2 entry))
- (match (nth 1 entry)))
-(unless (TeX-in-comment)
-  (looking-at (nth 0 entry))
-  (if (fboundp symbol)
-  (funcall symbol match)
-(puthash (if (listp match)
- (mapcar #'TeX-match-buffer match)
-   (TeX-match-buffer match))
- (setq count (1- count))
- (cdr (or (assq symbol syms)
-  (car (push
-(cons symbol
-  (make-hash-table :test 'equal))
-syms)
-(setq count 0)
-(dolist (symbol syms)
-  (setq lst (symbol-value (car symbol)))
-  (while lst
-(puthash (pop lst)
- (setq count (1+ count))
- (cdr symbol)))
-  (maphash (lambda (key value)
- (push (cons value key) lst))
-   (cdr symbol))
-  (clrhash (cdr symbol))
-  (set (car symbol) (mapcar #'cdr (sort lst #'car-less-than-car)))
-
+  (if regexp-list
+  ;; Extract 

Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

2017-08-26 Thread Colin Baxter
> "David" == David Kastrup  writes:

David> Colin Baxter  writes:
>>> "Tassilo" == Tassilo Horn  writes:
>> 
Tassilo> Mosè Giordano  writes: Hi!
>> 
>> >>> Do you all agree to make this an option? If so, I can update
>> the >>> patch to accommodate that.  >> >> I'm not still convinced
>> that the patch you propose is a good >> idea.  Why should people
>> run "View" command to *not* view the >> document?
>> 
Tassilo> I know what Hong's referring to.  You want to view the
Tassilo> document in Evince but keep editing in emacs, thus the
Tassilo> input focus should stick there.
>> 
>> To me, and assuming I have not totally misunderstood the
>> proposal, there seems to be a philosophical issue here. If you
>> were to write a program, you wouldn't expect to view the output
>> of the compilation as you enter the code. You might look at an
>> initial output but then you would concentrate on the code before
>> compiling again - you surely wouldn't do both
>> simultaneously. TeX/LaTeX is also code, so why would not the same
>> expectation apply? I apologise if I have misunderstood.

David> Well, your philosophy did not manage to prevent
David> preview-latex.

Very true. I can only claim never to have used it.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel


Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

2017-08-26 Thread Colin Baxter
> "Tassilo" == Tassilo Horn  writes:

Tassilo> Mosè Giordano  writes: Hi!

>>> Do you all agree to make this an option? If so, I can update the
>>> patch to accommodate that.
>> 
>> I'm not still convinced that the patch you propose is a good
>> idea.  Why should people run "View" command to *not* view the
>> document?

Tassilo> I know what Hong's referring to.  You want to view the
Tassilo> document in Evince but keep editing in emacs, thus the
Tassilo> input focus should stick there.

To me, and assuming I have not totally misunderstood the proposal, there
seems to be a philosophical issue here. If you were to write a program,
you wouldn't expect to view the output of the compilation as you
enter the code. You might look at an initial output but then you would
concentrate on the code before compiling again - you surely wouldn't do
both simultaneously. TeX/LaTeX is also code, so why would not the same
expectation apply? I apologise if I have misunderstood.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel


Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

2017-08-26 Thread gojjoe
Hi Colin,

On 2017-08-26 10:08, Colin Baxter wrote:
> you wouldn't expect to view the output of the compilation as you
> enter the code. You might look at an initial output but then you would
> concentrate on the code before compiling again - you surely wouldn't do
> both simultaneously. TeX/LaTeX is also code, so why would not the same
> expectation apply? I apologise if I have misunderstood.

It's code but also and foremost a typographic tool. When finishing to 
latex-typeset a document – and "finishing" can take quite some time in itself – 
I think it's inevitable to alternately compile and check the output 
continuously, to see if some parts of text look better in a certain disposition 
or another, or to find the best position for that important figure. Especially 
if you know the text will be printed. Not even auctex's preview can help for 
this; its purpose is different. I'm sure this is the case for most latex users, 
or for many of them at least.

Cheers,
J

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel


Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

2017-08-26 Thread David Kastrup
Colin Baxter  writes:

>> "Tassilo" == Tassilo Horn  writes:
>
> Tassilo> Mosè Giordano  writes: Hi!
>
> >>> Do you all agree to make this an option? If so, I can update the
> >>> patch to accommodate that.
> >> 
> >> I'm not still convinced that the patch you propose is a good
> >> idea.  Why should people run "View" command to *not* view the
> >> document?
>
> Tassilo> I know what Hong's referring to.  You want to view the
> Tassilo> document in Evince but keep editing in emacs, thus the
> Tassilo> input focus should stick there.
>
> To me, and assuming I have not totally misunderstood the proposal,
> there seems to be a philosophical issue here. If you were to write a
> program, you wouldn't expect to view the output of the compilation as
> you enter the code. You might look at an initial output but then you
> would concentrate on the code before compiling again - you surely
> wouldn't do both simultaneously. TeX/LaTeX is also code, so why would
> not the same expectation apply? I apologise if I have misunderstood.

Well, your philosophy did not manage to prevent preview-latex.

-- 
David Kastrup

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel