[O] following org links to gnus messages and window management

Hello, I'm using escreen (http://www.emacswiki.org/emacs/EmacsScreen) to manage my windows in emacs, typically keeping gnus on screen 0, org agenda and related todo files on screen 2, and so on. When I follow a link in a task to a gnus file, this takes over the current frame, and when I'm done de

Re: [O] [PATCH] Only set org-hide foreground if one is available

Hi Nikolai, Nikolai Weibull writes: > Sorry, I realize that I was way too terse. No problem. Thanks for the detailed explanations, makes sense. I pushed your patch. Thanks, -- Bastien

Re: [O] [patch] capture property table-line-pos can be a function

Hi Thomas, Thomas Holst writes: > I am sorry, I used =git format-patch= for the patches assuming all will > go well. Here are both patches with rewritten commit messages. Hopefully > I made them well. No problem -- the game now is to find the small differences between your original patches and

Re: [O] [PATCH] Fix clock table when there are links in headings.

Hi Bastien, 2014-03-18 20:10 GMT+04:00 Bastien : > Hi Alexey, > > Alexey Lebedeff writes: > >> Sorry, I failed to explicitly mention that it was in agenda >> clockreport. It was in the screenshot, but I forgot that clocktable is >> used in other places than agenda. > > You need to configure `org-

Re: [O] A JavaScript Org-mode parser I'm experimenting with

Hi François, hi Masafumi, François Pinard writes: > Just want to share that, for the last few days, I'm playing with a > JavaScript Org-mode parser written by Masafumi Oyamada, found here: > > https://github.com/mooz/org-js Looks great! Thanks for this Masafumi. > Might someone, familiar en

Re: [O] [PATCH] Fix clock table when there are links in headings.

Hi Alexey, Alexey Lebedeff writes: > But I don't want do disable linking agenda clocktable row to the > original heading, it's very convenient. I just want it to look pretty, > but the thing from the screenshot looks really ugly. Patch affects > execution only when :link is true. Of course you'

Re: [O] [patch] capture property table-line-pos can be a function

Hi Bastien, · Bastien wrote: > Hi Thomas, > > Thomas Holst writes: > >> I am sorry, I used =git format-patch= for the patches assuming all will >> go well. Here are both patches with rewritten commit messages. Hopefully >> I made them well. > > No problem -- the game now is to find the small diff

Re: [O] Navigating from agenda causes incorrect expansion of children

Hi Dan, you need to have (agenda t) in `org-show-siblings'. See `org-show-siblings' docstring for details. HTH, -- Bastien

Re: [O] Strange newline characters in org-export-as-html

Hi Grant, Grant Rettke writes: > My config is definitely to blame. > > With my config newlines are output as:  Okay, thanks for confirming, -- Bastien

Re: [O] HTML table export options essentially undocumented

On Mar 18, 2014 4:45 PM, "Nicolas Goaziou" wrote: > Did you try column groups? > > (info "(org) Column groups") > > It is not back-end specific. No, I hadn't... I was in a rush and trying to do something that I thought would be simple (and just a quick and dirty one-off export). Even given more

Re: [O] Is there an environment for Org syntax?

