Great thanks!
On Thu, Jan 9, 2020 at 8:50 AM Nicolas Goaziou wrote:
> I removed this since you have signed FSF papers.
Got it, I'll leave it out in the future and add a note in
org-contribute.org in case someone
else missed the implication of that paragraph.
Looking at git, it seems that was introduced in 9.2.
On 10/01/2020 10:32 am, sergio ruiz wrote:
I am getting:
eval: Symbol’s function definition is void: org-macro--get-property
I am using:
Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/Applications/Emacs.app/Contents/Resources/lisp/org
It's interesting that you are unable to reproduce the result. I have Emacs 26.3
(9.0) on macOS Mojave 10.14.6. I have reproduced it with `emacs -q`, so the
problem is not my init file. Then I don't know what the culprit is and am
curious and available to try things to find it.
Miguel
On Thu,
I am getting:
eval: Symbol’s function definition is void: org-macro--get-property
I am using:
Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/Applications/Emacs.app/Contents/Resources/lisp/org/)
Mark set
Is this a newer function?
Thanks!
> You can use elisp code to look up the property
On 10/01/2020 9:23 am, sergio ruiz wrote:
* Report section
:PROPERTIES:
:url: http://www.googole.com
:END:
I'd like to have several sections like this. Each section woudl have
different values for the same property. They would make different
calls to respective url. something like
#+BEGIN_SR
On 10/01/2020 5:56 am, sergio ruiz wrote:
#+BEGIN_SRC shell :var url_input=url_name
curl url_input
#+END_SRC
#+RESULTS:
^^ This doesn't work. It is trying to use "url_input" in the curl command.
You need a $ in front of the name when referencing a variable in the shell:
#+BEGIN_SRC shell
I realized this is related to my previous post, but if i could do this, it
would save alot of work.
I would like to access the values of the properties inside the (shell) code
block.
Thanks!
* Report section
:PROPERTIES:
:url: http://www.googole.com
:END:
I'd like to have several secti
sergio ruiz writes:
> Is there a way to reference the values of properties, so that at render time,
> the document does something like:
>
> * Opening section
> :PROPERTIES:
> :section: test
> :time: 1 day
> :END:
>
> Is there a way to do something like.. this section is the section
> and
Is there a way to reference the values of properties, so that at render time,
the document does something like:
* Opening section
:PROPERTIES:
:section: test
:time: 1 day
:END:
Is there a way to do something like.. this section is the section and
will be done in
which would render as:
Hello,
John Hendy writes:
> I had no problem doing the following:
>
> - C-x (
> - C-e C-s l p C-n
> - C-x )
> - go to first of my results headlines
> - C-u 51 C-x e
>
> It sounds like you already tried this... are you using `C-x (` or are
> you defining the macros via elisp?
I'm doing the follo
Hello,
Kyle Meyer writes:
> As an alternative, can't you type `C-u C-c C-e` (i.e. call
> org-export-dispatch with a prefix argument)?
Thank you for the suggestion -- this accomplishes exactly what I want!
Next time, I'll remember to RTFM before asking for help :P
Cheers,
Jack
On Thu, Jan 9, 2020 at 12:24 PM Jack Kamm wrote:
>
> Hello,
>
> I have an org-mode file, and am exporting one of its subtrees to a
> beamer presentation.
>
> I would like to use a keyboard macro for this, because re-exporting the
> presentation requires a lot of keypresses:
> - Jump to the appropr
Jack Kamm writes:
> I would like to use a keyboard macro for this, because re-exporting the
> presentation requires a lot of keypresses:
> - Jump to the appropriate heading
> - Start the dispatcher
> - Toggle subtree export (C-s)
> - Finally, export
>
> So, I defined a keyboard macro to do all th
Hello,
I have an org-mode file, and am exporting one of its subtrees to a
beamer presentation.
I would like to use a keyboard macro for this, because re-exporting the
presentation requires a lot of keypresses:
- Jump to the appropriate heading
- Start the dispatcher
- Toggle subtree export (C-s)
Hello,
Nicolas Goaziou writes:
> Thank you for the patch! Some comments follow.
>
> It would be useful to also explain what happens when the value is
> `reorganize-frame', `split-window-right', or `split-window-right', e.g.,
> that previous window configuration is restored.
>
> It may be useful
Hey, all.
I am trying to set a string at the head of the file and use it in different
places in the file.
Everything works correctly for somethign like ruby, but I am not sure how do do
this with a shell command.
Just sets the string to the url
#+NAME: url_name
#+BEGIN_SRC ruby
"http://www.goo
Hello,
Tom Gillespie writes:
> This is a tiny change to the manual to account for the change from org
> -> ol in the org-man example. There may be other references in the
> manual that have similar issues but I did not check.
Applied. Thank you.
> TINYCHANGE
I removed this since you have sign
Hello,
Miguel Morin writes:
> I put "refiling" in the title as that is the moment when things go awry, so I
> noticed it when I refiled items.
>
> I updated Org to 9.3.1 and confirm that the bug is still present. Because I
> got some compatibility problems, I tested it with `emacs -q`, in whic
On Thursday, 9 Jan 2020 at 16:09, alain.coch...@unistra.fr wrote:
> It seems to me that this is what you are referring to, Eric: using the
> :ignore: tag in conjunction with package 'ox-extra'.
Thanks. I haven't tried it but, looking at the documentation & code, it
does what my little snippet do
> Note that my implementation is old and it could very well be that
> later versions of org have introduced something to cater for this
> use case. I have org customizations going back over 10 years...
It seems to me that this is what you are referring to, Eric: using the
:ignore: tag in con
Hi, sorry I missed this thread in the peri-holiday rush, just want to say
thank you all for ironing out the difficulties arsing from that change
earlier.
On Tue, Jan 7, 2020 at 4:06 AM Nicolas Goaziou
wrote:
> Hello,
>
> Jack Kamm writes:
>
> > Attached is a patch to restore the window configur
Fraga, Eric writes:
> On Thursday, 9 Jan 2020 at 11:38, Sven Bretfeld wrote:
>> Works like a charm! Almost perfect. Thank you very much. One problem:
>> For some reason the :ignoreheading: tag causes the PROPERTY drawer to be
>> exported.
>
> Ah, probably because the property drawer is now not i
On Thursday, 9 Jan 2020 at 11:38, Sven Bretfeld wrote:
> Works like a charm! Almost perfect. Thank you very much. One problem:
> For some reason the :ignoreheading: tag causes the PROPERTY drawer to be
> exported.
Ah, probably because the property drawer is now not in the right place
(i.e. immed
Fraga, Eric writes:
> On Thursday, 9 Jan 2020 at 09:20, Sven Bretfeld wrote:
>> Hi everybody
>>
>> Is this possible?
>>
>> ** headline <-- not exported
>>:PROPERTIES: <-- not exported
>>Some content. <-- exported
>
> yes. I do this all the time to add structure to a document, struc
On Thursday, 9 Jan 2020 at 09:20, Sven Bretfeld wrote:
> Hi everybody
>
> Is this possible?
>
> ** headline <-- not exported
>:PROPERTIES: <-- not exported
>Some content. <-- exported
yes. I do this all the time to add structure to a document, structure
that is not required in the
Hi Vladimir,
The main difference I have noticed is that you can have multiple blocks
with the same :noweb-ref header argument, and they will be concatenated on
tangle. I use this in some of my files to progressively build a block of
code which is then referenced somewhere else. With #+name, you ca
Hi everybody
Is this possible?
** headline <-- not exported
:PROPERTIES: <-- not exported
Some content. <-- exported
The reason is that I use to finely pre-structure articles, starting with
org-brain and gradually developing each node into a paragraph of the
article. So basically eac
27 matches
Mail list logo