Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

[Fabrice Popineau]

2018-01-29 2:34 GMT+01:00 Berry, Charles :

> > On Jan 28, 2018, at 3:24 PM, Nicolas Goaziou 
> wrote:
> >
> > Would you have an ECM? I don't know what is "the by-backend trick".
>
> Not a bug AFAICS.
>
> `by-backend' is a macro mentioned here:
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2013-07/msg00500.html
>
> I guess it needs to use `org-export-current-backend' if it is to be
> handled in recent org versions.
>

Thanks for the pointer to the variable but that is not the problem.

You should have a look at commit  38be85124551083d269.
It prevents evaluation of the by-backend form in parameters.

-- 
Fabrice

Re: [O] executing org-table TBLFM form changes (resets) language settings

[Rainer Stengele]

Am 26.01.2018 um 10:46 schrieb Rainer Stengele:

Am 25.01.2018 um 20:27 schrieb Nick Dokos:

Rainer Stengele  writes:


All,

My current-language-environment is "German".
Having an Org table with a TBLFM attached:

| IM Startzeit  | IM Endezeit   | Stunden | delta(x,16) | Anm. |
|---+---+-+-+--|
| [2018-01-22 Mo 19:30] | [2018-01-23 Di 14:30] |   19.00 |    3.00 |  |
|   |   | | |  |

#+TBLFM: $3=24*(date(<$2>)-date(<$1>)); %.2f::$4=$3-16.0; %.2f

entering a new timestamp correctly inserts German dayname abbrevs: ("Do", German for 
"Thu", English):

| IM Startzeit  | IM Endezeit   | Stunden | delta(x,16) | Anm. |
|---+---+-+-+--|
| [2018-01-22 Mo 19:30] | [2018-01-23 Di 14:30] |   19.00 |    3.00 |  |
| [2018-01-25 Do 14:19] |   | | |  |

#+TBLFM: $3=24*(date(<$2>)-date(<$1>)); %.2f::$4=$3-16.0; %.2f

Executing the TBLFM line with C-c C-c changes (resets) the language environment 
to English.

Now inserting a timestamp inserts "Thu" instead of "Do", that is it uses the 
English day name abbrevs:

| IM Startzeit  | IM Endezeit   |  Stunden |  delta(x,16) | 
Anm. |
|---+---+--+--+--|
| [2018-01-22 Mo 19:30] | [2018-01-23 Di 14:30] |    19.00 | 3.00 | 
 |
| [2018-01-25 Thu 14:21]|   |  |  | 
 |

#+TBLFM: $3=24*(date(<$2>)-date(<$1>)); %.2f::$4=$3-16.0; %.2f

Believe me it took me some time to find out what action in Emacs changes the 
whole lang environment.

Is that a bug or is there a language setting in the TBLFM form?

Thanks for any hint.

Regards,
Rainer



I can reproduce this if I start emacs like this:

    emacs -q -l ~/src/minimal/min.org.el /tmp/dates.org &

set the language environment inside emacs and then do C-c C-c on the TBLFM line
and try to add another date.

I cannot reproduce it when invoking emacs like this:

    LANG=de_DE.UTF-8 emacs -q -l ~/src/minimal/min.org.el /tmp/dates.org

so it seems you are right that in the first case, something changes the language
environment.


Hi Nick,

thanks for confirming.
I am running under Windows and cannot apply your environment setting like this.

Does anyboday have a chance to correct the misbehaviour in the TBLFM table code 
that changes the language settings?
I will not be able to do it on my own.

Thank you.
Regards, Rainer




Hi again,

I found out that it is the "date" function that changes the language settings. 
TBLFM lines without date calc don't change the behaviour.
May I please ask a calc expert to look into that function and investigate the 
unwanted behaviour.
I am also not sure how to easily reset the language setting manually to the 
correct one.
Can someone give me a hint please.

Thank you.
Regards, Rainer

[O] Why the new structure template engine not in Org ELPA package?

[numbch...@gmail.com]

RT.

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

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

[Yasushi SHOJI]

