I wrote a piece of code like below:
#+NAME: inc-file
#+BEGIN_SRC elisp :results value raw :exports results :var file="
common.inc.org"
(concat "#+INCLUDE: /path/to/include-dir/" file) ;; path is cal-ed from
path of current-buffer file
#+END_SRC
#+CALL: inc-file(file="a.org") :results raw
but t
El 25/03/14 19:27, Marcin Borkowski ha escrit:
> Dnia 2014-03-25, o godz. 16:00:01
> Pere Quintana Seguí napisał(a):
>
>> I log most of my work with org-mode. Some of my tasks are repetitive,
>> this is, I do them weekly or daily (i.e. empty mail inbox). After many
>> years, the logs are very lon
El 25/03/14 19:47, Achim Gratz ha escrit:
> I've long resorted to using two drawers back-to-back:
That seems to be the most straightforward solution. I'll do that.
Maybe org-mode could do this automatically. A variable would determine
when log entries should be archived in the second drawer.
I w
Hello,
I'm collaborating on a paper with some colleagues, and I convinced them
to use org-mode. I'm trying to make sure the paper is as self-contained
as possible (I don't want them to have to change their emacs
configuration file). To change the documentclass name of the exported
article, I added
On Wed, 26 Mar 2014 04:10:02 -0400, Pere Quintana Seguí
wrote:
El 25/03/14 19:27, Marcin Borkowski ha escrit:
Dnia 2014-03-25, o godz. 16:00:01
Pere Quintana Seguí napisał(a):
I log most of my work with org-mode. Some of my tasks are repetitive,
this is, I do them weekly or daily (i.e. em
Hello,
KDr2 writes:
> I wrote a piece of code like below:
>
> #+NAME: inc-file
> #+BEGIN_SRC elisp :results value raw :exports results :var file="
> common.inc.org"
> (concat "#+INCLUDE: /path/to/include-dir/" file) ;; path is cal-ed from
> path of current-buffer file
> #+END_SRC
>
> #+CALL: i
Alan Schmitt writes:
> Hello,
>
> I'm collaborating on a paper with some colleagues, and I convinced them
> to use org-mode. I'm trying to make sure the paper is as self-contained
> as possible (I don't want them to have to change their emacs
> configuration file).To change the documentclass name
Nicolas Goaziou writes:
> You can use a macro here:
>
> #+MACRO: inc-file #+INCLUDE: /path/to-include-dir/$1
>
> {{{inc-file(a.org)}}}
Err, no. Macros are also expanded after INCLUDE keywords. The only code
executed before these are handled is
`org-export-before-processing-hook'.
Hi Michael,
Pontus Michael writes:
> Source block fontification is achieved by copying source block
> contents into temporary buffer under appropriate major mode and
> mirroring face text-properties into original buffer.
thanks for the change and the detailed explanations.
Eric, I'm short of t
Achim Gratz writes:
[...]
> I've long resorted to using two drawers back-to-back:
>
> :LOGBOOK:
> …stuff…
> :END:
> :CLOSED:
> …old stuff…
> :END:
Thanks for this. Very simple yet elegant solution.
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.2, Org release_8.2.5h-687-g9d39aa
Hello,
When I attempt to run M-x org-bibtex on a .org file with non-standard
bibtex types that have a tag, they fail to export if
org-bibtex-tags-are-keywords is set to t. This persists even if I add the
bibtex type to org-bibtex-types. I checked, and this problem persists with
a minimal init fil
Hi All,
The evaluation of code block
#+begin_src R :file img.pdf
hist(rnorm(100))
#+END_SRC
does not output "img.pdf" to the current folder. But if I use "~/img.pdf",
file will be saved to "~/". Am I missing something here?
Thanks,
YZ
--
Yi Zhang
Thanks very much.
I use dynamic block now, by adding `org-update-all-dblocks' to
`org-export-before-processing-hook'.
On Wed, Mar 26, 2014 at 5:42 PM, Nicolas Goaziou wrote:
> Nicolas Goaziou writes:
>
> > You can use a macro here:
> >
> > #+MACRO: inc-file #+INCLUDE: /path/to-include-dir/$1
Yi Zhang wrote:
> The evaluation of code block
>
> #+begin_src R :file img.pdf
> hist(rnorm(100))
> #+END_SRC
>
> does not output "img.pdf" to the current folder. But if I use "~/img.pdf",
> file will be saved to "~/". Am I missing something here?
You miss ":results graphics", for example:
#+b
Feng Shu wrote:
> Alan Schmitt writes:
>>
>> I'm collaborating on a paper with some colleagues, and I convinced
>> them to use org-mode. I'm trying to make sure the paper is as
>> self-contained as possible (I don't want them to have to change their
>> emacs configuration file).To change the docum
Feng Shu writes:
> Alan Schmitt writes:
>
>> Hello,
>>
>> I'm collaborating on a paper with some colleagues, and I convinced them
>> to use org-mode. I'm trying to make sure the paper is as self-contained
>> as possible (I don't want them to have to change their emacs
>> configuration file).To c
Hello Fabrice,
Fabrice Niessen writes:
> You could have a look at Orgmk [1], a suite of shell scripts I wrote
> with the following goals in mind:
>
> - to be more productive, by running the export only when the source Org
> files are updated.
>
> - *to share some common Emacs and Org configura
Hello,
Alan Schmitt writes:
> I'm collaborating on a paper with some colleagues, and I convinced them
> to use org-mode. I'm trying to make sure the paper is as self-contained
> as possible (I don't want them to have to change their emacs
> configuration file). To change the documentclass name o
Hi:
I want to write a hook to menupulate org babel output,
The problem is: How can I get two points info: [pointA] and [pointB]
in my hook function?
#+begin_src R :results output raw drawer
tbl <- data.frame(a=c(1,2,3),b=c(3,2,1))
print(ascii(tbl),type="org")
#+END_SRC
#+RESULTS:
:RESULTS:
[poin
On 2014-03-23 17:01, Marcin Borkowski wrote:
Hi list,
publishing doesn't work. I guess that I broke something;). May the
source and publishing directories be the same? I have this in my
init.el:
(setq org-publish-project-alist
'(("fnis2014"
:base-directory "~/directory"
:publ
Feng Shu writes:
> Hi:
Hi Feng,
Look at the :post header argument.
(info "(org) post")
> I want to write a hook to menupulate org babel output,
> The problem is: How can I get two points info: [pointA] and [pointB]
> in my hook function?
>
> #+begin_src R :results output raw drawer
> tbl <- dat
Hello Nicolas,
Nicolas Goaziou writes:
>> My questions are:
>> - is there a way to do this without an emacs-lisp block?
>
> Yes there is, with a BIND keyword, e.g.:
>
> #+BIND: org-latex-classes (("article" "\\documentclass{llncs}"
> ("\\section{%s}" . "\\section*{%s}")))
>
> Though you need
I wrote a blog entry to describe all the dynamic tricks I used in the
exporting:
http://kdr2.com/tech/emacs/orgmode-export-process.html
On Wed, Mar 26, 2014 at 7:54 PM, KDr2 wrote:
> Thanks very much.
>
> I use dynamic block now, by adding `org-update-all-dblocks' to
> `org-export-before-proce
Alan Schmitt writes:
> It is in a :noexport: section already. Here is a quick test.
>
> Exporting
>
> * Test :noexport:
>
> #+begin_src sh
> echo "date 1" >> ~/tmp/results
> echo `date` >> ~/tmp/results
> #+end_src
>
> #+begin_src sh :exports results :results silent
> echo "date 2" >> ~/tmp/resul
Hello,
KDr2 writes:
> I wrote a blog entry to describe all the dynamic tricks I used in the
> exporting:
>
> http://kdr2.com/tech/emacs/orgmode-export-process.html
Thank you for sharing.
For completeness, there is another step involved in the process before
switching to back-ends: run function
Hi,
May I bump up this thread?
Thanks for your help.
Regards,
Francesco
"Francesco Pizzolante" wrote:
> Hi,
>
> This is not a definitive patch. It's just a first step in getting a better
> one.
>
> The issue is the fact that, when exporting to PDF, in some cases, Org tells
> that the export h
Hello,
Xavier Garrido writes:
> Thanks for your answer. Maybe I will try your solution. Otherwise
> I will run a "before-parse-hook" to change fn:XX to something unique
> (by adding buffer name for example.
We could do it by default.
One problem is that INCLUDE keyword is a very simple feature
Hello,
"Francesco Pizzolante"
writes:
>> The issue is the fact that, when exporting to PDF, in some cases, Org tells
>> that the export has been done successfully while the PDF file has not been
>> produced!
>>
>> As an example, if you open the target PDF file with Adobe Reader and, in the
>>
Nicolas Goaziou writes:
> Alan Schmitt writes:
>
>> It is in a :noexport: section already. Here is a quick test.
>>
>> Exporting
>>
>> * Test :noexport:
>>
>> #+begin_src sh
>> echo "date 1" >> ~/tmp/results
>> echo `date` >> ~/tmp/results
>> #+end_src
>>
>> #+begin_src sh :exports results :resu
I find if I accidentally return over an item's date, I get a second
agenda buffer for that date.
That seems fine, but what I don't like is that from now on, any org
agenda commands go to THAT buffer, rather than going into the old agenda
buffer, which I keep around all the time.
So I have, for ex
Oh, I'll star this mail, and add it to my post later, thanks again :)
On Wed, Mar 26, 2014 at 10:31 PM, Nicolas Goaziou wrote:
> Hello,
>
> KDr2 writes:
>
> > I wrote a blog entry to describe all the dynamic tricks I used in the
> > exporting:
> >
> > http://kdr2.com/tech/emacs/orgmode-export-p
Hi Bastien,
Bastien wrote:
> Sebastien Vauban writes:
>>
>> (add-hook 'text-mode-hook
>> (lambda ()
>> (message "Turning on Flyspell in buffer `%s'" (buffer-name))
>> (flyspell-mode 1)))
>>
>> Though, as you can see, that has the perverse impact th
Hi Nicolas,
Thanks for your answer.
>>> As an example, if you open the target PDF file with Adobe Reader and, in the
>>> meantime, you export your Org file again to PDF, you'll see that Org will
>>> tell
>>> you it's OK (Process Completed) while, if you look at the *Org PDF LaTeX
>>> Output* bu
Aaron Ecay writes:
> Hi Rainer,
>
> This patch looks very promising. (I have not had a chance to test the
> implementation yet).
Thanks - please let me know as soon as you tested it.
> One issue might be the name of the “org” variable
> – maybe this should instead be “.org” or “_org” to less
"Francesco Pizzolante" writes:
>> IOW, it cannot tell the difference between a successful export and an
>> export failure with an already existing PDFFILE.
>
> This is not true as this code checks for the `errors' variable in all
> cases. With an already existing PDFFILE, you will end up with t
Sebastien Vauban
writes:
> Hello,
>
> I use Flyspell in all my text-mode and prog-mode buffers, hence as well
> in my Org mode buffers -- as they ultimately derive from Text mode.
>
> I do that with:
>
> (add-hook 'text-mode-hook
> (lambda ()
> (message "Turning
Hi!
I am using custom links like "[[photo:FirstnameLastname.jpg]]" in my
contacts.org.
Those links stopped working recently. Whenever I try to click or C-c
C-c the link, I get "user-error: No link found".
Same happens with file: links.
Both links work outside of my PROPERTIES drawer.
--
mail|
seems to work. thank you.
On 3/25/14, Bastien wrote:
> Fixed again, thanks and sorry for this regression.
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. And
ANYBODY can get it.
Denmark: free Karina Hansen NOW.
If I f.ex make a beautiful table in org-mode:
|-+-+---++-|
| foo | bar | xyzzy | hukarz | |
| qux | | corge | grault | garply waldo fred plugh |
| baz | | || |
|-+-+---+--
Alan Schmitt writes:
> I usually export in offline mode, so I can keep editing while the export
> is going on.
If you and your colleagues export asynchronously, then the document
class (and other environment changes) can be placed in an initialization
file for the asynchronous process.
An appro
Nicolas Goaziou wrote:
> "Francesco Pizzolante" writes:
>
>>> IOW, it cannot tell the difference between a successful export and an
>>> export failure with an already existing PDFFILE.
>>
>> This is not true as this code checks for the `errors' variable in all
>> cases. With an already existing PD
On 2014-03-26 at 14:32, Esben Stien wrote:
> If I f.ex make a beautiful table in org-mode:
>
> |-+-+---++-|
> | foo | bar | xyzzy | hukarz | |
> | qux | | corge | grault | garply waldo fred plugh |
> | baz | | |
On 26 March 2014, Esben Stien wrote:
|-+-+---++-|
| foo | bar | xyzzy | hukarz | |
| qux | | corge | grault | garply waldo fred plugh |
| baz | | || |
|-+-+---++-
Hi Nicolas,
Le 26/03/2014 15:41, Nicolas Goaziou a écrit :
Hello,
Xavier Garrido writes:
Thanks for your answer. Maybe I will try your solution. Otherwise
I will run a "before-parse-hook" to change fn:XX to something unique
(by adding buffer name for example.
We could do it by default.
On
Hello,
Here is a patch that allows for the output of ocaml babel blocks to be
captured. It also makes the parsing of the resulting value more robust:
results of type "string list" are now converted to a table, for
instance.
At the moment I only check for results of the form "verbatim" or
"output"
Hello,
Some time ago, the "flowing text" inside Org buffers was rendered in the
`org-default' face.
It isn't the case anymore. Is it a bug on my side?
Best regards,
Seb
--
Sebastien Vauban
Hello,
I've been playing with block chaining to generate some dot file then to
export then as images. I had a little trouble finding the number of '\'
I need to put in front of a quote if I want the quote to be quoted. Here
is a way to make it work:
--8<---cut here---start
Hello Tom,
t...@tsdye.com (Thomas S. Dye) writes:
> Alan Schmitt writes:
>
>> I usually export in offline mode, so I can keep editing while the export
>> is going on.
>
> If you and your colleagues export asynchronously, then the document
> class (and other environment changes) can be placed in
Hello,
Alan Schmitt writes:
> I've been playing with block chaining to generate some dot file then to
> export then as images. I had a little trouble finding the number of '\'
> I need to put in front of a quote if I want the quote to be quoted. Here
> is a way to make it work:
>
> #+name: foo
>
Nicolas Goaziou wrote:
Hello,
Nicholas and Francesco,
"Francesco Pizzolante"
writes:
The issue is the fact that, when exporting to PDF, in some cases, Org tells
that the export has been done successfully while the PDF file has not been
produced!
As an example, if you open the target PDF
Daimrod writes:
> Feng Shu writes:
>
>> Hi:
> Hi Feng,
>
> Look at the :post header argument.
> (info "(org) post")
Thanks ...
>
>> I want to write a hook to menupulate org babel output,
>> The problem is: How can I get two points info: [pointA] and [pointB]
>> in my hook function?
>>
>> #+begi
Hi Alan,
Alan Schmitt writes:
> Feng Shu writes:
>
>> Alan Schmitt writes:
>>
>>> Hello,
>>>
>>> I'm collaborating on a paper with some colleagues, and I convinced them
>>> to use org-mode. I'm trying to make sure the paper is as self-contained
>>> as possible (I don't want them to have to cha
On Wed, 26 Mar 2014 18:19:35 -0400, Nicolas Goaziou
wrote:
Hello,
Alan Schmitt writes:
I've been playing with block chaining to generate some dot file then to
export then as images. I had a little trouble finding the number of '\'
I need to put in front of a quote if I want the quote to b
Daimrod writes:
> Feng Shu writes:
>
>> Hi:
> Hi Feng,
>
> Look at the :post header argument.
> (info "(org) post")
How to use elisp in :post directly,
for example:
#+begin_src R :results output raw drawer :post (align-multi-table)
#+end_src
#+begin_comment
(defun align-multi-table (&optio
Ken Mankoff writes:
> Looks perfect to me.
Yeah, it seems it's because of non mono font, but I didn't think it
would be that drastic difference.
, but I confirmed it, by copying something I sent to a person with a
gmail account into my emacs and it was perfect again.
I guess this issue does
Hi,
Sacha Chua made a nice hack to export checkboxes as unicode symbols to
HTML here:
http://sachachua.com/blog/2014/03/emacs-tweaks-export-org-checkboxes-using-utf-8-symbols/?shareadraft=baba27119_533313c944f64
(defun sacha/org-html-checkbox (checkbox)
"Format CHECKBOX into HTML."
(case che
Feng Shu writes:
> Daimrod writes:
>
>> Feng Shu writes:
>>
>>> Hi:
>> Hi Feng,
>>
>> Look at the :post header argument.
>> (info "(org) post")
>
> How to use elisp in :post directly,
I don't think you can.
You have to use it this way (not tested):
#+NAME: align-multi-table
#+BEGIN_SRC emacs
On Mon, Mar 24, 2014 at 7:00 PM, Feng Shu wrote:
> John Hendy writes:
>
>> On Mon, Mar 24, 2014 at 10:22 AM, Feng Shu wrote:
>>> Hi everyone
>>>
>>> I want to R output table with plot, I use a solution below,
>>> Who can tell me other solutions?
>>>
>>
>> I sort of follow the below, but I think
tell him or her to click on "show original".
or export to tsv, which will sometimes work.
in maint, if you encrypt with org-crypt on an entry with children, then
demote, then decrypt, the subtree levels do not match up.
for example, the children can end up as uncle/aunt nodes.
maybe something like these are possibilities:
1) optionally adjust subtree levels to match the location
John Hendy writes:
> On Mon, Mar 24, 2014 at 7:00 PM, Feng Shu wrote:
>> John Hendy writes:
>>
>>> On Mon, Mar 24, 2014 at 10:22 AM, Feng Shu wrote:
Hi everyone
I want to R output table with plot, I use a solution below,
Who can tell me other solutions?
>>>
>>> I sort
Daimrod writes:
> Feng Shu writes:
>
>> Daimrod writes:
>>
>>> Feng Shu writes:
>>>
Hi:
>>> Hi Feng,
>>>
>>> Look at the :post header argument.
>>> (info "(org) post")
>>
>> How to use elisp in :post directly,
>
> I don't think you can.
>
> You have to use it this way (not tested):
> #+NA
62 matches
Mail list logo