Hi Arash,
> Arash Esbati writes:
> Well, currently this is the only solution we have in the lowercase
> area. More uppercase and \C-prefixed options are available. But as you
> said, a framework for full flexibility is not easy.
Indeed.
> What do you think about a change like this:
Currently, the latexmk can't automatically convert graphics formats
for files located under the subfolders of a project due to the
graphics package limitation of not logging the path info into the log
file.
So, I want to write a function to convert the graphic formats, say,
from svg to pdf/eps
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 f200e28278856ebadac2f02786bf201c4f6f8c0d (commit)
from
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 f200e28278856ebadac2f02786bf201c4f6f8c0d (commit)
from
Ikumi Keita writes:
>> Arash Esbati writes:
>>
>> Adding "Key sequence" with a string as KEY is missing.
>
> Yeah, I think it should be updated, too. However, I feel that it's not
> enough just to mention that KEY can be a string describing key sequence.
> As I experienced first in this