Hi,

On Mon, Jan 29, 2018 at 12:17 AM, Nicolas Goaziou
 wrote:
> Yasushi SHOJI  writes:
>
>> 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.
>
> Somewhat fixed. The indentation of description items is weird.

I confirm that.

Thank you, always, for your great work!

>> The other big one is indentation of begin_example.  I'm not sure
>> this one is my setting or not.
>
> Have you set `org-src-preserve-indentation' or
> `org-edit-src-content-indentation'?

Nop.

`org-src-preserve-indentation'  is nil.
`org-edit-src-content-indentation' is 2.

But, formatter still align the contents to 0.

Do you see this on your env?  Or, is it just me?

>> 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.
>
> Not sure how to fix this, or even if that should be fixed.

I'd like to have the formatter and `fill-paragraph` work in a coherent way.
But, if you, who know org much better than me, don't know, I don't think
I can help.  Though, just in case, can you elaborate a bit?


Since you fixed the big ones, I can see another issue.  This is also indentation
issue, but with a macro replacement .  Somehow, macro replacement
gets extra indentation.  Like this:

@@ -6226,7 +6200,7 @@ schedule an item:[fn:65]
  or which will become due within ~org-deadline-warning-days~.
  With {{{kbd(C-u)}}} prefix, show all deadlines in the file.  With
  a numeric prefix, check that many days.  For example, {{{kbd(C-1
- C-c / d)}}} shows all deadlines due tomorrow.
+  C-c / d)}}} shows all deadlines due tomorrow.
-- 
 yashi

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

[Berry, Charles]

> On Jan 28, 2018, at 3:24 PM, Nicolas Goaziou  wrote:
> 
> Would you have an ECM? I don't know what is "the by-backend trick".

Not a bug AFAICS.

`by-backend' is a macro mentioned here:

https://lists.gnu.org/archive/html/emacs-orgmode/2013-07/msg00500.html

I guess it needs to use `org-export-current-backend' if it is to be handled in 
recent org versions.

Chuck

Re: [O] computing the size of a tikz to png image during export

[Berry, Charles]

> On Jan 28, 2018, at 7:37 AM, Fabrice Popineau  
> wrote:
> 
> I jump on this example to ask: does this by-backend trick still work with Org 
> 9.1.6?

Probably not. Nowadays, you should reference `org-export-current-backend ', not 
`backend'.


