Re: [O] Release Org 9.1 soon ?

On Sat, Aug 26, 2017, 9:26 PM Nicolas Goaziou wrote: > Hello, > > Kaushal Modi writes: > > > I still have the org-set-tags refactoring[1] pending on my plate. > > Is there anything left to do? Do you need more time or can we merge it? > I need to

Re: [O] Release Org 9.1 soon ?

Hello, Kaushal Modi writes: > I still have the org-set-tags refactoring[1] pending on my plate. Is there anything left to do? Do you need more time or can we merge it? > I'd also like to add a new Org exporter, ox-hugo. As adding it wouldn't > break other Org

Re: [O] counter macro doesn't increment when additional macro is on same line

Argh, wish I could delete this post. I was using a defective macro definition (I pasted the wrong code in my original post!): (defun get-ts+7 () (interactive) (let ((base-date (save-excursion (re-search-backward (org-re-timestamp 'all))

Re: [O] Questions about using macro replacement

Answering without full knowledge! Thank you so much for the reply - your reply gave me several ideas. I think Q1 and Q3 are solved, but I still have no idea how to do Q2 or if it is possible. Q1, I figured it out and started using it - the {{{n}}} macros are awesome! 2. I was wondering if it

Re: [O] how to get version information on title slide with org beamer

> On Aug 26, 2017, at 10:57 AM, Eric S Fraga wrote: > > Hello all, > > I know I can use {{{modification-time(...,t)}}} say to get the revision > control system information about when the repository was last > modified. However, I would like to have other information (e.g.

[O] Consolidated capture tagets on master not in ORG-NEWS

On master, capture targets were changed in commit 0f1b5ec496, but this change isn't reflected in ORG-NEWS. Not sure if this change was intended to go in the impending 9.1 release as I'm still unfamiliar with the release workflow. Happy to update ORG-NEWS if needed. Cheers, Adrian

Re: [O] Questions about using macro replacement

Answering without full knowledge! On Wed, Aug 23, 2017 at 11:13 PM, Joon Ro wrote: > Hi, > > I have several questions about macro replacement usage. > > 1. I saw people using {{{n}}} macros, which looks very useful, but I could > not find it in current documentation about

[O] counter macro doesn't increment when additional macro is on same line

the {{{n}}} macro seems to reset to "1" if it is located on the same line as another macro that I've defined. I'm not sure if it's error with my macro or some kind or race condition-ish problem in macro expansion. Here's a minimal example: #+MACRO: ts (eval (get-ts+7)) #+BEGIN_SRC

Re: [O] Org protocol, Windows 10

2017-08-26 10:31 GMT+02:00 Nikolay Kudryavtsev < nikolay.kudryavt...@gmail.com>: > Hello Fabrice. > > If you set your protocol bookmarklet with a single slash like > "org-protocol:/capture" everything would work. > You are right: using this syntax, emacslientw gets the right url without the

Re: [O] LaTeX > PDF blocked by extender chars in filename

Aloha Eduardo, In my experience, having both org and org-plus-contrib installed is a problem. You might want to settle on the one or the other, then see if your problem persists. hth, Tom Eduardo Mercovich writes: > Hola Nicolas. > >>> The file > img/ProcesoDeDiseñoDeInteraccion.pdf >>> was

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hola Nicolas. The file > img/ProcesoDeDiseñoDeInteraccion.pdf was translated/inserted on the org buffer as > img/ProcesoDeDise%C3%B1oDeInteraccion.pdf What command did you use to "translate/insert" the filename? C-c C-l with keyboard and tab completion. + Org-mode: Org-mode version

[O] how to get version information on title slide with org beamer

Hello all, I know I can use {{{modification-time(...,t)}}} say to get the revision control system information about when the repository was last modified. However, I would like to have other information (e.g. the mercurial id). More importantly, I would like this information to appear on my

Re: [O] Release Org 9.1 soon ?

On Sat, Aug 26, 2017, 4:19 AM Nicolas Goaziou wrote: > Hello, > > I think it would be good to release Org 9.1 before the end of the month, > if possible. > > Is there any major issue left, or any important pending patch to apply > before doing the merge? > > Once this is

Re: [O] Org-lint complains about valid footnote?

On Friday, 25 Aug 2017 at 15:25, Nicolas Goaziou wrote: > Hello, > > Eric S Fraga writes: > >> In tracking down another problem with the latest version of org (more to >> follow probably), I thought using org-lint might help. With the >> attached simple example, I get: >> >>

Re: [O] problem evaluating src block on file opening

On Friday, 25 Aug 2017 at 22:01, Nicolas Goaziou wrote: > "Berry, Charles" writes: >>> On Aug 25, 2017, at 6:01 AM, Eric S Fraga wrote: >>> >>> Hello, >>> >>> Long story short: org-babel-goto-named-src-block does not seem to work, >>> at least since

Re: [O] "header-args :eval inline-only" not working

Hello, "Berry, Charles" writes: > Maybe remove the `inline-only' option as a first step. > > I have no use for org-export-use-babel, but one thing it does do is > prevent processing of headers which could be helpful if tricky header > constructions cause export to fail. Fair

Re: [O] Org protocol, Windows 10

Hello Fabrice. If you set your protocol bookmarklet with a single slash like "org-protocol:/capture" everything would work. I asked before for someone from the dev team to weight in on it, because org test seem to use both. -- Best Regards, Nikolay Kudryavtsev

[O] Release Org 9.1 soon ?

Hello, I think it would be good to release Org 9.1 before the end of the month, if possible. Is there any major issue left, or any important pending patch to apply before doing the merge? Once this is done, I will merge the "hide-column" branch in master. I will also take care of removing Org

Re: [O] [PATCH] Add TITLE export to ox-md

Hello, Jay Kamat writes: > I agree that vanilla markdown does not support title, but if ox-md does not > support any form of title, then there is disparity between the output of other > org exports and the markdown exporter. I would like to solve that disparity if >