Thanks.
Nicolas Goaziou writes:
Hello,
"Thomas S. Dye" writes:
Is it possible to have a dedicated target in a comment?
No, it isn't. A comment is not active data.
You could, however, have a target in a drawer, that you would
not export.
Regards,
--
Thomas S. Dye
http://www.tsdye.co
Hello,
"Thomas S. Dye" writes:
> Is it possible to have a dedicated target in a comment?
No, it isn't. A comment is not active data.
You could, however, have a target in a drawer, that you would not export.
Regards,
--
Nicolas Goaziou
On Sun, Jan 28, 2018 at 6:41 AM, Ken Mankoff wrote:
> Hi Nicolas,
>
> On Sat, Jan 27, 2018 at 7:50 PM, Nicolas Goaziou
> wrote:
>
>> Hello,
>>
>> Ken Mankoff writes:
>>
>> > Adding "(setq org-icalendar-exclude-tags ":noexport:")" prior to
>> exporting
>> > does not change anything.
>>
>> What a
Hi Nicolas,
On Sat, Jan 27, 2018 at 7:50 PM, Nicolas Goaziou
wrote:
> Hello,
>
> Ken Mankoff writes:
>
> > Adding "(setq org-icalendar-exclude-tags ":noexport:")" prior to
> exporting
> > does not change anything.
>
> What about
>
> (setq org-icalendar-exclude-tags '(":noexport:"))
>
Thanks
Aloha all,
Is it possible to have a dedicated target in a comment?
I found a Common Lisp package that generates documentation in Org
mode. It outputs dedicated targets like so:
# link target 2: <>
# link target: <>
Org-lint complains about unknown fuzzy link locations and the file
won't ex
Hello,
Ken Mankoff writes:
> Adding "(setq org-icalendar-exclude-tags ":noexport:")" prior to exporting
> does not change anything.
What about
(setq org-icalendar-exclude-tags '(":noexport:"))
?
Regards,
--
Nicolas Goaziou0x80A93738
I have a custom agenda with a section that is generated with:
(todo "WAITING|VERIFY" ((org-agenda-overriding-header "Waiting or Verify")))
And it generates an Agenda section that looks like:
==
Waiting or Verify
Foo: WAITING Something
Bar: WAITING Ot
Nicolas Goaziou writes:
> Hello,
>
> "numbch...@gmail.com" writes:
>
>> Because it is not good for tangling.
>> For example, tangle the bellowing src block, the tangled source code file
>> will has `(ref:hello)` too.
>> ```
>>
>> #+begin_src emacs-lisp :tangle "data/code/src-coderef.el"
>> (mess
Hello,
"numbch...@gmail.com" writes:
> Because it is not good for tangling.
> For example, tangle the bellowing src block, the tangled source code file
> will has `(ref:hello)` too.
> ```
>
> #+begin_src emacs-lisp :tangle "data/code/src-coderef.el"
> (message "hello, world") (ref:hello)
> #+end
Hi Nicolas,
On Fri, Jan 26, 2018 at 7:32 PM, Nicolas Goaziou wrote:
> Yasushi SHOJI writes:
>
>> Also, the code converts all lower case "#+title", "+begin_src" and
>> other "#+"s to
>> the UPCASE. Is this intended? I thought we are moving away from CAP
>> to lower?
>
> This was changed a few
10 matches
Mail list logo