,[ C-h v org-export-current-backend RET ]
| org-export-current-backend is a variable defined in ‘ox.el’.
| Its value is nil
| 
| Documentation:
| Name, if any, of the back-end used during an export process.
| 
| Its value is a symbol such as ‘html’, ‘latex’, ‘ascii’, or nil if
| the back-end is anonymous (see ‘org-export-create-backend’) or if
| there is no export process in progress.
| 
| It can be used to teach Babel blocks how to act differently
| according to the back-end used.
| 
| [back]
`

HTH,

Chuck

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:

> Yes. I'm in my emacs.org config file (or *scratch* buffer). I have the
> following settings:
>
> (setq org-icalendar-include-todo "all")
> (setq org-icalendar-use-deadline '(event-if-todo event-if-not-todo
> todo-due))
> (setq org-icalendar-use-scheduled '(event-if-todo event-if-not-todo
> todo-start))
> (setq org-icalendar-exclude-tags '("noicalexport"))
>
> If I then put the pointer after:
> (org-icalendar-combine-agenda-files nil)
>
> And C-x C-e and look at ~/org.ical, it is what I expect. If I change "nil"
> to "t" and re-execute that line, it contains items tagged "noexport".

I cannot reproduce it. My minimal config is:

  (require 'ox-icalendar)

  (setq org-icalendar-include-todo "all")
  (setq org-icalendar-use-deadline '(event-if-todo event-if-not-todo todo-due))
  (setq org-icalendar-use-scheduled '(event-if-todo event-if-not-todo 
todo-start))
  (setq org-icalendar-exclude-tags '("noicalexport"))
  (setq org-agenda-files '("/tmp/bug-ical.org"))
  (setq org-export-async-init-file "~/dev/mini-init.el")

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

where "/tmp/bug-ical.org" is your initial Org document and
"~/dev/mini-init.el" is the minimal config file.

Then generated ics file does not contain the entry with the
"noicalexport" tag.

Regards,

-- 
Nicolas Goaziou

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

[Fabrice Popineau]

2018-01-29 0:24 GMT+01:00 Nicolas Goaziou :

> Hello,
>
> Fabrice Popineau  writes:
>
> > Well, I think there is a problem with the current master
> > since commit 38be85124551083d269.
> >
> > The problem is that the by-backend trick which were tolerated before
> > does not work anymore.
> >
> > Tested between Org 9.1.6 as in current emacs-26.0.91 release versus
> current
> > Org master.
> >
> > More over, ignoring the no-eval parameter
> > in org-babel-parse-header-arguments
> > restores the previous behavior.
>
> Would you have an ECM? I don't know what is "the by-backend trick".
>
>
Example attached.
Actually, I wonder if you can avoid to evaluate arguments in
org-babel-parse-header-arguments
and continue to support the use of by-backend.

Regards,

Fabrice


test.org
Description: Binary data

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

[Nicolas Goaziou]

Hello,

Fabrice Popineau  writes:

> Well, I think there is a problem with the current master
> since commit 38be85124551083d269.
>
> The problem is that the by-backend trick which were tolerated before
> does not work anymore.
>
> Tested between Org 9.1.6 as in current emacs-26.0.91 release versus current
> Org master.
>
> More over, ignoring the no-eval parameter
> in org-babel-parse-header-arguments
> restores the previous behavior.

Would you have an ECM? I don't know what is "the by-backend trick".

Regards,

-- 
Nicolas Goaziou

Re: [O] Specifying the tangle filename based on the source filename?

[Diego Zamboni]

Ah, this is exactly what I was looking for. Thanks!

—Diego

> On 28 Jan 2018, at 21:47, Grant Rettke  wrote:
> 
> On Sun, Jan 28, 2018 at 7:54 AM, Diego Zamboni  > wrote:
> Hi,
> 
> I’ve been converting many of my configuration files to org-mode to better 
> document them (examples: 
> https://github.com/zzamboni/dot_emacs/blob/master/init.org 
> , 
> https://github.com/zzamboni/dot_elvish/blob/master/rc.org 
> ). Usually I have 
> a line like the following at the top of each org file:
> 
> #+PROPERTY: header-args:emacs-lisp :tangle init.el
> 
> So that all the code blocks in the file are, by default, tangled to the 
> corresponding config file. I was wondering if it might be possible to avoid 
> hardcoding the output file (“init.el” in this example) and instead derive it 
> from the source filename (“init.org ” in this case). I’ve 
> looked a bit through the manual and although I found the macro, I couldn’t 
> get it to work.
> 
> #+PROPERTY: header-args :tangle (concat (file-name-sans-extension 
> (buffer-file-name)) ".el")
> 
> #+NAME: org_gcr_2018-01-25_mara_5AA14ABD-5F82-4515-893A-B2370B6F4321
> #+BEGIN_SRC emacs-lisp
> (message "Text")
> #+END_SRC
>  
> 

Re: [O] Specifying the tangle filename based on the source filename?

[Grant Rettke]

On Sun, Jan 28, 2018 at 7:54 AM, Diego Zamboni  wrote:

> Hi,
>
> I’ve been converting many of my configuration files to org-mode to better
> document them (examples: https://github.com/zzamboni/dot_emacs/blob/
> master/init.org, https://github.com/zzamboni/dot_elvish/blob/master/rc.org).
> Usually I have a line like the following at the top of each org file:
>
> #+PROPERTY: header-args:emacs-lisp :tangle init.el
>
> So that all the code blocks in the file are, by default, tangled to the
> corresponding config file. I was wondering if it might be possible to avoid
> hardcoding the output file (“init.el” in this example) and instead derive
> it from the source filename (“init.org” in this case). I’ve looked a bit
> through the manual and although I found the macro, I couldn’t get it to
> work.
>
> #+PROPERTY: header-args :tangle (concat (file-name-sans-extension
(buffer-file-name)) ".el")

#+NAME: org_gcr_2018-01-25_mara_5AA14ABD-5F82-4515-893A-B2370B6F4321
#+BEGIN_SRC emacs-lisp
(message "Text")
#+END_SRC

Re: [O] Specifying the tangle filename based on the source filename?

[Diego Zamboni]

Hi Jack,

This is very useful. At the moment I’m still keeping my org files next to their 
generated files instead of a single tree, but your code makes me think it 
should be possible to set up a save hook to set the header-args variable for 
each file. I’m already using a save hook to run org-babel-tangle when I save an 
org file, so it shouldn’t be too difficult to add this. I’ll give it a try.

Thanks for the pointer!

Best,
—Diego


> On 28 Jan 2018, at 19:13, Jack Henahan  wrote:
> 
> I do something similar, and I use a snippet like this
> 
> #+begin_src emacs-lisp
>  (defun the-in-the-org-lib-p ()
>(and (f-this-file)
> (f-child-of? (f-this-file) the-org-lib-directory)))
> 
>  (defun the-org-lib-hook ()
>(if (the-in-the-org-lib-p)
>(progn
>  (setq-local org-babel-default-header-args:emacs-lisp
>  `((:tangle . ,(f-expand (f-swap-ext (f-filename 
> (f-this-file)) "el") the-lib-directory))
>(:noweb . "yes"))
> 
>(add-hook 'org-mode-hook 'the-org-lib-hook)
> #+end_src
> 
> `the-org-lib-directory' points to where all my Org config sources are,
> while `the-lib-directory' points to where the tangled files go. My Org
> files then have a structure like
> 
> org/whatever.org
> 
> * Configuring Whatever Features
> ** Requirements :noexport:
> #+begin_src emacs-lisp
>  ;; -*- lexical-binding: t; -*-
>  ;;; whatever.el --- Whatever functionality
> 
>  (require 'whatever)
> #+end_src
> ** Some Subfeature
> Explain how we use the feature
> #+begin_src emacs-lisp
>  (my-configuration 'stuff)
> #+end_src
> 
> ** Provides :noexport:
> #+begin_src emacs-lisp
>  (provide 'whatever)
> 
>  ;;; whatever.el ends here
> #+end_src
> 
> I have some additional configuration to tangle my lib files on save, and
> to regenerate the top-level documentation so that (in theory) the README
> is always up to date with the configuration. The :noexport: tags remove
> the noise of require and provides when I export.
> 
> Diego Zamboni  writes:
> 
>> Hi,
>> 
>> I’ve been converting many of my configuration files to org-mode to better 
>> document them (examples:
>> https://github.com/zzamboni/dot_emacs/blob/master/init.org, 
>> https://github.com/zzamboni/dot_elvish/blob/master/rc.org). Usually I
>> have a line like the following at the top of each org file:
>> 
>> #+PROPERTY: header-args:emacs-lisp :tangle init.el
>> 
>> So that all the code blocks in the file are, by default, tangled to the 
>> corresponding config file. I was wondering if it might be
>> possible to avoid hardcoding the output file (“init.el” in this example) and 
>> instead derive it from the source filename (“init.org” in
>> this case). I’ve looked a bit through the manual and although I found the 
>> {{{input-file}}} macro, I couldn’t get it to work.
>> 
>> Thanks for any help,
>> —Diego
> 

[O] BUG report [Was: computing the size of a tikz to png image during export]

[Fabrice Popineau]

Well, I think there is a problem with the current master
since commit 38be85124551083d269.

The problem is that the by-backend trick which were tolerated before
does not work anymore.

Tested between Org 9.1.6 as in current emacs-26.0.91 release versus current
Org master.

More over, ignoring the no-eval parameter
in org-babel-parse-header-arguments
restores the previous behavior.

Regards,

Fabrice





2018-01-28 16:37 GMT+01:00 Fabrice Popineau :

>
>
> 2018-01-24 8:54 GMT+01:00 Alan Schmitt :
>
>> Hello,
>>
>> I use this great trick to have both a pdf and html export of tikz
>> images:
>>
>> #+header: :file (by-backend (latex "tp6-tree.tikz") (t "tp6-tree.png"))
>> #+header: :imagemagick yes :iminoptions -density 600 :imoutoptions
>> -geometry 800
>> #+header: :results file raw
>> #+header: :fit yes
>> #+header: :headers '("\\usepackage{tikz}")
>> #+begin_src latex
>> \begin{tikzpicture}
>> …
>> \end{tikzpicture}
>> #+end_src
>>
>>
> I jump on this example to ask: does this by-backend trick still work with
> Org 9.1.6?
> Because I used it too and for some reason it fails to evaluate the
> by-backend form now.
> What am I overlooking ?
>
> Thanks,
>
> Fabrice
>
>


-- 
Fabrice Popineau
-
SUPELEC
Département Informatique
3, rue Joliot Curie
91192 Gif/Yvette Cedex
Tel direct : +33 (0) 169851950
Standard : +33 (0) 169851212
--

Re: [O] Specifying the tangle filename based on the source filename?

[Jack Henahan]

I do something similar, and I use a snippet like this

#+begin_src emacs-lisp
  (defun the-in-the-org-lib-p ()
(and (f-this-file)
 (f-child-of? (f-this-file) the-org-lib-directory)))

  (defun the-org-lib-hook ()
(if (the-in-the-org-lib-p)
(progn
  (setq-local org-babel-default-header-args:emacs-lisp
  `((:tangle . ,(f-expand (f-swap-ext (f-filename 
(f-this-file)) "el") the-lib-directory))
(:noweb . "yes"))

(add-hook 'org-mode-hook 'the-org-lib-hook)
#+end_src

`the-org-lib-directory' points to where all my Org config sources are,
while `the-lib-directory' points to where the tangled files go. My Org
files then have a structure like

org/whatever.org

* Configuring Whatever Features
** Requirements :noexport:
#+begin_src emacs-lisp
  ;; -*- lexical-binding: t; -*-
  ;;; whatever.el --- Whatever functionality
 
  (require 'whatever)
#+end_src
** Some Subfeature
Explain how we use the feature
#+begin_src emacs-lisp
  (my-configuration 'stuff)
#+end_src

** Provides :noexport:
#+begin_src emacs-lisp
  (provide 'whatever)

  ;;; whatever.el ends here
#+end_src

I have some additional configuration to tangle my lib files on save, and
to regenerate the top-level documentation so that (in theory) the README
is always up to date with the configuration. The :noexport: tags remove
the noise of require and provides when I export.

Diego Zamboni  writes:

> Hi,
>
> I’ve been converting many of my configuration files to org-mode to better 
> document them (examples:
> https://github.com/zzamboni/dot_emacs/blob/master/init.org, 
> https://github.com/zzamboni/dot_elvish/blob/master/rc.org). Usually I
> have a line like the following at the top of each org file:
>
> #+PROPERTY: header-args:emacs-lisp :tangle init.el
>
> So that all the code blocks in the file are, by default, tangled to the 
> corresponding config file. I was wondering if it might be
> possible to avoid hardcoding the output file (“init.el” in this example) and 
> instead derive it from the source filename (“init.org” in
> this case). I’ve looked a bit through the manual and although I found the 
> {{{input-file}}} macro, I couldn’t get it to work.
>
> Thanks for any help,
> —Diego

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

[Nicolas Goaziou]

Hello,

Yasushi SHOJI  writes:

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

Somewhat fixed. The indentation of description items is weird.

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

Have you set `org-src-preserve-indentation' or
`org-edit-src-content-indentation'?

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

Not sure how to fix this, or even if that should be fixed.

Regards,

-- 
Nicolas Goaziou

Re: [O] computing the size of a tikz to png image during export

[Fabrice Popineau]

2018-01-24 8:54 GMT+01:00 Alan Schmitt :

> Hello,
>
> I use this great trick to have both a pdf and html export of tikz
> images:
>
> #+header: :file (by-backend (latex "tp6-tree.tikz") (t "tp6-tree.png"))
> #+header: :imagemagick yes :iminoptions -density 600 :imoutoptions
> -geometry 800
> #+header: :results file raw
> #+header: :fit yes
> #+header: :headers '("\\usepackage{tikz}")
> #+begin_src latex
> \begin{tikzpicture}
> …
> \end{tikzpicture}
> #+end_src
>
>
I jump on this example to ask: does this by-backend trick still work with
Org 9.1.6?
Because I used it too and for some reason it fails to evaluate the
by-backend form now.
What am I overlooking ?

Thanks,

Fabrice

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 1:42 PM, Nicolas Goaziou 
wrote:

> Where did you put
>
>   (setq org-icalendar-exclude-tags '("noexport"))
>
> ?
>
> Is it accessible from `org-export-async-init-file'?
>

Yes. I'm in my emacs.org config file (or *scratch* buffer). I have the
following settings:

(setq org-icalendar-include-todo "all")
(setq org-icalendar-use-deadline '(event-if-todo event-if-not-todo
todo-due))
(setq org-icalendar-use-scheduled '(event-if-todo event-if-not-todo
todo-start))
(setq org-icalendar-exclude-tags '("noicalexport"))

If I then put the pointer after:
(org-icalendar-combine-agenda-files nil)

And C-x C-e and look at ~/org.ical, it is what I expect. If I change "nil"
to "t" and re-execute that line, it contains items tagged "noexport".

I tried to give an MWE, but perhaps it wasn't well prepared. I'm happy to
debug this via email (I'm pretty sure we're making progress). But if I can
provide a better MWE org file I am happy to do so. Please let me know how
to improve the provided bug report.

Thanks,

  -k.

[O] Specifying the tangle filename based on the source filename?

[Diego Zamboni]

Hi,

I’ve been converting many of my configuration files to org-mode to better 
document them (examples: 
https://github.com/zzamboni/dot_emacs/blob/master/init.org 
, 
https://github.com/zzamboni/dot_elvish/blob/master/rc.org 
). Usually I have a 
line like the following at the top of each org file:

#+PROPERTY: header-args:emacs-lisp :tangle init.el

So that all the code blocks in the file are, by default, tangled to the 
corresponding config file. I was wondering if it might be possible to avoid 
hardcoding the output file (“init.el” in this example) and instead derive it 
from the source filename (“init.org” in this case). I’ve looked a bit through 
the manual and although I found the {{{input-file}}} macro, I couldn’t get it 
to work.

Thanks for any help,
—Diego

Re: [O] show future scheduled date in Agenda

[Narendra Joshi]

Ken Mankoff  writes:

> I have a custom agenda with a section that is generated with:
>
> (todo "WAITING|VERIFY" ((org-agenda-overriding-header "Waiting or Verify")))
You will need to do (agenda "WAITING|VERIFY" ...) for items that are
scheduled. They will be displayed only if you have adjusted value for
`org-scheduled-delay-days`. 

> 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?
I think you can adjust the format of this with some
variable. `org-agenda-prefix-format` has a specifier "%s" for scheduling
information. There must be a variable/function for formatting scheduling
information. I couldn't quickly find it though.

> Or
>
> ==
> Waiting or Verify
>  Foo: WAITING [42d]  Something
>  Bar: WAITING [212d] Other Thing:tag:
>  Bar: VERIFY Did X happen?
This should be available with the default prefix format for agenda type
entries in your custom agenda.

Best,
-- 
Narendra Joshi

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]

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

Where did you put

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

?

Is it accessible from `org-export-async-init-file'?

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

[numbch...@gmail.com]

Thanks. @Nicolas

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

On Sat, Jan 27, 2018 at 6:58 PM, Nicolas Goaziou 
wrote:

> 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"
> 
>