Re: [O] Dedicated targets

[Thomas S. Dye]

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.com

Re: [O] Dedicated targets

[Nicolas Goaziou]

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

Re: [O] Bug: iCal export does not respect :noexport: tag [9.1.6 (9.1.6-31-gffa5f3-elpa @ /Users/kdm/.emacs.d/elpa/org-20180122/)]

[Ken Mankoff]

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 about
>>
>>   (setq org-icalendar-exclude-tags '(":noexport:"))
>>
>
> Thanks for the hint.
>
> (setq org-icalendar-exclude-tags '("noexport"))
>
> It works without the ':' characters.
>

BUT a bug still exists. If I export with async:

(org-icalendar-combine-agenda-files t)

Then all entries show up. If I export blocking

(org-icalendar-combine-agenda-files nil)

Then the `exclide-tags` setting is respected.

   -k.

Re: [O] Bug: iCal export does not respect :noexport: tag [9.1.6 (9.1.6-31-gffa5f3-elpa @ /Users/kdm/.emacs.d/elpa/org-20180122/)]

[Ken Mankoff]

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 for the hint.

(setq org-icalendar-exclude-tags '("noexport"))

It works without the ':' characters.

Thank you!

  -k.

[O] Dedicated targets

[Thomas S. Dye]

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 export to html.


All the best,
Tom

--
Thomas S. Dye
http://www.tsdye.com

Re: [O] Bug: iCal export does not respect :noexport: tag [9.1.6 (9.1.6-31-gffa5f3-elpa @ /Users/kdm/.emacs.d/elpa/org-20180122/)]

[Nicolas Goaziou]

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

[O] show future scheduled date in Agenda

[Ken Mankoff]

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 Other Thing:tag:
 Bar: VERIFY  Did X happen?


Is it possible to show SCHEDULED dates for these items? I often set something 
to WAITING and re-schedule it for +7d, but would like to know at a glance when 
something is scheduled (if it is). The new Agenda section might look like:

==
Waiting or Verify
 Foo: WAITING [2018-06-10 Sun] Something
 Bar: WAITING [2018-09-22 Sat] Other Thing:tag:
 Bar: VERIFY  Did X happen?

Or

==
Waiting or Verify
 Foo: WAITING [42d]  Something
 Bar: WAITING [212d] Other Thing:tag:
 Bar: VERIFY Did X happen?

Is this fairly easy to do? Can the Table view support something like this?

Thanks,

  -k.

Re: [O] [feature] prepend comment char before org-babel-ref

[Nicolas Goaziou]

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"
>> (message "hello, world") (ref:hello)
>> #+end_src
>
> You need to add "-r" switch so Org knows you want to remove coderefs:
>
>   #+begin_src emacs-lisp :tangle "data/code/src-coderef.el"
>   (message "hello, world") (ref:hello)
>   #+end_src

I meant

  #+begin_src emacs-lisp -r :tangle "data/code/src-coderef.el"

Re: [O] [feature] prepend comment char before org-babel-ref

[Nicolas Goaziou]

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_src

You need to add "-r" switch so Org knows you want to remove coderefs:

  #+begin_src emacs-lisp :tangle "data/code/src-coderef.el"
  (message "hello, world") (ref:hello)
  #+end_src


Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] [RFC] Moving "manual.org" into core

[Yasushi SHOJI]

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 days ago. See commit
> 13424336a6f30c50952d291e7a82906c1210daf0.

Thanks.  I pulled the head and read that.

I still see quite a lot of changes when I reformat the
manual.org.

A big one seems to be the indentation of description lists.
The formatter seems to prefer aligning the begging of a description
to the begging of a term.  But manual.org has some indentation.

The other big one is indentation of begin_example.  I'm not sure
this one is my setting or not.

Some minor diff is caused by links.  The formatter doesn't fold a
paragraph when link is at the end of the line. That is, if a paragraph
has a [[link like this]], the line goes on and on till the next fold
point.
-- 
 yashi