This patch fixes situation when :title/:date/:index properties are
stored in the project cache and then not updated even when the
corresponding project file does get updated.
>From 06bd6a52686ec868a336d89a0ceef4359a71fb14 Mon Sep 17 00:00:00 2001
Message-ID: <06bd6a52686ec868a336d89a0ceef4359a71f
Doerthous writes:
>> Do you mean that you want the code to be indented according to the major
>> mode rules?
>>
>
> Why it relates to major mode,
>
> Currently, with :noweb-prefix set to yes, the above code will be expand to
> #+begin_src elisp
> (let ((a 0)
> (let ((b 1))
>`(,a ,b))
> #+end_
Adam Porter writes:
>> It is not about democracy or veto. We disagree about expectations for
>> #+begin_center. Expectations are not about me or you, but rather about
>> what WORG authors will expect. So, asking people makes sense.
>
> If you feel strongly enough about the background color idea (
On Wed, 27 Mar 2024 11:59:06 +0100 Ihor Radchenko wrote ---
> Over a week have passed. No objections have been raised.
> Feel free to apply the patches.
Done. See:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e9c288dfaccc2960e5b6889e6aabea700ad4e05a
and parents.
Matt writes:
> On Wed, 27 Mar 2024 11:59:06 +0100 Ihor Radchenko wrote ---
>
> > Over a week have passed. No objections have been raised.
> > Feel free to apply the patches.
>
> Done. See:
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e9c288dfaccc2960e5b6889e6aabe
Ihor Radchenko writes:
> I think that a more general approach could be allowing :noweb-prefix to
> have a value of string that will be appended to each line on the
> expansion.
With the use case discussed before, is allowing :noweb-prefix to have a
value of string means I need to provide a strin
Doerthous writes:
> Ihor Radchenko writes:
>
>> I think that a more general approach could be allowing :noweb-prefix to
>> have a value of string that will be appended to each line on the
>> expansion.
>
> With the use case discussed before, is allowing :noweb-prefix to have a
> value of string
Ihor Radchenko writes:
> I still feel that what you are really looking for is major-mode-specific
> indentation, not a prefix. Because indentation may require tabs, not
> spaces. Or may interfere with programming language.
I kind of understand what you mean: what I need is just the no
option, af
Doerthous writes:
> I kind of understand what you mean: what I need is just the no
> option, after the expansion (maybe with the help of some
> after-expansion-hooks), indent the source block according to
> major-mode. Right?
>
> I will try to find some hooks after expansion and some APIs to
> in
Thanks, I'll check it out.
Adam Porter writes:
> Sure. I've pushed that, adding a "co-authored-by" line for Bastien.
Thanks!
--
Bastien Guerry
Ihor Radchenko writes:
> Bastien, may you please check FSF records?
Yes, Laurence copyright status is okay.
--
Bastien Guerry
Hello,
I created the attached code to be able to preview SVG in org mode. Please
comment if you have suggestions for a better approach.
It works by having svg in a #+begin_src svg block and running org-format-svg on
it.
I took inspiration from org-format-latex and wonder whether it should be m
On 3/29/24 04:48, Ihor Radchenko wrote:
Also, we may consider re-using inlinetask style for TODO: entries.
Rather than
#+begin_center
TODO: Even better, find a volunteer to maintain this information!
#+end_center
We can do
TODO Even better, ...
That is a lot of
Aloha all,
Adam Porter writes:
On 3/29/24 04:48, Ihor Radchenko wrote:
Also, we may consider re-using inlinetask style for TODO:
entries.
Rather than
#+begin_center
TODO: Even better, find a volunteer to maintain this
information!
#+end_center
We can do
TOD
Hi Tom,
On 3/29/24 18:30, Thomas S. Dye wrote:
Here's another potential solution that I find useful.
d. Keeping tasks under a heading held back from export.
I have a capture template that saves tasks about the document under a *
Tasks :no-export: heading. To keep the agenda sane, I don't add
16 matches
Mail list logo