Hi Fletcher, Fletcher Charest writes: > When I use the edit buffer (by pressing C-c '), my Org syntax is > indented properly (in accordance with org-indent-mode, which is set > to t). The code block itself looks like this after editing: > > #+BEGIN_SRC org :exports code >   ,* Top level headline

Re: [O] following org links to gnus messages and window management

Hi Alan, Alan Schmitt writes: > When I follow a link in a task to a gnus file, this takes over the > current frame, and when I'm done dealing with the message, I have to > "winner-undo" my way until I restore my window configuration. This is > not very convenient. > > My questions are: > - is th

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Luke Crook writes: > I tried creating a custom class and then tried creating a custom style. But > I found the easiest to be the following; > > > #+AUTHOR: > #+LATEX_HEADER: \newcommand{\orgauthor}{} [...] > Works very well, apart from the duplication of author, email, date etc. You could a

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Eric S Fraga writes: > Luke Crook writes: > >> I tried creating a custom class and then tried creating a custom style. But >> I found the easiest to be the following; >> >> >> #+AUTHOR: >> #+LATEX_HEADER: \newcommand{\orgauthor}{} > > [...] > >> Works very well, apart from the duplication of

Re: [O] HTML table export options essentially undocumented

Hi James, James Harkins writes: > It may be useful to link to this from the page on tables in HTML > export, then. I slightly enhance the "Tables in HTML export" section of the manual. Thanks, -- Bastien

Re: [O] Post() evaluates but fails in export

Hi Nicolas, Nicolas Goaziou writes: > The attached patch should fix the issue. Could you confirm it? I just tested and it fixes the issue. I'll Jarmo double-confirm this. (The patch does not apply on maint anymore though :/...) Thanks in advance for apply it! -- Bastien

Re: [O] following org links to gnus messages and window management

Hi Bastien, Bastien writes: >> - if not, is there a way to copy a link then open it using the >> minibuffer (I would then do the switch to screen 0 manually)? > > This does not use the minibuffer but you could add that: > > (progn > (org-next-link) > (org-open-link-from-string >(org-el

[O] why I got the message

hi, all my emacs is GNU Emacs 24.0.95.1 (x86_64-redhat-linux-gnu, GTK+ Version 2.24.10), org is 8.2.5h when I used C-c | to add a table 5X2 as follows: | d | | | | | |---+---+---+---+---| | d | | | | | and place cursor at "d" in 1 x 1, and (1) press M-x org-table-delete-

Re: [O] Problem with org-bibtex-read with fields type, key

Hi Stefan, "Stefan-W. Hahn" writes: > I have a little problem with org-bibtex function org-bibtex-read: > > My bibtex entries have the keyword "type" and "key". When > reading such an entry with org-bibtex-read I get an alist > with the entries ":type" and ":key" each twice. Yes, I confirm the

Re: [O] why I got the message

Hi Dilon, I cannot reproduce the problem. Please M-x org-version RET and report the *whole* indication, it might be a problem in your installation. Best, -- Bastien

Re: [O] special table from clock

Hi Martin, Martin writes: > But I'm unsure how to store the data for that in my APPT entries: I > could use properties (but how?) and I would really like to use the > CLOCK entries for calculating the times. Well, this *is* a complex request. One quick idea is to use properties and to look a

Re: [O] link interfering with brackets when abbreviated

Samuel Wales writes: > btw, the nuclear power plant MUST be painted blue. FWIW, I strongly disagree. -- Bastien

Re: [O] verbatim and apostrophes

Hi Alan, Alan Schmitt writes: > A suggestion could be to allow any text inside the markers, except for > the marker itself which would need to be escaped. Escaping could take > the form of doubling the marker: > > ~"foo bar"~ --> "foo bar" > ~"foo ~~ bar"~ --> "foo ~ bar" > > As I've not thought

Re: [O] why I got the message

Bastien gnu.org> writes: > > Hi Dilon, > > I cannot reproduce the problem. > > Please M-x org-version RET and report the *whole* indication, > it might be a problem in your installation. I got the message when M-x org-version RET: Org-mode version 8.2.5h (8.2.5h-dist @ /study/doctor/note/org-

Re: [O] why I got the message

Dillon Peng writes: > Bastien gnu.org> writes: > >> >> Hi Dilon, >> >> I cannot reproduce the problem. >> >> Please M-x org-version RET and report the *whole* indication, >> it might be a problem in your installation. > > I got the message when M-x org-version RET: > Org-mode version 8.2.5h (

Re: [O] [patch][ox-html] Stylistic changes

On 2014-03-18 15:46, Rasmus wrote: Rick Frankel writes: On 2014-03-17 23:36, Rasmus wrote: When you refer above to "utf-8 entities", do you mean the named html entities (e.g., <) or the actual utf-8 encoded characters? The latter. Do M-x describe-char on such an character. Emacs will tell yo

Re: [O] why I got the message

hi, I figured out! after restart emacs with (require 'ox), I found a strange error message: Wrong type argument: integerp, (48 . 57) and the error message disapeared after updating emacs from 24.0.95-1 to 24.1-7, and M-S- also works! thanks again!

Re: [O] [patch][ox-html] Support for level based containers

On 2014-03-18 15:41, Rasmus wrote: Rick Frankel writes: On 2014-03-17 23:31, Rasmus wrote: A general rule is that the section element is appropriate only if the element's contents would be listed explicitly in the document's outline. So, using this definition, in html5, the wrappers should

Re: [O] Incorrect hexification in URLs in LaTeX Export

On Mar 18, 2014, at 17:24, "R. Michael Weylandt" wrote: > Can't comment on Andreas's issue about unescaping text when it's given to org > already escaped. Hi Bastien, TLDR: remove ?\= from org-link-escape-chars. I looked at this again and I think I've stumbled on another small issue relati

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Hello, Bastien writes: > Luke Crook writes: > >> It would be great if org-mode added support for substitution to the #+ >> fields. > > Nicolas, what do you think? In the current model, macros are considered part of Org syntax, like, e.g., text markup. One advantage is that they can be parsed,

Re: [O] Post() evaluates but fails in export

Hello, Bastien writes: > (The patch does not apply on maint anymore though :/...) It never applied to maint. It was built on top of master. ISTR some features don't exist in maint (is it :post header?). Regards, -- Nicolas Goaziou

Re: [O] Post() evaluates but fails in export

Hi Nicolas, Nicolas Goaziou writes: >> (The patch does not apply on maint anymore though :/...) > > It never applied to maint. It was built on top of master. ISTR some > features don't exist in maint (is it :post header?). Oh, yes, of course. Feel free to apply it on master then. Thanks! --

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Hi Nicolas, thanks for the thorough answer, I agree. Can we sum it up as "Macros are only available in headlines and paragraphs", for the sake of clarifying the Macro section in the manual? Also, it seems that macros are only fontified in headlines and paragraphs, which matches the short descrip

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Bastien writes: > thanks for the thorough answer, I agree. Champagne! ;) > Can we sum it up as "Macros are only available in headlines and > paragraphs", for the sake of clarifying the Macro section in the > manual? The manual states: "in paragraphs, verse blocks, table cells and some keywo

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Nicolas Goaziou writes: > Bastien writes: > >> thanks for the thorough answer, I agree. > > Champagne! ;) Hehe. >> Can we sum it up as "Macros are only available in headlines and >> paragraphs", for the sake of clarifying the Macro section in the >> manual? > > The manual states: > > "in par

[O] Property EXPORT_OPTIONS ignored?

Hi, i'm trying to exclude one section from the toc Following http://orgmode.org/manual/Export-settings.html in following example section 2 shoud not appear in the toc, but it appears. #+OPTIONS: toc:t * Section 1 * Section 2 :PROPERTIES: :EXPORT_OPTIONS: toc:nil :END: What I'm missing? TIA, Ro

Re: [O] OrgStruct for Python source code

Hi Karl, Karl Voit writes: > This should fold all defs. Unfortunately, this does not work at my > side. Did I make a mistake or do I have to limit myself to matching > comment lines only? simply turn on orgstruct-mode in a python buffer and try M-x org-cycle RET on a def: it will fold it. `org

Re: [O] Property EXPORT_OPTIONS ignored?

Hi Robert, Robert Eckl writes: > i'm trying to exclude one section from the toc > > Following http://orgmode.org/manual/Export-settings.html in following > example section 2 shoud not appear in the toc, but it appears. > > #+OPTIONS: toc:t > * Section 1 > * Section 2 > :PROPERTIES: > :EXPORT_OP

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Rasmus gmx.us> writes: > > I've used this snip to recover such fields > > \makeatletter > \let\Title\ title > \let\Author\ author > \let\Date\ date > \makeatother > > Obviously, this is only good for LaTeX. > How would I implement this? Is including in the .tex file sufficient? Having

[O] bug#17040: 24.3.50; Emacs + Org mode hangs

> From: Sebastien Vauban > Date: Wed, 19 Mar 2014 15:57:36 +0100 > > Anyway, here's the backtrace I got: Thanks for the effort, but as I said several times, such backtraces are not useful without the Lisp backtrace part. All I can say from this backtrace is that you were deep inside some hook s

[O] org-html-do-format-code: End of buffer

When I export org-file to the HTML by means of C-c C-e h H (as HTML buffer) I get the following error: org-html-do-format-code: End of buffer and exporting doesn't finish (buffer with the result doesn't appear). Mentioned org-file is pretty simple: #+name: basic-python #+begin_src python :resu

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Eric S Fraga 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: \orgauthor > > This would avoid duplication. Brilliant!! Thank you.

Re: [O] mobile-org http links not recognized on iPhone

I've just tested this and you are right. If I follow the orgmode convention of http links and use the View in mobile-org, the links are clickable. But if I cut and paste a link like http://www.something.com in orgmode, it's not clickable in mobile-org View. I guess I'll have to follow the orgmode

[O] OrgStruct for Python source code

Hi! I am evaluating methods to fold Python source code. I stumbled over orgstruct-mode which looks quite cool to me. My first test with (setq orgstruct-heading-prefix-regexp "^[ ]*##[ ]+\*[ ]") worked out of the box. Unfortunately, this attempt requires a comment linke for each Python-def

Re: [O] [BABEL] BUG Re: Omitting try/catch blocks from tangled R code?

John Hendy gmail.com> writes: [deleted] > > > > I think the default behavior should be reverted, as tangling and > > exporting are two different things. When I tangle, I want to see the > > code blocks as they are in the org document (with possible variables and > > expansions) but not to create

Re: [O] OrgStruct for Python source code

* Bastien wrote: > Hi Karl, Hi Bastien! > simply turn on orgstruct-mode in a python buffer and try > M-x org-cycle RET on a def: it will fold it. Oh, even better! :-) Thanks for the pointer! -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https

Re: [O] Navigating from agenda causes incorrect expansion of children

I think there must be a bunch of us who are experiencing this, because I am too. The fix does not work for me. 3b is never shown. * test 1 *** 2a SCHEDULED: <2014-03-19 Wed> * 3a * 3b *** 2b On 3/19/14, Bastien wrote: > Hi Dan, > > you need to have (agenda t) in `org-show-siblings'. >

Re: [O] Post() evaluates but fails in export

Bastien writes: > Oh, yes, of course. Feel free to apply it on master then. Done. Regards, -- Nicolas Goaziou

[O] Obsolete information in worg

In this section: http://orgmode.org/worg/org-configs/org-config-examples.html#sec-2_2 the information about yasnippet is out of date; more up-to-date information is available in the manual: http://orgmode.org/org.html#Interaction Hence, I suggest removing the references to yasnippet from the wo

[O] Small bug in example code

In the function org-toggle-iimage-in-org in the page http://orgmode.org/worg/org-configs/org-config-examples.html#sec-2_2 the call (iimage-mode) needs to be (iimage-mode 'toggle), otherwise iimage-mode is only ever switched on. (iimage-mode does toggle when used as a command, but not when called

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Bastien writes: > Nicolas Goaziou writes: > >> As you noticed, secondary strings are omitted in the manual, but still >> valid locations: titles in headlines or inlinetasks, inline footnotes, >> and plain list item tags. > > Any reason not to mention secondary strings? No reason besides clarity

Re: [O] preview and default class [8.2.5h (release_8.2.5h-677-g55b0a3 @ /home/youngfrog/sourcetrees/org-mode/lisp/)]

Hi Bastien, > Mhh, yes, I'm for moving it to the previewing section. > > Do you want to get commit access so that you can fix this directly? > Otherwise, just send a patch and I'll apply it. > > Thanks! Here's a patch. I can commit it if you like, but I don't want to do so without some review (it

Re: [O] Obsolete information in worg

Hi Reuben, Reuben Thomas writes: > In this section: > > http://orgmode.org/worg/org-configs/org-config-examples.html#sec-2_2 > > the information about yasnippet is out of date; more up-to-date > information is available in the manual: > > http://orgmode.org/org.html#Interaction > > Hence, I sugg

Re: [O] Small bug in example code

Reuben Thomas writes: > In the function org-toggle-iimage-in-org in the page > > http://orgmode.org/worg/org-configs/org-config-examples.html#sec-2_2 > > the call (iimage-mode) needs to be (iimage-mode 'toggle), otherwise > iimage-mode is only ever switched on. (iimage-mode does toggle when > use

Re: [O] Post() evaluates but fails in export

Nicolas Goaziou writes: > Bastien writes: > >> Oh, yes, of course. Feel free to apply it on master then. > > Done. Thanks, -- Bastien

Re: [O] Navigating from agenda causes incorrect expansion of children

Samuel Wales writes: > I think there must be a bunch of us who are experiencing > this, because I am too. > > The fix does not work for me. > > 3b is never shown. > > * test 1 > *** 2a > SCHEDULED: <2014-03-19 Wed> > * 3a > * 3b > *** 2b This is not the same case: in Dan's example, the s

Re: [O] org-html-do-format-code: End of buffer

Hi Andrey, Andrey Tykhonov writes: > What is the problem? Why mentioned error occurs? How can I fix it? Please > help. Can you reproduce the error with (setq debug-on-error t) and send us the backtrace? If you can do this from an uncompiled version of Org, that's even better. -- Bastien

Re: [O] Small bug in example code

OK, I have commits ready to push as soon as you install my SSH key! On 19 March 2014 22:52, Bastien wrote: > Reuben Thomas writes: > > > In the function org-toggle-iimage-in-org in the page > > > > http://orgmode.org/worg/org-configs/org-config-examples.html#sec-2_2 > > > > the call (iimage-mo

Re: [O] #+LATEX_HEADER:\newcommand{\orgtitle}{{{{TITLE}}}}

Luke Crook writes: > Rasmus gmx.us> writes: > >> >> I've used this snip to recover such fields >> >> \makeatletter >> \let\Title\ title >> \let\Author\ author >> \let\Date\ date >> \makeatother >> >> Obviously, this is only good for LaTeX. >> > > How would I implement this? Is including

Re: [O] org-html-do-format-code: End of buffer

Hi Bastien! Bastien writes: > Hi Andrey, > > Andrey Tykhonov writes: > >> What is the problem? Why mentioned error occurs? How can I fix it? Please >> help. > > Can you reproduce the error with (setq debug-on-error t) and send us > the backtrace? If you can do this from an uncompiled version

Re: [O] Small bug in example code

Reuben Thomas writes: > OK, I have commits ready to push as soon as you install my SSH key! Done, -- Bastien

Re: [O] Navigating from agenda causes incorrect expansion of children

for the first time in many, many years of HATING this behavior and trying to debug it and trying to defadvice around it, i have a lead on it. thank you. so where is the setting to show EVERYTHING? this is HUGE. On 3/19/14, Bastien wrote: > Samuel Wales writes: > >> I think there must be a bu

Re: [O] org-html-do-format-code: End of buffer

Hi Andrey, Andrey Tykhonov writes: > I've tried to reproduce with (toggle-debug-on-error) and now (setq > debug-on-error t) but buffer with the backtrace doesn't appear. Maybe you need to try from a fresh Emacs session: in this case, just add (setq debug-on-error t) in your .emacs.el. > I can

Re: [O] Navigating from agenda causes incorrect expansion of children

Samuel Wales writes: > so where is the setting to show EVERYTHING? (add-hook 'org-agenda-after-show-hook 'show-all) :) -- Bastien

Re: [O] Namespace problem org-mode / Clojure

That's great! A big thanks to Bastien for fixing the elisp, and keeping Clojure code blocks working smoothly. Speaking of org-mode and Clojure... You may be interested in the recent Clojure org-mode postings at the Google group: https://groups.google.com/forum/#!topic/clojure/hWqPXn1_pK4 https

Re: [O] Navigating from agenda causes incorrect expansion of children

expands logbook, but i can take it from here. thank you! unfortunately, that is not a global solution as there are various other places where the same behavior occurs. On 3/19/14, Bastien wrote: > Samuel Wales writes: > >> so where is the setting to show EVERYTHING? > > (add-hook 'org-agenda-

Re: [O] OrgStruct for Python source code

On 3/19/2014 3:39 PM, Karl Voit wrote: I am evaluating methods to fold Python source code. simply turn on orgstruct-mode in a python buffer and try M-x org-cycle RET on a def: it will fold it. Another option is to use Thorsten Jolitz's excellent outshine mode ( http://orgmode.org/worg/org-tuto

Re: [O] OrgStruct for Python source code

On 3/19/2014 9:19 PM, Ilya Shlyakhter wrote: Another option is to use Thorsten Jolitz's excellent outshine mode ( http://orgmode.org/worg/org-tutorials/org-outside-org.html ). I've written a small extension that allows it to fold language elements: http://www.broadinstitute.org/~ilya/outshine-p

Re: [O] following org links to gnus messages and window management

Alan Schmitt writes: > Hi Bastien, > > Bastien writes: > >>> - if not, is there a way to copy a link then open it using the >>> minibuffer (I would then do the switch to screen 0 manually)? >> >> This does not use the minibuffer but you could add that: >> >> (progn >> (org-next-link) >> (o

Re: [O] [BABEL] BUG Re: Omitting try/catch blocks from tangled R code?

Charles Berry writes: > John Hendy gmail.com> writes: > > [deleted] >> > >> > I think the default behavior should be reverted, as tangling and >> > exporting are two different things. When I tangle, I want to see the >> > code blocks as they are in the org document (with possible variables and >