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 create a new patch. Will do so in the coming wee
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 functionality, would it be safe to
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))
(match-str
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 i
> 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. the
> mercurial id).
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
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 macro replacement (
> h
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 emacs
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 super
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 tr
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 8.3.4
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 beam
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 done, I will merge the "h
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:
>>
>> 5 high Missing
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 b862c24b9f or thereabouts?
>>
>> Confirmed
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 enough. I removed `
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
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 St
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
> possible.
The point of "md"
19 matches
Mail list logo