Hi Tobias,
>>>>> Ikumi Keita writes:
>>>>> Tobias Bora writes:
>> I don't know why, but I updated recently my .emacs file (which may
>> downloaded a recent version of auctex), and since then I can't open
>> documentation anymore. Ind
Hi,
>>>>> Arash Esbati writes:
> Hi Keita,
> Ikumi Keita writes:
>> That's a good idea. Can I leave that work to you?
> Yes, you can :-) I'll try to work on this soonish.
Thank you. I pushed the commit except the prompt formatting.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
branch: master
commit 2bc07b78fff81da3eb705ab6bc93da35ddb4ba76
Author: Ikumi Keita
Commit: Ikumi Keita
Fix `TeX-documentation-texdoc' for okular
We used `start-process-shell-command' for these 4 years. However,
it turned out that that invalidated okular. (See bug#40577
branch: master
commit edc5e2ff63f6777d81e0293eb69d47d3b5a0658f
Author: Ikumi Keita
Commit: Ikumi Keita
Call Texdoc coherently
* tex.el (TeX-documentation-texdoc): Use `call-process' rather than
`shell-command-to-string' to invoke Texdoc.
Bind buffer object of working buffer
ikumi pushed a change to branch master.
from f5d40daa ; * style/nameref.el ("nameref"): Fix comment.
new 2bc07b78 Fix `TeX-documentation-texdoc' for okular
new edc5e2ff Call Texdoc coherently
Summary of changes:
tex.el | 123
gt; have this in tex.el:
> Then we could write:
> (setq pkg (TeX-read-string (TeX-format-prompt
> "View documentation for" pkg)
>nil nil pkg))
> Adjusting the other 30 occurrences in the repo should be easy. WDYT?
he patch #2. It also turns
INITIAL-INPUT argument for `TeX-read-string' into DEFAULT, taking
your effort into accout. What do you think about it?
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
0001-Make-TeX-documentation-texdoc-work-for-okular.patch.gz
Description: Fix for okular
0002-
le-find' to test whether texdoc is
| ;; available.
`
Thus I'm fine to follow your suggestion.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
doc isn't available) to run Texdoc.
This has a drawback that the user who sticks to older TeX Live
distribution isn't notified at all when the given keyword didn't match
any documentation, but I expect it's permissible. Mosè, what do you
think about it?
Regards,
Ikumi Keita
#StandWithUkraine #
s, then could you provide the value of the
following environment variables in the emacs shell (M-x shell)? That
is, type "echo $PDFVIEWER RET" etc. in that shell.
PDFVIEWER
PDFVIEWER_texdoc
TEXDOCVIEW_pdf
TEXDOC_VIEWER_PDF
I'd like to know whether there is something bad in your viewer
setting to run inside emacs while safe in a vanilla shell.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
577
Can you test whether the following code works for you? This was used
before my commit mentioned in [1]. I'd like to know whether my commit
harmed okular or not.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
--
(def
branch: master
commit e7379b3fec138f87e9a415750334c0f1327f9a1f
Author: Ikumi Keita
Commit: Ikumi Keita
Simplify version and date specification
* latex/preview.dtx (section{The Implementation}): Don't use RCS
tags for version and date. Declare manually instead.
(): Update
Hi Arash and Al,
>>>>> Arash Esbati writes:
> Ikumi Keita writes:
>> But maybe it's a corner case that we don't have to worry about. I'm not
>> sure.
> This is indeed a corner case: Packages like fvextra.sty which allow
> things like \Verb{content} explici
ex-syntactic-keywords-extra))
Hmm. That would fail if some verbatim macro has an intentional unpaired
"{" in its argument like \foobar{aaa"{"bbb} .
But maybe it's a corner case that we don't have to worry about. I'm not
sure. What do others think about this?
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
x run as you say,
so I realized that hyperref.sty treats "%", in addtion to "#" and "~",
as special. Hmm, this is diffcult...
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
)*\\(}\\)")
>(1 "|") (2 "|"
> ...)
Is it appropriate to treat the URL argument of \href as verbatim?
According to hyperdoc document, only "#" and "~" are special there.
Maybe we should reconsider not to add "href" (and alikes as well?) to
`LaTeX-verbatim-macros-with-braces-local' in style/hyperref.el.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
gt; f(x) \right|_{x=x_{c}}
> \end{equation*}
> Which looks odd to me. Can somebody confirm this?
No, it doesn't reproduce for me. The environment stays the original form
when I type C-c C-q C-e inside the equation* environment. I guess
something in your personal customization are i
>>>>> Ikumi Keita writes:
> Hi all,
> I'd like to apply the attached fix for this issue. If no objection, I'll
> install it with some regression tests.
Done. Thanks, Enrico.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
branch: master
commit f9b378a45c89b16a183f46830e4c7ec7b2aec7c5
Author: Ikumi Keita
Commit: Ikumi Keita
Support detached arguments
* tex.el (TeX-find-macro-boundaries): Skip white spaces between a
macro argument and comment starter.
Fix doc string.
Add FIXME comment
Hi all,
I'd like to apply the attached fix for this issue. If no objection, I'll
install it with some regression tests.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
>From a496210874133b219d8e881f9a7178d7c9e23e91 Mon Sep 17 00:00:00 2001
From: Ikumi Keita
Date: Fri, 6 Jan 2023 01
Hi all,
Can somebody with write permission for Emacs repository kindly apply the
attached patch to RefTeX?
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
diff -r 2672391e6055 lisp/textmodes/reftex-cite.el
--- a/lisp/textmodes/reftex-cite.el Sat Mar 27 02:34:27 2021 +0900
+++ b/lisp
branch: master
commit 906e57dfb87d0a297164364f0c771151a86d8f9c
Author: Ikumi Keita
Commit: Ikumi Keita
; * style/physics.el: Write proper date.
---
style/physics.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/style/physics.el b/style/physics.el
index 8676a696
branch: master
commit 54c82bd093aec4b1fa9264ac91b70cf30da737b6
Author: Ikumi Keita
Commit: Ikumi Keita
New style file physics.el
* style/physics.el: New style file.
* Makefile.in (STYLESRC): Add it.
---
Makefile.in | 3 +-
style/physics.el | 418
ult behavior; "allowspaces" package
option can disable it.)
Thus if we are to be very strict, AUCTeX shouldn't consider separated
brackets as optional arguments for these cases. (I'm not sure whether
it's worth discriminating such strictly.)
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
branch: master
commit bf66b302a4afa297fc2322a875935fd9a4d47525
Author: Ikumi Keita
Commit: Ikumi Keita
Improve the previous commit slightly
* latex.el (LaTeX-current-environment,LaTeX-backward-up-environment):
Move the task to find out the environment name from the latter
>>>>> Ikumi Keita writes:
> My current status is the attached patch, but it fails with regression
> test `LaTeX-change-environment-with-esc', of course. Mosè, Tassilo, do
> you think that `LaTeX-modify-environment' should keep the ability to
> change environment na
branch: master
commit a57e627284383e2a28082b8be652b2714a366766
Author: Ikumi Keita
Commit: Ikumi Keita
Improve consistency between similar functions
Include doctex mode special treatment of `LaTeX-current-environmnet'
into `LaTeX-find-matching-begin' and `LaTeX-find-matching
branch: master
commit 5f129b5dcab1d1c3b3b987348cfa841e265548c4
Author: Ikumi Keita
Commit: Ikumi Keita
Support starred variant name
* latex.el (LaTeX-find-matching-end):
(LaTeX-find-matching-begin):
Find correct begin or end when the point is just after the asterisk
ikumi pushed a change to branch master.
from 28866558 Use `symbol-value' instead of `eval'
new 5f129b5d Support starred variant name
new a57e6272 Improve consistency between similar functions
new d3ab64f8 Reduce redundancy in regexp
Summary of changes:
branch: master
commit d3ab64f89394d16473ee1af144d5cf6bde77380c
Author: Ikumi Keita
Commit: Ikumi Keita
Reduce redundancy in regexp
* latex.el (LaTeX-environment-name-regexp): Don't quote regexp inside
[^...].
(LaTeX-modify-environment): Omit spurious regexp group. (already
branch: master
commit 288665587a4fcb6b7fc356e86a86ee9670186232
Author: Ikumi Keita
Commit: Ikumi Keita
Use `symbol-value' instead of `eval'
* multi-prompt.el (multi-prompt-expand-completion-table): Use
`symbol-value' explicitly instead of `eval' to obtain the value
>>>>> Arash Esbati writes:
> Ikumi Keita writes:
>> All right, then my propsal is the attached one.
> Thanks, LGTM.
Thank you, pushed to the git repo.
Bye,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
branch: master
commit 22fa670915fb1fb6a08b60c7bb5acfb79684dd55
Author: Ikumi Keita
Commit: Ikumi Keita
; Fix doc strings
* tex.el (TeX-command-list): Quote Lisp symbols.
(TeX-insert-braces): Fix a typo.
* latex.el (LaTeX--completion-annotation-from-math-menu)
(LaTeX
branch: master
commit 3806176ba2fa11cc990e49792f9db34532c85258
Author: Ikumi Keita
Commit: Ikumi Keita
Fix argument description in doc strings
* latex.el (TeX-read-key-val):
* multi-prompt.el (multi-prompt-key-value):
Correct the format of KEY-VAL-ALIST and state
ikumi pushed a change to branch master.
from d43bfae3 Overhaul beamer.el
new 22fa6709 ; Fix doc strings
new 3806176b Fix argument description in doc strings
Summary of changes:
latex.el| 14 --
multi-prompt.el | 10 +++---
style/acro.el | 9
>>>>> Ikumi Keita writes:
>>>>> Arash Esbati writes:
>> - `LaTeX-arg-beamer-theme',
>> - `LaTeX-arg-beamer-outer-theme',
>> - `LaTeX-arg-beamer-color-theme' and
>> - `LaTeX-arg-beamer-font-theme'.
>> WDYT?
> Thanks,
branch: master
commit d43bfae3fa7aa016120da7a36ed46b83133e5ba4
Author: Ikumi Keita
Commit: Ikumi Keita
Overhaul beamer.el
* style/beamer.el (LaTeX-beamer-after-insert-env): Use `member'
instead of `TeX-member'.
Add comment.
(TeX-arg-beamer-overlay-spec): Simplify
>>>>> Ikumi Keita writes:
> Thanks for your comments. I'll install the proposed fix as well as
> macrocode*? support, unless Mosè or Tassilo objects explicitly.
> Since `LaTeX-find-matching-begin' and `LaTeX-current-environment' is
> very similar in their task in implem
Hi Arash,
>>>>> Arash Esbati writes:
> I'd probably change the last sentence to:
> The second element can also be a variable returning a list of strings.
All right, then my propsal is the attached one.
Regards,
Ikumi Keita
#StandWithUkraine #St
Hi Arash,
>>>>> Ikumi Keita writes:
>> TABLE is an alist. The first element of each list is a string
>> representing a key and the optional second element is a list with
>> strings to be used as values for the key.
>> Does is make sense? Any commen
s is make sense? Any comments welcome.
Reasonable. :-)
Bye,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
and simplify.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
same thing would also apply to
> - `LaTeX-arg-beamer-theme',
> - `LaTeX-arg-beamer-outer-theme',
> - `LaTeX-arg-beamer-color-theme' and
> - `LaTeX-arg-beamer-font-theme'.
> WDYT?
Thanks, I'll follow your suggestion.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
nk=5, but not for example
> shrink=5,label=theorem
You can. Hit TAB after "shrink=5," and see what happens.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
)), not "a list with
strings". Actually, when I evaluate
(TeX-read-key-val nil '(("foo" "1" "2" "3")))
and type f o o = TAB, emacs signals an error complaining
(invalid-function "1")
. We need instead
(TeX-read-key-val nil '(("foo" ("1" "2" "3"
I think the doc string should be adapted accordingly. What do you think
about it?
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
ated.
You can type in equal sign yourself. Unfortunately, AUCTeX key-value
completion facility doesn't have an option to supply "=" automatically.
I admit that it isn't totally satisfactory, but it seems difficult to
extend the facility to have such an option as far as I can see. :-(
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
---
so it doesn't handle the exceptional cases of bug#19281, namely
"\begin{\bar{xyz}}" and "\end{\bar{xyz}}". Should we cater for such
cases?
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19281
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
arse-args'. I expect that wouldn't bother existing users.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
Here is the updated style file. Give it a roll. ;-)
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
beamer.el.gz
Description: frame option enabled
C-m calls
ask all optional arguments every time. That is, in one C-c C-m call, you
cannot skip subsequent option queries after you provided empty answer
for an option query.)
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
ch to
the base buffer and run there when they are called in an indirect
buffer.)
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
[1] Thread titled "Output to directory patch" in
https://lists.gnu.org/archive/html/auctex-devel/2021-02/
rect buffers. Why do
you edit in an indirect buffer? (Even if there is good reason to do so,
I feel that it's enough to make C-c C-c (and similar commands) ask
whether to switch to base buffer when you are in indirect buffer.)
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
_
>>>>> Ikumi Keita writes:
> Looking at the relevant code, I think I can do something for
> LaTeX-modify-environment to cover the situation where \begin and \end
> are on the same line. I expect that I can have spare time to manage this
> issue on November.
I pushed th
branch: master
commit 3e8aa71ef28ad05bd32bedf18bbeb4d8cd35c069
Author: Ikumi Keita
Commit: Ikumi Keita
Fix bug#58689 with a bit of optiomization
* latex.el (LaTeX-modify-environment): Comment out redundant
`beginning-of-line' and `end-of-line'.
---
latex.el | 20
tex-add-keywords '(("textbf" "<{"))
>'bold-command)
Thanks, I'll see what I can do.
(What I feel uneasy a bit is that AUCTeX framework to insert font macros
isn't capable of overlay arguments. :-( )
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
lean" command now cleans .vrb files generated when [fragile] option
is given to frame environment.
Enjoy!
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
Hi all,
I think I'm almost done with updating beamer.el. The current state is
attached as a patch. Any comments and suggestions are welcome.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
>From 9c63c6d64099c25301975c36f7c044fdcb1ee6db Mon Sep 17 00:00:00 2001
From: Ikumi Keita
D
y of optional args when entering
environments by C-c C-e.
I consider implementing such feature in AUCTeX when I have more spare
time :-)
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
>>>>> Arash Esbati writes:
> This is what I did (287da56401); it's probably the easiest way :-)
Cheers,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
itle" . nil)
("newpage" . nil)))
in your init file. However, I recommend to use customize interface as I
wrote in my previous message, which would be intuitive enough and easy
to handle IMHO.
Best regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
> - Use another name, say `LaTeX-current-environment-for-insertion',
>which is ugly
> - Drop it completely and use the function in the hooks
I prefer the last one, but I don't adhere.
Bye,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
macro’
| will use its value to decide what to do, whatever the value of
| the variable ‘TeX-insert-braces’.
`
I think the customization interface provided by M-x customize-option
RET TeX-insert-braces-alist RET is sufficient for most users, even if
this doc string isn't such descriptive.
Bye,
Ik
ginal topic. How can we activate input support for environment
optional arguments if the user customizes
`TeX-insert-macro-default-style' to `mandatory-args-only'?
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
ect of `TeX-insert-braces'. See
https://lists.gnu.org/r/bug-auctex/2022-09/msg00029.html
.
Bye,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
If you still want to stay with that idea, how about moving the
let-binding into `LaTeX--env-parse-args'? Then we can avoid unintended
interaction of `LaTeX-current-environment' and
`LaTeX-insert-environment', and simplify `LaTeX-env-item-args' and
`LaTeX-env-label-args' at the same time.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
X--env-parse-args args));)
, indentation gets back to correct behavior.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
branch: master
commit ba70baec6ca95c609e794624ca589c1de9ea02d8
Author: Ikumi Keita
Commit: Ikumi Keita
Fix doc strings regarding to section commands
* context.el (ConTeXt-numbered-section-hook):
(ConTeXt-unnumbered-section-hook):
Add mention about `ConTeXt-reference
branch: master
commit 7da1860c2a8cf7a2eb8f1596bf51af5532aa949b
Author: Ikumi Keita
Commit: Ikumi Keita
Support starred section names
* latex.el (LaTeX-section-level): Accept starred section names.
Simplify.
(LaTeX-section-name): Simplify.
(LaTeX-section-heading
by majority of AUCTeX users.
in my first message with respect to changing the key bind of
`LaTeX-modify-environment'.
Best regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
is still kind of awkward and I hope
smarter solution.
>> Does anyone come up with good ideas?
> Would it make sense to say:
> • C-u C-c C-e modifies the document
> • C-u C-u C-c C-e toggles the arguments query
> ?
Yes, it's another feasible treatment. However, a more uni
t document it at the
| ;; moment.
`
in the defun of `TeX-insert-macro'. Maybe now is the "future" mentioned
there.)
Does anyone come up with good ideas?
Best regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
LaTeX
>> 2.09 document because `TeX-arg-define-macro-arguments' takes care of
>> it.)
> LGTM, thanks.
Thanks, applied.
Bye,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
ikumi pushed a change to branch master.
from d937d403 Simplify implementation of style/changelog.el
new 3d5ac9cf Cleanup newcommand/newenvironment support
new eca0fadb ; Trivial cleanups
Summary of changes:
context.el | 20 ++--
latex.el | 38
branch: master
commit 3d5ac9cf7af5bedbae2e430024f001168d4e4a99
Author: Ikumi Keita
Commit: Ikumi Keita
Cleanup newcommand/newenvironment support
* latex.el (LaTeX-common-initialization): Use
`TeX-arg-define-macro-arguments' for optional argument
for (re)newenvironment
branch: master
commit eca0fadbc3462aebc48f8a672243a2776e148d8a
Author: Ikumi Keita
Commit: Ikumi Keita
; Trivial cleanups
* tex.el (TeX-search-unescaped): Quote function names by #'.
(TeX-parse-all-errors): Remove comment which no longer applies since
tex-buf.el was merged
;.
I'd propose to apply the attached fix, which also includes removal of
duplication of code. (The deleted portion is inside "else" clause of
`(if (string-equal LaTeX-version "2")', but it wouldn't fail for LaTeX
2.09 document because `TeX-arg-define-macro-arguments' takes care of
SD atril did support forward search 3-4 years ago.
Hmm, I don't have a good idea to cover such situation on AUCTeX, either.
I'll personally build my atril with synctex enabled.
Thanks,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
branch: master
commit c60ed913a04656fa346db6403d3adb713d76f975
Author: Ikumi Keita
Commit: Ikumi Keita
; Remove unnecessary `declare-function'
* style/tikz.el: Remove unnecessary `declare-function' that I
shouldn't add.
---
style/tikz.el | 2 --
1 file changed, 2 deletions
t-evince' isn't working as expected. If I
understand correctly, it should return nil since my atril doesn't
support forward search. However, it returns t for me. I'd appreciate if
you could take a look.
Best,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
P.S. As far as I can see, `TeX-ev
ion
> `TeX-TikZ-point-name-regexp'. Does it really make sense to maintain a
> `defgroup' for this? Why not just adding the single entry to
> tex-style.el and be done with it?
Done as well. ;-)
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
branch: master
commit 94c28a32147b3c2de02dc2702ae38ac232b40d70
Author: Ikumi Keita
Commit: Ikumi Keita
Enhance scope environmnent support
* context.el (ConTeXt-after-insert-env-hook): New hook.
(ConTeXt-insert-environment): Follow the change in
`LaTeX-insert-environment
ikumi pushed a change to branch master.
from 75bea89b Simplify implementation of style/booktabs.el
new 94c28a32 Enhance scope environmnent support
new ee9e8a2b Move `TeX-TikZ-point-name-regexp' to tex-style.el
Summary of changes:
context.el| 167
branch: master
commit ee9e8a2b6ef5677f7739e8dd19a31563520e93d3
Author: Ikumi Keita
Commit: Ikumi Keita
Move `TeX-TikZ-point-name-regexp' to tex-style.el
* tex-style.el:
* style/tikz.el (TeX-TikZ-point-function-map):
Move defcustom into tex-style.el.
(AUCTeX-TikZ
Hi Arash,
>>>>> Arash Esbati writes:
> Thanks for your response. The change is now installed with commit
> 47f9ead1c6.
I've made the attached patch with your new facility using
`TeX-exit-mark'. What do you think about it?
Regards,
Ikumi Keita
#StandWithUkraine #Sto
m/mate-desktop/atril/blob/master/data/org.mate.atril.Daemon.service.in
I'm not familiar with D-BUS. I hope Tassilo can settle out the issue.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
ple didn't make sense. There t should have been some
string literal such as "Title".
> C-c C-e baz RET gives:
> \begin{baz}{}
> *
> \end{baz}
Ah, this is it. Now I see it works very well.
> For me, t behaves as described in the manual "Insert empty braces, lea
the point inside "{}" after C-c
C-e when the user gave empty answer for argument query for environments
like this:
(LaTeX-add-environments
...
'("foo" LaTeX-env-args t)
...)
If the user intentionally keep there empty, that behavior wouldn't be
what the user wants.
(But maybe I'm too skeptical and there is no environment which applies
this worry.)
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
Hi Arash,
>>>>> Arash Esbati writes:
> Arash Esbati writes:
>> What do you think about this:
> Sorry, the change was not good enough, please consider this one:
Thanks, it works well.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
e:
[...]
> But this is not possible with the current definition of
> `LaTeX--env-parse-args'. What do you think about the suggested change?
Ah, I see. You are talking about a separate topic of moving the point
inside the empty "[]". Doesn't the suggested change brea
l. It
would allow us to eliminate awkward usage of `TeX-arg-eval' for
\frametitle support in beamer.el. (Actually, beamer.el is my next target
;-) )
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
ess further comment
arrives from someone.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
ou could see if you achieve what you're
> looking after with `LaTeX-env-args' -- but I think that wouldn't work
> because of the (save-excursion ...) it uses?
Hmm. Currently I'm not sure which `save-excursion' is the one you are
talking about, but will look closer later. Thank you for comments.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
ves the point inside in that empty "[]",
assuming that the user actually expects to fill in that bracket
immediately, possibly with the help of in-buffer completion facility.
I admit that it might be a bit too aggresive. What do you think about
this idea?
Best,
Ikumi Keita
#StandWithU
branch: master
commit 21e624026a250f39a508ec06274fbfa72b99b6a1
Author: Ikumi Keita
Commit: Ikumi Keita
Improve support for TikZ
* style/tikz.el ("tikz"): Add "tikz", "tikzset", "usetikzlibrary" and
"foreach" macros.
Run s
branch: master
commit c0c955633839777848a94400a45ef97667e7a992
Author: Ikumi Keita
Commit: Ikumi Keita
Don't insert empty node name
* style/tikz.el (TeX-TikZ-node-arg): Treat node name as optional to
avoid the insertion of empty node name.
(TeX-TikZ-arg-options, TeX-TikZ
branch: master
commit 316550f0bfa61d197fca7b4a9fc9b864b1b46640
Author: Ikumi Keita
Commit: Ikumi Keita
Fix `ConTeXt-add-environments'
* context.el (ConTeXt-environment, ConTeXt-environment-menu): Use
function `ConTeXt-environment-list' to refer to the current
environments
ikumi pushed a change to branch master.
from 52a7f405 ; * doc/auctex.texi (Adding Environments): Adjust
indentation.
new 21e62402 Improve support for TikZ
new 316550f0 Fix `ConTeXt-add-environments'
new c0c95563 Don't insert empty node name
Summary of
>>>>> Arash Esbati writes:
> Yes, sorry, my bad. I was thinking about `TeX-auto-add-regexp' which is
> executed in the hooks where `TeX-auto-add-type' is only used top-level.
> So let's scratch my idea and go on with yours :-)
Thanks, I'll to.
Bye,
Ikumi
-hooks)))
> ;; Alist of parsed information.
> ;; Each entry is a list with the following elements:
> ;;
That alone wouldn't work. Suppose that you open two LaTeX files. The
second buffer wouldn't have `TeX-auto-parser' updated.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
type "environment" "ConTeXt")
in context.el add entries with the same key "environment" in
`TeX-auto-parser'. Thus we need to fix `TeX-auto-add-type'.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
401 - 500 of 1985 matches
Mail list logo
