[O] C-c ! org-time-stamp-inactive ?
For me, C-c ! has suddenly become unbound and no longer inserts an inactive timestamp. Has this changed in the base org-mode, or most likely is this an issue with my setup? Thanks.
[O] org-block-background in 8.3.1?
I'm not sure if I still need to set org-block-background in 8.3.1. But if I do need to continue setting this, what is the new name for org- block-background? (set-face-attribute 'org-block-background nil :height (round (* 0.9 (face-attribute 'fixed-pitch :height (set-face-attribute 'org-block nil :height (round (* 0.9 (face-attribute 'fixed-pitch :height
Re: [O] org-insert-heading
Nicolas Goaziou mail at nicolasgoaziou.fr writes: Point is /before/ the ellipses here. You need to move after them, e.g., using C-f or mess with `org-special-ctrl-a/e'. Regards, OK thanks. I understood behind the ellipses at the end of a headline as before the ellipses, not after. But I still don't think it works as it is meant to. Org creates a new list item in the folded heading if the last line is a list item. Otherwise org creates a new heading at the same level as the folded heading. So * TESTcursor here, then M-enter - skfjdskjfs gives the following * TEST * cursor here - skfjdskjfs But * Test...cursor here, then M-enter gives the following * TEST - skfjdskjfs - cursor here Also the following won't create a new header or list item at all. * TEST... cursor here, then M-enter Doesn't do anything
Re: [O] org-insert-heading
Luke Crook luke at balooga.com writes: * TEST... cursor here, then M-enter Doesn't do anything The above I cannot consistently reproduce. So ignore for now. Thanks.
[O] org-insert-heading
Question concerning the behaviour of org-insert-heading; The manual states the following. If the command is used at the end of a folded subtree (i.e., behind the ellipses at the end of a headline), then a headline will be inserted after the end of the subtree. However at least in my installation (Emacs 34.3, org-mode 8.2.10), the new heading is created prior to the ellipses. For example * Heading folded... ^ cursor here, then M-RET results in the following. * Heading folded * ... ^ cursor here
Re: [O] org-insert-heading
Luke Crook luke at balooga.com writes: However at least in my installation (Emacs 34.3, org-mode 8.2.10), Emacs 24.3 obviously.
Re: [O] Org 8 Bug in interactive formula editing mode?
Nick Dokos ndokos at gmail.com writes: Nope - I tried to reproduce it with latest (both master and maint) and could not, so I suspect an error in your configuration. I experience the same issue. http://article.gmane.org/gmane.emacs.orgmode/88610 /Luke
Re: [O] Org 8 Bug in interactive formula editing mode?
Nick Dokos ndokos atzgmail.com writes: Can anybody else reproduce this? /me raises hand.
[O] org-table-edit-formulas misbehaving in 8.2.7b
I just noticed that org does not jump to the correct cell in the table when examining formulas using org-table-edit-formulas. This was working in 8.2.6. In most cases, it will jump to a different location in the buffer. Example table below. Note that I had to break the table formulae onto two lines to pass the 80 characters per line rule when posting. #+CAPTION: Sector 1 #+NAME: Sector_1 #+TBLNAME: Sector_1 | | Field Name | Size | Default Value | |---++---+---| | / | | | | | ! || bits | | |---++---+---| | | Field_1| 8 | | | | Field_2| 2 | | | | Field_3| 3 | | | | Reserved | 3 | | | | Field_4|16 | | |---++---+---| | # | RESERVED | 0 | | | ^ || res | | |---++---+---| | # | Total |32 | | | ^ || tbits | | #+TBLFM: $res=if(mod(vsum(@II..@III),8)=0,0,8-mod(vsum(@II..@III),8)):: $tbits=vsum(@II..@III)+$res
[O] #+BEGIN_SRC export in Latex
The following example is not being exported in Latex as a code block. However it is exported correctly in HTML export. org-mode version 8.2.6 #+BEGIN_SRC emacs-lisp -n -r (save-excursion (ref:sc) (goto-char (point-min))) (ref:jump) #+END_SRC
Re: [O] #+BEGIN_SRC export in Latex
Eric S Fraga e.fraga at ucl.ac.uk writes: On Wednesday, 30 Apr 2014 at 18:00, Luke Crook wrote: The following example is not being exported in Latex as a code block. However it is exported correctly in HTML export. org-mode version 8.2.6 #+BEGIN_SRC emacs-lisp -n -r (save-excursion (ref:sc) (goto-char (point-min))) (ref:jump) #+END_SRC What do you actually get in your latex export? I have just tried this and it works just fine. Mind you, my org is not quite up to date but it *is* 8.2.6. Found the culprit. I have the following in my emacs.org file ** Fontify source blocks in Latext #+BEGIN_SRC emacs-lisp (setq org-latex-listings t) #+END_SRC Setting org-latex-listings back to NIL fixed the problem.
[O] Internal Links In a table
I just noticed that links in tables Ref1, Ref2 below do not increment, whereas links in lists do. Example below. * Reference Documents | Reference | Document Description | |---+--| | Ref1Ref-1 | Ref 1| | Ref2Ref-2 | Ref 2| | Ref3Ref-3 | Ref 3| | Ref4Ref-4 | Ref 4| | Ref5Ref-5 | Ref 5| Ref-[[Ref1]], Ref-[[Ref2]], Ref-[[Ref3]] * List 1 - item1 Item 1 - item2 Item 2 - item3 Item 3 - item4 Item 4 - item5 Item 5 Item-[[item1]], Item-[[item2]]. * List 2 - item6 Item 1 - item7 Item 2 - item8 Item 3 - item9 Item 4 - item10 Item 5 Item-[[item6]], Item-[[item7]]
Re: [O] Internal Links In a table
Nicolas Goaziou n.goaziou at gmail.com writes: This is expected. Targets in tables return table number, but only among captioned tables. Otherwise, the returned value is undefined. Got it. Thanks for the info. /Luke
Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}
Rasmus rasmus at gmx.us writes: I've used this snip to recover such fields \makeatletter \let\Title\ at title \let\Author\ at author \let\Date\ at date \makeatother Obviously, this is only good for LaTeX. How would I implement this? Is including in the .tex file sufficient? Having these in the Org-mode file itself? When I try in the .tex file, it appears almost verbatim as; Title at title Author at author I cannot get the substitution to work.
Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}
Eric S Fraga e.fraga at ucl.ac.uk writes:
You could always use the new command in the org directive, assuming you
only use LaTeX export:
#+LATEX_HEADER: \newcommand{\orgauthor}{author}
#+AUTHOR: \orgauthor
This would avoid duplication.
Brilliant!! Thank you.
Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}
Bastien bzg at gnu.org writes:
Hi Luke,
Luke Crook luke at balooga.com writes:
#+LATEX_HEADER: \newcommand{\orgtitle}TITLE
My understanding is that Org's macros cannot be used
within #+... options.
HTH,
Bastien, thanks. That would certainly explain it. I think I will try to
define my own class.
Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}
I tried creating a custom class and then tried creating a custom style. But
I found the easiest to be the following;
#+AUTHOR: author
#+LATEX_HEADER: \newcommand{\orgauthor}{author}
#+EMAIL: email
#+LATEX_HEADER: \newcommand{\orgemail}{email}
#+TITLE: Title
#+LATEX_HEADER: \newcommand{\orgtitle}{Title}
#+DATE: Date
#+LATEX_HEADER: \newcommand{\orgdate}{Date}
Then in my custom Latex title page;
#+LATEX_HEADER: \input{template}
I use \orgauthor{} etc. for the relevant fields.
Works very well, apart from the duplication of author, email, date etc.
It would be great if org-mode added support for substitution to the #+
fields.
[O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}
I'm looking for a quick and dirty way to use the org-mode variables within
Latex.
I thought the following might work;
#+TITLE: A nice title
#+LATEX_HEADER: \newcommand{\orgtitle}TITLE
And then in the .tex file;
\orgtitle{}
Suggestions?
Thanks
[O] Including date in TaskJuggler exports
The following small change to ox-taskjuggler.el will export the date stored in #+DATE: Modified site/org-mode/contrib/lisp/ox-taskjuggler.el diff --git a/site/org-mode/contrib/lisp/ox-taskjuggler.el b/site/org- mode/contrib/lisp/ox-taskjuggler.el index 761e180..5a1895c 100644 --- a/site/org-mode/contrib/lisp/ox-taskjuggler.el +++ b/site/org-mode/contrib/lisp/ox-taskjuggler.el @@ -696,18 +696,30 @@ Return complete project plan as a string in TaskJuggler syntax. (mapconcat (lambda (report) (org-taskjuggler--build-report report info)) main-reports ) - ;; insert title in default reports + ;; insert title and date in default reports (let* ((title (org-export-data (plist-get info :title) info)) (report-title (if (string= title ) (org-taskjuggler-get-name project) - title))) - (mapconcat - 'org-element-normalize-string - (mapcar - (function -(lambda (report) - (replace-regexp-in-string %title report-title report t t))) - org-taskjuggler-default-reports) ) + title)) + (date (org-export-data (plist-get info :date) info)) + (report-date (if (string= date ) + (org-taskjuggler-get-name project) + date))) + (let* ((with-title (mapcar + (function + (lambda (report) +(replace-regexp-in-string %title report-title report t t))) + org-taskjuggler-default-reports)) +(with-date (mapcar +(function + (lambda (report) + (replace-regexp-in-string %date report-date report t t))) +with-title))) + + (mapconcat +'org-element-normalize-string +with-date +))
Re: [O] Changing behaviour of {:} in column view?
Sebastien Vauban sva-news@... writes:
Luke Crook wrote:
In column view, org-mode sums 3xSubtasks each having an effort of 1d
as 1d
0:00. Is there a way to change the sum to display this as 3d?
You could try to attach an ECM (« Exemple Complet Minimal », or minimal
working example) demo'ing your problem. That'd save time for people to
try to confirm the problem, and eventually fix it.
Yes, I should have done.
The following shows the sum of Tasks 1/2/3 as 1d 00:00 in column view,
which is correct as this reflects the actual number of hours of effort (8
hours a day). My question is, can this be displayed assuming 'n' hours of
effort a day and shown in days? So the sum of Effort in this case would be
displayed as 3d.
* Test
:PROPERTIES:
:ID: Tasks
:COLUMNS: %ITEM %17Effort(Effort){:}
:END:
** Task 1
:PROPERTIES:
:Effort: 1d
:END:
** Task 2
:PROPERTIES:
:Effort: 1d
:END:
** Task 3
:PROPERTIES:
:Effort: 1d
:END:
[O] Changing behaviour of {:} in column view?
In column view, org-mode sums 3xSubtasks each having an effort of 1d as 1d 0:00. Is there a way to change the sum to display this as 3d? /Luke
Re: [O] Links to headings not generated in Tables
Hi Nicolas, What about the following code. In the following, 1 and 2 are not appearing in the HTML or the Latex exorts. * test One, [[1]] and two, [[2]]. * blee | ID| Descr | Descr | |---+---+---| | 1 | One | One | | 2 | Two | Two | On Thu, Nov 21, 2013 at 1:04 PM, Nick Dokos ndo...@gmail.com wrote: Luke Crook l...@balooga.com writes: Nicolas Goaziou n.goaziou at gmail.com writes: Hello, Luke Crook luke at balooga.com writes: Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version. OK. Then could you provide an ECM? I'm unable to reproduce the problem. Regards, Hi Nicolas, The first two work correctly, the third does not generate a link for me. | [[id:6920d682-963f-412b-927b-af7dcfd57c79][Code 13]] | | [[*Code 13]] | | [[*Code 13][Code 13]] | *** Code 13 :PROPERTIES: :ID: 6920d682-963f-412b-927b-af7dcfd57c79 :END: It does for me - here's the table in the HTML output: --8---cut here---start-8--- table border=2 cellspacing=0 cellpadding=6 rules=groups frame=hsides colgroup col class=left / /colgroup tbody tr td class=lefta href=#sec-1Code 13/a/td /tr tr td class=lefta href=#sec-11/a/td /tr tr td class=lefta href=#sec-1Code 13/a/td /tr /tbody /table --8---cut here---end---8--- Org-mode version 8.2.3c (release_8.2.3c-256-g5ea022.dirty @ /home/nick/elisp/org-mode/lisp/) Nick
Re: [O] Links to headings not generated in Tables
Here is the html export. The anchor is generated, but with no text. a id=1 name=1/a/td thead tr th scope=col class=leftID/th th scope=col class=leftDescr/th th scope=col class=leftDescr/th /tr /thead tbody tr td class=lefta id=1 name=1/a/td td class=leftOne/td td class=leftOne/td /tr tr td class=lefta id=2 name=2/a/td td class=leftTwo/td td class=leftTwo/td /tr /tbody /table On Thu, Dec 19, 2013 at 11:12 AM, Luke Crook l...@balooga.com wrote: Hi Nicolas, What about the following code. In the following, 1 and 2 are not appearing in the HTML or the Latex exorts. * test One, [[1]] and two, [[2]]. * blee | ID| Descr | Descr | |---+---+---| | 1 | One | One | | 2 | Two | Two | On Thu, Nov 21, 2013 at 1:04 PM, Nick Dokos ndo...@gmail.com wrote: Luke Crook l...@balooga.com writes: Nicolas Goaziou n.goaziou at gmail.com writes: Hello, Luke Crook luke at balooga.com writes: Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version. OK. Then could you provide an ECM? I'm unable to reproduce the problem. Regards, Hi Nicolas, The first two work correctly, the third does not generate a link for me. | [[id:6920d682-963f-412b-927b-af7dcfd57c79][Code 13]] | | [[*Code 13]] | | [[*Code 13][Code 13]] | *** Code 13 :PROPERTIES: :ID: 6920d682-963f-412b-927b-af7dcfd57c79 :END: It does for me - here's the table in the HTML output: --8---cut here---start-8--- table border=2 cellspacing=0 cellpadding=6 rules=groups frame=hsides colgroup col class=left / /colgroup tbody tr td class=lefta href=#sec-1Code 13/a/td /tr tr td class=lefta href=#sec-11/a/td /tr tr td class=lefta href=#sec-1Code 13/a/td /tr /tbody /table --8---cut here---end---8--- Org-mode version 8.2.3c (release_8.2.3c-256-g5ea022.dirty @ /home/nick/elisp/org-mode/lisp/) Nick
Re: [O] Links to headings not generated in Tables
Ok. I feel quite quite silly now. Thanks /Luke On Thu, Dec 19, 2013 at 12:48 PM, Nicolas Goaziou n.goaz...@gmail.comwrote: Hello, Luke Crook l...@balooga.com writes: What about the following code. In the following, 1 and 2 are not appearing in the HTML or the Latex exorts. * test One, [[1]] and two, [[2]]. * blee | ID| Descr | Descr | |---+---+---| | 1 | One | One | | 2 | Two | Two | This is the expected behaviour. Targets are always invisible. See section 4.2 in manual. Regards, -- Nicolas Goaziou
Re: [O] Links to headings not generated in Tables
Nicolas Goaziou n.goaziou at gmail.com writes: Hello, Luke Crook luke at balooga.com writes: Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version. OK. Then could you provide an ECM? I'm unable to reproduce the problem. Regards, Hi Nicolas, The first two work correctly, the third does not generate a link for me. | [[id:6920d682-963f-412b-927b-af7dcfd57c79][Code 13]] | | [[*Code 13]] | | [[*Code 13][Code 13]] | *** Code 13 :PROPERTIES: :ID: 6920d682-963f-412b-927b-af7dcfd57c79 :END:
[O] \newpage in HTML export
Both \newpage and #+LATEX: \newpage generate page breaks in Latex. However \newpage is included verbatim in HTML export. Should I use #+LATEX: \newpage instead? /Luke
[O] Links to headings not generated in Tables
I am unable to get links of the following type to appear in Tables when exporting to HTML or Latex; [[*Heading 1][A Heading]] The links are valid in Emacs, meaning I can navigate to the target using C-c C-o. Links to headings using ID, or links to other tables ( e.g. [[tbl:aTable]]) do seem to work. /Luke
Re: [O] Links to headings not generated in Tables
Nicolas Goaziou n.goaziou at gmail.com writes: You are probably using an old Org revision (e.g. the one shipped with Emacs 24.3). Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version.
Re: [O] \newpage in HTML export
That works. But that means I need both #+HTML: and #+Latex: for the same thing. \newpage should convert as appropriate depending on the export. So, \newpage should translate to the HTML equivalent on HTML export, and the Latex equivalent on Latex export. It only works correctly on Latex export
Re: [O] \ref{} not working in HTML export
Nicolas Goaziou n.goaziou at gmail.com writes:
\ref{} is LaTeX syntax. Try [[tbl:repositories]] instead.
Regards,
That did the trick, thank you.
Re: [O] List of Figures not being generated in 8.0.3?
Thanks for highlighting this. Being able to skip the #+NAME tag in this situation makes it quite straightforward.
Re: [O] List of Figures not being generated in 8.0.3?
On Tue, Jun 11, 2013 at 4:58 PM, Rasmus ras...@gmx.us wrote:
Hi Luke!
It seems you're using v8.0.3. . .
Thank you for the feedback. I should have scrubbed my tags pre-8.0 tags to
conform to the post-8.0 world, sorry about that.
The following tags now work as expected. The List of Figures links to
the figure. I had to add a #+LABEL tag for the \ref{fig-1} to generate the
correct link.
#+NAME: fig-1
#+begin_src plantuml :file fig_1.png :cmdline -Tpng
(*) -- Test
#+end_src
#+ATTR_LaTeX: width: 2cm
#+CAPTION: Caption for Figure 1
#+LABEL: fig:fig-1
#+RESULTS: fig-1
[[file:fig_1.png]]
So, everything working again.
Thank you.
Re: [O] List of Figures not being generated in 8.0.3?
On Tue, Jun 11, 2013 at 4:58 PM, Rasmus ras...@gmx.us wrote: It seems you're using v8.0.3. . . Your example would be something like #+OPTIONS: toc:nil #+TOC: figures ## -- not implemented currently #+LATEX: \listoffigures The following generates the List of Figures #+TOC: listings No need for the specific latex tags below it seems, as #+TOC seems to output correctly in latex now. #+LATEX: \listoftables #+LATEX: \listoffigures
[O] List of Figures not being generated in 8.0.3?
I just noticed that the List of Figures is not being generated in 8.0.3.
I have a figure with;
#+LATEX: \listoffigures
#+ATTR_LaTeX: width=5.5cm
#+CAPTION: A Caption Here
#+LABEL: fig:test-figure-1
#+begin_src plantuml :file test-figure-1.png :cmdline -Tpng
plantuml stuff here
#+end_src
I have verified that the png is being generated in 8.0.3. However the
figure is not being included in the List of Figures.
References to the figure \ref{fig:test-figure-1} will render as ?? in the
Latex output. There references render as \ref{fig:test-figure-1} in the
HTML output.
Works correctly in org-more 7.8.11
Can anyone help?
Re: [O] org-mode 7.9.4 now returns org-strip-protective-commas
On Fri, Mar 22, 2013 at 1:54 PM, Nick Dokos nicholas.do...@hp.com wrote: My guess is that you have a seriously mixed-up installation. It was a load-path problem. I use an init.el file to load my ~/.emacs.d/ emacs.org initialization file, and I totally forgot to update the path to the org directory in init.el.
[O] #+begin_landscape#+end_landscape
When exporting to Latex, the system used to change the paper orientation to landscape for tables between the #+begin_landscape #+end_landscape tags. I noticed that v7.9.3f no longer does this. Were the #+begin_landscape/#+end_landscape tags deprecated? Thanks, -Luke
Re: [O] #+begin_landscape#+end_landscape
This actually works. In fact, this is how I used to control table
landscape mode before changing to #+begin_landscape/#+end_landscape.
Sorry, I should have been more clear that I use the \usepackage{pdflscape}
package that actually rotates the orientation of the page to be more easily
readable in a pdf viewer.
On Tue, Mar 26, 2013 at 2:41 PM, John Hendy jw.he...@gmail.com wrote:
On Tue, Mar 26, 2013 at 4:32 PM, Luke Crook l...@balooga.com wrote:
When exporting to Latex, the system used to change the paper orientation
to
landscape for tables between the #+begin_landscape #+end_landscape tags.
I noticed that v7.9.3f no longer does this. Were the
#+begin_landscape/#+end_landscape tags deprecated?
Not sure on the exact question; in the mean time, could you use?
#+latex: \begin{landscape}
#+latex: \end{landscape}
John
Thanks,
-Luke
Re: [O] #+begin_landscape#+end_landscape
Yes, I have. In fact, lscape is what I am using.
I haven't changed the document at all, all I have done is upgrade Emacs
which comes with org-mode v7.9.3f.
In fact, I just exported the document in on a different machine that has
org-mode 7.8.11 installed, and #+begin_landscape/#+end_landscape works as
expected.
On Tue, Mar 26, 2013 at 4:36 PM, Charles Berry ccbe...@ucsd.edu wrote:
Luke Crook luke at balooga.com writes:
When exporting to Latex, the system used to change the paper orientation
to
landscape for tables between the #+begin_landscape #+end_landscape tags.
I noticed that v7.9.3f no longer does this. Were the
#+begin_landscape/#+end_landscape tags deprecated?
Thanks,
-Luke
Did you include the landscape package??
This
,
| #+LATEX_HEADER: \usepackage{lscape}
|
| before
|
| #+begin_landscape
|
| here is some text
|
| #+end_landscape
|
| after
`
gives me three pages using the new exporter. 'before' and 'after' in
portrait
and here is some text in landscape.
HTH,
Re: [O] #+begin_landscape#+end_landscape
Sorry, pdfscape is what I am using. But I have used lscape in other docs
and #+begin_landscape/#+end_landscape does basically the same thing.
On Tue, Mar 26, 2013 at 6:03 PM, Luke Crook l...@balooga.com wrote:
Yes, I have. In fact, lscape is what I am using.
I haven't changed the document at all, all I have done is upgrade Emacs
which comes with org-mode v7.9.3f.
In fact, I just exported the document in on a different machine that has
org-mode 7.8.11 installed, and #+begin_landscape/#+end_landscape works as
expected.
On Tue, Mar 26, 2013 at 4:36 PM, Charles Berry ccbe...@ucsd.edu wrote:
Luke Crook luke at balooga.com writes:
When exporting to Latex, the system used to change the paper
orientation to
landscape for tables between the #+begin_landscape #+end_landscape tags.
I noticed that v7.9.3f no longer does this. Were the
#+begin_landscape/#+end_landscape tags deprecated?
Thanks,
-Luke
Did you include the landscape package??
This
,
| #+LATEX_HEADER: \usepackage{lscape}
|
| before
|
| #+begin_landscape
|
| here is some text
|
| #+end_landscape
|
| after
`
gives me three pages using the new exporter. 'before' and 'after' in
portrait
and here is some text in landscape.
HTH,
Re: [O] org-mode 7.9.4 now returns org-strip-protective-commas
Nick Dokos nicholas.dokos at hp.com writes: My guess is that you have a seriously mixed-up installation. That's what org-version just told me. I downloaded the latest version of Emacs for windows which includes org-mode v7.9.3f. I'll try start from there. ///Luke
[O] org-mode 7.9.4 now returns org-strip-protective-commas
I updated org-mode to 7.9.4, and now a I receive the following error from Emacs when I try to generate Latex output; Code block evaluation complete. org-export-select-backend-specific-text: Symbol's function definition is void: org-strip-protective-commas Any ideas what might be going on?
Re: [O] org-mode 7.9.4 now returns org-strip-protective-commas
Luke Crook luke at balooga.com writes: I also see the following error in 7.9.4; Code block evaluation complete. progn: Symbol's function definition is void: org-unescape-code-in-region
[O] flyspell-prog-mode and org files
Does org-mode support 'flyspell-prog-mode', in that flyspell should ignore everything within #+begin_src and #+end_src blocks? Thanks, -Luke
Re: [O] Wrong type argument listp on export
Eric Schulte schulte.eric at gmail.com writes: I've just pushed up a fix -- Eric Thanks for fixing this. -Luke
Re: [O] Include headings in export, but exclude from TOC?
suvayu ali fatkasuvayu+linux at gmail.com writes: On Mon, May 16, 2011 at 6:38 PM, Luke Crook luke at balooga.com wrote: :NOEXPORT: removes a heading from export and the TOC. Is there a tag that will only exclude a heading from appearing in the TOC? For LaTeX export the following header option should take care of this: #+OPTIONS: H:4 num:3 H:4 says export up to level 4 headlines num:3 says only number up to level 3 headlines I am not sure whether this works for the other export backends. Unfortunately the headings I want to hide are at different depths. Some are at level 3, some at level 4 etc. -Luke
[O] Include headings in export, but exclude from TOC?
:NOEXPORT: removes a heading from export and the TOC. Is there a tag that will only exclude a heading from appearing in the TOC? -Luke
[O] Re: Using babel to generate a commit log
Eric Schulte schulte.eric at gmail.com writes: Since this could be generally useful would you be willing to add it to the library of babel (org/contrib/babel/library-of-babel.org)? That would be great. If so then if you could supply a few explanatory sentences, I'll add those and the code block to the library-of-babel.org distributed with Org-mode. This function will attempt to retrieve the entire commit log for the file associated with the current buffer and insert this log into the export. The function uses the Emacs VC commands to interface to the local version control system, but has only been tested to work with Git. 'limit' is currently unsupported. -Luke
[O] Re: Using babel to generate a commit log
Suvayu Ali fatkasuvayu+linux at gmail.com writes: On Wed, 30 Mar 2011 05:38:41 + (UTC) Luke Crook luke at balooga.com wrote: 1) The code between #+begin_src and #+end_src is exported and not the result of evaluating the code (the commit log). [...] How can I fix (1). Have you tried ':exports results' as a header argument? I just tried ':exports results'. But now I get the following error when exporting the file, Cannot open load file: vc-nil -Luke
[O] Re: Using babel to generate a commit log
Jambunathan K kjambunathan at gmail.com writes: Luke Crook luke at balooga.com writes: 2) I have to add at delay of at least 5 seconds (set-for 5 t) as vc-git calls git log as an asynchronous process. If not for the delay then babel immediately returns an empty buffer and the vc-call-backend process never completes. Is there a better way that I can accomplish (2) ? Quick hints if you are willing to settle for some hacks. In vc-do-command, you may have to set OKSTATUS to 0. Track `vc-disable-async-diff' in vc.el and vc-svn.el for possible hints. I changed my code to wait until the 'Git' process completes. Luckily vc-call- backend returns the async process. #+begin_src emacs-lisp :var limit= :file test.log :exports results ;; Most of this code is copied from vc.el vc-print-log (when (vc-find-backend-function (vc-backend (buffer-file-name (current-buffer))) 'print-log) (let* ((limit (if (numberp limit) limit vc-log-show-limit)) (vc-fileset (vc-deduce-fileset t)) ;FIXME: Why t? --Stef (backend (car vc-fileset)) (files (cadr vc-fileset))) (with-temp-buffer (let ((status (vc-call-backend backend 'print-log files (current-buffer (while (not (eq 'exit (process-status status))) (sit-for 1 t)) (buffer-string) #+end_src -Luke
[O] Re: Using babel to generate a commit log
Nick Dokos nicholas.dokos at hp.com writes: Luke Crook luke at balooga.com wrote: Suvayu Ali fatkasuvayu+linux at gmail.com writes: Have you tried ':exports results' as a header argument? I just tried ':exports results'. But now I get the following error when exporting the file, Cannot open load file: vc-nil That sounds like vc does not know what backend to use: maybe you are not in a git-controlled directory? 'C-c C-c' at the top of the source block does generate the correct output though. It is just 'C-c C-e export backend' that returns this error. -Luke
[O] Re: Using babel to generate a commit log
Nick Dokos nicholas.dokos at hp.com writes: Luke Crook luke at balooga.com wrote: 'C-c C-c' at the top of the source block does generate the correct output though. It is just 'C-c C-e export backend' that returns this error. Right: (current-buffer) is not what you think it is when exporting - it is the temp buffer that the export mechanism sets up. There is a way to get the original buffer during capture, but I don't know of a similar mechanism during export. I hardwired the file name instead, but I got no further than the vc-fileset call: there seem to be all sorts of contextual assumptions that vc makes that are violated in the export context. Yes, this makes sense thanks. I'll create another thread asking how to retrieve the original buffer during the export process. -Luke
[O] How to retrieve the original buffer during export?
I have code within #+begin_src and #+end_src that has to have the original org- mode buffer during the export process, (vc-fileset (vc-deduce-fileset t)). Is there an org-mode command that can be called during the export process that will return this buffer? Thanks, -Luke
[O] Re: Using babel to generate a commit log
Nick Dokos nicholas.dokos at hp.com writes: Luke Crook luke at balooga.com wrote: Jambunathan K kjambunathan at gmail.com writes: I changed my code to wait until the 'Git' process completes. Luckily vc- call- backend returns the async process. ... or you could use a sentinel One bit of defensive programming might be to check that status *is* a process before you do the wait: vc-do-command returns a real status in the synchronous case, so if you cut-n-paste this code with some other command that does not use async, it'll blow up. I have modified the code to only check the status if the process is actually running; (with-temp-buffer (let ((status (vc-call-backend backend 'print-log files (current-buffer (when (= 0 (process-exit-status status)) (while (not (eq 'exit (process-status status))) (sit-for 1 t))) I'm not sure about using a sentinel though as this is just a callback that is executed when the process completes. Wouldn't the sentinel fire after the source block has returned? Or do you mean to wait until a variable set by the sentinel returns t? -Luke
[O] Re: Using babel to generate a commit log
Luke Crook luke at balooga.com writes: Nick Dokos nicholas.dokos at hp.com writes: There is a way to get the original buffer during capture, but I don't know of a similar mechanism during export. I hardwired the file name instead, but I got no further than the vc-fileset call: there seem to be all sorts of contextual assumptions that vc makes that are violated in the export context. org-publish-initial-buffer provides this when publishing, but I can't find an equivalent for a standard export. -Luke
[O] Re: How to retrieve the original buffer during export?
Luke Crook luke at balooga.com writes: I have code within #+begin_src and #+end_src that has to have the original org- mode buffer during the export process, (vc-fileset (vc-deduce-fileset t)). Is there an org-mode command that can be called during the export process that will return this buffer? Answered in this post: http://article.gmane.org/gmane.emacs.orgmode/40358 -Luke
[O] Re: Using babel to generate a commit log
Eric Schulte schulte.eric at gmail.com writes: Luke Crook luke at balooga.com writes: I have written the following code that uses the Emacs vc-* commands to generate a commit log. Is there a reason this processing takes place using Emacs Lisp rather than a simple shell code block, the following alternative should be simpler and more robust. #+begin_src sh :exports results :results output git log -1 #+end_src I wanted to abstract away the actual vcs used so that this code could be used by others having a different vcs. In my case I only want the commits for the file being exported and not the previous 'n' commits. I have all my specs in the same git repo. -Luke
[O] Re: Using babel to generate a commit log
Eric Schulte schulte.eric at gmail.com writes: It is true that export takes place in a fresh Org-mode buffer, however the header arguments of Org-mode code blocks are guaranteed to be evaluated in the original buffer, so a trick like the following can be used to grab the original buffer. #+begin_src emacs-lisp :var buf=(buffer-file-name (current-buffer)) :exports both (message buffer %S! buf) #+end_src That is exactly what I need. Thank you very much. -Luke
[O] Re: Using babel to generate a commit log
Luke Crook luke at balooga.com writes: Eric Schulte schulte.eric at gmail.com writes: #+begin_src emacs-lisp :var buf=(buffer-file-name (current-buffer)) :exports both (message buffer %S! buf) #+end_src The following code will now generate the commit log. #+begin_src emacs-lisp :var limit=-1 :var buf=(buffer-name (current-buffer)) :exports results ;; Most of this code is copied from vc.el vc-print-log (when (vc-find-backend-function (vc-backend (buffer-file-name (get-buffer buf))) 'print-log) (let ((limit -1) (vc-fileset nil) (backend nil) (files nil)) (with-current-buffer (get-buffer buf) (setq vc-fileset (vc-deduce-fileset t)) ;FIXME: Why t? --Stef (setq backend (car vc-fileset)) (setq files (cadr vc-fileset))) (with-temp-buffer (let ((status (vc-call-backend backend 'print-log files (current-buffer (when (and (processp status) ;; Make sure status is a process (= 0 (process-exit-status status))) ;; And that it has not terminated (while (not (eq 'exit (process-status status))) ;; Loop and sleep until complete (sit-for 1 t))) (buffer-string) #+end_src
[O] Using babel to generate a commit log
I have written the following code that uses the Emacs vc-* commands to generate a commit log. I would like the output of this code to be included when my file is exported. #+begin_src emacs-lisp :var limit= ;; Most of this code is copied from vc.el vc-print-log (when (vc-find-backend-function (vc-backend (buffer-file-name (current-buffer))) 'print-log) (let* ((limit (if (numberp limit) limit vc-log-show-limit)) (vc-fileset (vc-deduce-fileset t)) ;FIXME: Why t? --Stef (backend (car vc-fileset)) (files (cadr vc-fileset))) (with-temp-buffer (vc-call-backend backend 'print-log files (current-buffer)) (sit-for 5 t) (buffer-string #+end_src What is happening is; 1) The code between #+begin_src and #+end_src is exported and not the result of evaluating the code (the commit log). 2) I have to add at delay of at least 5 seconds (set-for 5 t) as vc-git calls git log as an asynchronous process. If not for the delay then babel immediately returns an empty buffer and the vc-call-backend process never completes. How can I fix (1). Is there a better way that I can accomplish (2) ? Thanks, -Luke
Re: [O] making flexible table formulas
On Mon, Feb 28, 2011 at 9:35 AM, Rustom Mody rustompm...@gmail.com wrote: When using orgmode for hacking on data in a table (org a la spreadsheet) I have this situation Say I am concentrating on column 2 and I want the bottom cell to be the sum of the above cells For a 7 row table with 8th row having the total I get #+TBLFM: @8$2=vsum(@1$2..@7$2) But now I have a problem: If say I add a row to the table then the next time I recompute the formula(s) the ninth row is not affected and the 8th row which is now data gets overwritten with a computation. So basically I want the @1 and @7 which are hardcoded above to be replaced by something to the effect: everything above... and the @8$2 should be something to the tune of bottom of $2 Place the rows you want to sum between horizontal separator lines (see http://orgmode.org/manual/Built_002din-table-editor.html#Built_002din-table-editor ) Then you can do the following: #+TBLFM: @8$2=vsum(@I..@II) Which means, sum the columns between the first and the second separators. -Luke ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Latex custom Title page question
I have successfully created a custom title page which I have used to replace the default version created by org-mode. Per http://orgmode.org/worg/org-tutorials/org-latex-export.html 11.2 Titles and Title Page Layout. However my title page contains the document title, date and version number. I would rather not have to create a separate custom-title.tex for each document that I create. Can I specify the Title etc. in org-mode in such a way that it can be included in the custom Title page? I have tried moving custom-title.tex into org-mode sandwiched between #+BEGIN_latex / #+END_latex commands, but this does not put the title on the first page. I have included a blank #+TITLE and #+OPTIONS: toc:nil but this still generates an empty page before my custom title page. Thanks, -Luke ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bug in column mode where parent has TODO [#A] [/]
Bernt Hansen bernt at norang.ca writes: Hi Luke, This problem was fixed in master on February 4 after release_7.4 in commit 28b88bbb11289d6c8d39ccc8dc420e7051fc0d4c. Regards, Bernt Thank you. I'll upgrade to the latest version. -Luke ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: mobileorg app can't sync
Luke Crook luke at balooga.com writes: I'll try this and report back. I started over. Followed the instructions at http://mobileorg.ncogni.to/ and everything works. Thanks, -Luke ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Importing text/data on export?
I would like to create some technical specifications in a format of (a) Cover Page, (b) Title Page, (c) Revision History, (d) TOC, (e) List of Tables, (f) List of Figures, and (g) Actual specifications/text/etc. A-C might be part of each org-mode document, or might only be included on export. However there are fields in these sections that are document specific that must be updated on export, for example; title, doc number, revision number. In addition, the Cover Page has to be of the approved format having space for the appropriate signoff signatures for the author and several approvers. Is org-mode capable of this, or is this something that has to be done outside of org-mode? For the revision history, I think creating this table on export by including the commit text from git would be great. Does anyone have any pointers on how to accomplish this? -Luke ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: mobileorg app can't sync
Greg Troxel gdt at ir.bbn.com writes: Rodney Price rodprice at raytheon.com writes: I've been trying to get MobileOrg set up with Dropbox, and I seem to have done something to make it impossible for MobileOrg to sync. Whenever I try, I get an error message like, Unexpected error: error getting mobileorg.org (paraphrased somewhat) It was syncing fine at one point, but then I decided to move my ~/org directory into the Dropbox directory, and MobileOrg evidently didn't like the change. How do I get the MobileOrg app (on an iPod Touch) to start up again? I have same same error. The steps I took are as follows; - Downloaded MobilOrg app for iPhone. - Created an account on Dropbox. - Linked Mobilorg to Dropbox account. - Created test entry in Mobilorg. - Attempted to sync. Error returned Error syncing changes. An error was encountered while attempting to fetch mobileorg.org from the server. The error was: Unexpected error On my Dropbox account, I see: MobileOrg\.dropbox -Luke I have not used dropbox, but the directory with your org files and the place in webdav that is your MobileOrg staging area are conceptually separate. You still have to org-mobile-push even if org-directory is someplace in dav space. To let someone debug this, you'll have to post your entire relevant config, including setting of org-mobile-directory, org-directory, and the URL you put in MobileOrg. (I have mobileorg syncing fine, from two instances (production and beta builds), one where I have a separate DAV dir accessed via the local filesystem, and one which is accessed on a remote server via tramp/ssh) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode at gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: mobileorg app can't sync
On Thu, Oct 21, 2010 at 11:17 AM, Erik Iverson er...@ccbr.umn.edu wrote: I have same same error. The steps I took are as follows; - Downloaded MobilOrg app for iPhone. - Created an account on Dropbox. - Linked Mobilorg to Dropbox account. - Created test entry in Mobilorg. - Attempted to sync. Error returned Error syncing changes. An error was encountered while attempting to fetch mobileorg.org from the server. The error was: Unexpected error On my Dropbox account, I see: MobileOrg\.dropbox But you need to run org-mobile-push from Emacs, and set any variables it relies on. I forget which, but they are in the manual. Ah, so I have to have an existing org-mobile-push'ified .org file in Dropbox prior to syncing? I don't think this is really made clear in the instructions. I didn't know that there was an org-mobile-push dependency between Emacs and Mobileorg. I had the impression that Mobilorg could be used stand-alone. I'll try this and report back. -Luke ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
