Mosè Giordano <m...@gnu.org> writes:
> Hi Carlos,
>
> 2015-09-27 22:08 GMT+02:00 Carlos <linguafa...@gmail.com>:
>> Mosè:
>>
>> I still think (point-min) is a better alternative than (point-max) since
>> only a greater than > is required, that would jump right to where the
>> warning is
>> at. So far, in my end, until further notice:
>>
>> --- /context.el 2015-09-27 15:10:40.285263202 -0400
>> +++ /context.el 2015-09-27 15:39:12.673222971 -0400
>>
>> @@ -570,22 +570,11 @@
>> ;; outputs. Just looking for "another run needed" would
>> ;; find the first occurence
>> (goto-char (point-max))
>> - (re-search-backward "TeXUtil " nil t)
>> - (re-search-forward "another run needed" nil t))
>> + (setq TeX-recenter-output-buffer 'TeX-command-next)
>> (message (concat "You should run ConTeXt again "
>> - "to get references right, "
>> - (TeX-current-pages)))
>> - (setq TeX-command-next TeX-command-default))
>> - ((re-search-forward "removed files :" nil t)
>> - (message "sucessfully cleaned up"))
>> - ((re-search-forward "^ ?TeX\\(Exec\\|Util\\)" nil t) ;; strange
>> regexp --pg
>> - (message (concat name ": successfully formatted "
>> - (TeX-current-pages)))
>> - (setq TeX-command-next TeX-command-Show))
>> - (t
>> - (message (concat name ": problems after "
>> - (TeX-current-pages)))
>> - (setq TeX-command-next TeX-command-default))))
>> + "to get references right,"
>> + (concat "formatted:"
>> + (TeX-current-pages))))))))
>>
>
> This breaks things for people not using "context", doesn't it?
Documents compiled with texexec, should use texexec and/or mkiv
accordingly. Functions by/for texexec, are unaffected.
I have seen many more adopted changes in 'mark iv' than with
'texexec'. For example, As recent as a month ago, a table's requirements (as
specified by a power user) would not compile with either 2013 or 2014
'mark iv''s operations. This was later confirmed, by installing a 2015
version, which successfully completed it.
As you know, It's useful to have different installations, if space is not a
constraining factor, so both outcomes can be checked against one
another. A reminder of this: is offered in Knuth's quote, as specified
by the default input file 'knuth' which is contained in ConTeXt. "The
real test begins as people with different viewpoints undertake their
own experiments". Nothing is more powerful than hands-on approaching
methods. It would be a long stretch, to stay up to date with every,
every update, every change, every modification. etc.
Unless the change, has such an effect on font handling, like mkiv deploys,
then it no longer is an option, but a necessity, to update. In the words
of known experts, the facilities involved in ConTeXt with the inclusion
of Lua, is the future of typesetting.
Mosè, Have you seen how it thoroughly scans for map files? If you have
context installed, Do it in the terminal and type context <file>,
so you can see the process. Simplest route is by loading a module in the file
\usemodule[simplefonts]
\setmainfont[<system font here>]
\starttext
\input <file>
\stoptext
And to answer your question,, I don't think it'd break. It certainly, would
not break a function anymore than, (and the following is an analogy): than
a tufte-handout LaTeX document class, loaded with an acm bibliography
style, for the latter is beyond AucTeX's capabilities' reach to
handle. The cause of
the problem is in the document itself, which must be fixed, before continuing
any further.
>> ;;; Environments
>> @@ -1723,6 +1712,7 @@
>> (setq TeX-sentinel-default-function 'TeX-ConTeXt-sentinel)
>> (TeX-run-mode-hooks 'text-mode-hook 'TeX-mode-hook 'ConTeXt-mode-hook))
>>
>> +
>> (defun context-guess-current-interface ()
>> "Guess what ConTeXt interface the current buffer is using."
>> (interactive)
>>
>>
>> --- /tex.el 2015-09-27 15:10:40.365263200 -0400
>> +++ /tex.el 2015-09-27 15:47:27.657211341 -0400
>> @@ -141,6 +141,9 @@
>> ("ConTeXt Full" "texexec %(extraopts) %(execopts)%t"
>> TeX-run-TeX nil
>> (context-mode) :help "Run ConTeXt until completion")
>> + ("MKIV" "context --synctex=1 %t"
>> + TeX-run-TeX t
>> + (context-mode) :help "")
>> ("BibTeX" "bibtex %s" TeX-run-BibTeX nil t :help "Run BibTeX")
>> ("Biber" "biber %s" TeX-run-Biber nil t :help "Run Biber")
>> ,(if (or window-system (getenv "DISPLAY"))
>
> Are you sure "MKIV" is better and easier to recognize than "Mark IV"?
> Please bear in mind I'm not in ConTeXt, I don't know its naming
> conventions :-)
The convention officially settled with your "Mark IV" remark. So from a
user's point-of-view, do you think the other definitions should stay the
same, or should follow the "Mark II" conventions?
> Bye,
> Mosè
Take care Mosè
> _______________________________________________
> auctex-devel mailing list
> auctex-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/auctex-devel
_______________________________________________
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
