Ken Mankoff writes:
> It is not a 1x operation, it is a per-document operation. For example,
> in my use-case that started this whole discussion, each publication
> requires tweaking a dozen or more lines of biblatex config.
Of course there are an amount of lines that depends on the document.
Th
Aaron Ecay writes:
> This is basically making the user do (something like) org-edit-special
> manually.
That is an interesting idea. `org-edit-special' could be improved to
edit clusters of export keywords (e.g. #+LATEX) in a dedicated buffer.
Recognizing a keyword as an export keyword is doabl
On 2014-06-21 at 20:42, Aaron Ecay wrote:
> 2014ko ekainak 21an, Nicolas Goaziou-ek idatzi zuen:
>>
>> Aaron Ecay writes:
>>
>>> The first is that editing non-trivial latex code embedded in an
>>> elisp string quickly becomes tedious, whereas it’s much pleasanter
>>> in org using org-edit-speci
Hi Nicolas,
2014ko ekainak 21an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Aaron Ecay writes:
>
>> The first is that editing non-trivial latex code embedded in an elisp
>> string quickly becomes tedious, whereas it’s much pleasanter in org
>> using org-edit-special, syntax highlighting of
Hello,
Aaron Ecay writes:
> The first is that editing non-trivial latex code embedded in an elisp
> string quickly becomes tedious, whereas it’s much pleasanter in org
> using org-edit-special, syntax highlighting of src blocks, etc.
This is a no-op since you only do it a limited number of time
Hi Nicolas,
2014ko ekainak 20an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Ken Mankoff writes:
>
>> On 2014-06-20 at 04:50, Nicolas Goaziou wrote:
>>> I suggest to use existing solutions instead: configure
>>> `org-latex-classes'.
>>
>> I'm all for using existing solutions, but cannot se
Hello,
Ken Mankoff writes:
> On 2014-06-20 at 04:50, Nicolas Goaziou wrote:
>> I suggest to use existing solutions instead: configure
>> `org-latex-classes'.
>
> I'm all for using existing solutions, but cannot see how I might use
> this to easily customize export differently for different doc
2014-06-20 13:17 GMT+02:00 Ken Mankoff :
> On 2014-06-20 at 04:50, Nicolas Goaziou wrote:
> > I suggest to use existing solutions instead: configure
> > `org-latex-classes'.
>
> I'm all for using existing solutions, but cannot see how I might use
> this to easily customize export differently for d
On 2014-06-20 at 04:50, Nicolas Goaziou wrote:
> I suggest to use existing solutions instead: configure
> `org-latex-classes'.
I'm all for using existing solutions, but cannot see how I might use
this to easily customize export differently for different documents when
large amounts of LaTeX pr
Hello,
Sebastien Vauban
writes:
> Another solution which would be fine would be to have
> ‘#+BEGIN_LaTeX_HEADER ... #+END_LaTeX_HEADER’ blocks.
>
> Dunno if easy, however; but it'd be more straightforward for most users
> (no need to rely on Babel to tangle first).
I suggest to use existing s
Aaron Ecay wrote:
> 2014ko ekainak 19an, Ken Mankoff-ek idatzi zuen:
>> I'm following up on a thread suggesting a method to easily include
>> large amounts of LaTeX header material. See
>> https://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg00480.html
>>
>> Is there a way to automatically
Hi Ken,
2014ko ekainak 19an, Ken Mankoff-ek idatzi zuen:
>
> Hi,
>
> I'm following up on a thread suggesting a method to easily include
> large
> amounts of LaTeX header material. See
> https://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg00480.html
>
> Please consider this a +1 for th
Hi,
I'm following up on a thread suggesting a method to easily include
large
amounts of LaTeX header material. See
https://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg00480.html
Please consider this a +1 for that feature request.
One suggestion was:
You could have a LaTeX block and
13 matches
Mail list logo
