Re: [O] adapted org-flag-drawer to hide newlines of consecutive drawers to save lines
Hello, Bastien writes: > Beside, `org-flag-drawer' is currently under revision since Michael > report on slowliness (and recent discussion with Tod and Aaron.) I rewrote `org-flag-drawer' a few days ago. It shouldn't be slow if cache is activated. Regards, -- Nicolas Goaziou
Re: [O] Bug: property drawers within code blocks interfere [8.2.2 (8.2.2-elpa @ /home/tod/.emacs.d/.cask/24.3.50.1/elpa/org-20131108/)]
Hello Aaron and Bastien,
Aaron Ecay wrote:
> The property drawer after the code block is a red herring: the following
> file (with no real property drawer at all) misbehaves on property
> setting and getting functions, with the fake properties in the code
> block behaving as though they pertained to the headline (as can be
> confirmed by M-: (org-entry-get nil "EMAIL")):
>
> * stuff for bug report
> #+BEGIN_SRC emacs-lisp
> (setq i-am-a-string
> "
> :PROPERTIES:
> :EMAIL: %^{Email}
> :PHONE: %^{Phone number}
> :END:
> ")
> #+END_SRC
>
> I think this problem of unselective regex searches will also affect uses
> of e.g. org-scheduled-time-regexp
To come back on what you suspect, I must admit I still have the problem
described in the thread http://comments.gmane.org/gmane.emacs.orgmode/60959,
that is:
--8<---cut here---start->8---
* Some explanation of Org mode timestamps...
#+begin_src org
,SCHEDULED: <2013-11-21 Thu +1w/12d>
#+end_src
For ranges, you can try:
#+begin_src org
,<2013-11-20 Wed 15:00-17:00 +1w>.
#+end_src
--8<---cut here---end--->8---
both "events" will appear in my agenda (for next Wed/Thu).
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [PATCH] [Babel] Add line number to "Processing code block..." message
Hello Eric, Eric Schulte wrote: > "Sebastien Vauban" writes: >> Here is a small patch to improve the messages displayed by Org Babel when >> processing code blocks: now, you get the line number added to the output, so >> that you can easily find afterward which block had problems, if such things >> were reported in the *Messages* buffer. >> >> - (message "org-babel-exp processing...")) >> ... >> + (message "Processing %s code block at line %d..." lang line)) > > Thanks for this patch, I've applied it and then tweaked the wording of the > message. I thought my wording was more clear from a user perspective, but I don't mind with yours, and I'm happy that line has been added. Much clearer to use the information from the *Messages* buffer. Best regards, Seb -- Sebastien Vauban
Re: [O] Bug: property drawers within code blocks interfere [8.2.2 (8.2.2-elpa @ /home/tod/.emacs.d/.cask/24.3.50.1/elpa/org-20131108/)]
Bastien writes: > Hi Aaron and Tod, > > Aaron Ecay writes: > >> This seems like an excellent use case for the parser: basically a bunch >> of uses of org-*-regexp and org-re-property need to be augmented with >> a check like: >> (not (memq (org-element-type (org-element-at-point)) '(src-block >> example-block ...))) >> >> A better alternative might be to use the parser to find the property >> drawer in the first place (instead of a regex). Either way, it seems >> like the best strategy might be to fix all uses of these problem >> variables at once, which is a big undertaking. > > Also don't forget the cost in terms of speed. It's fine to fix the > behavior of Org for such cases, but those cases are rare, and could > be explicitely prevented. If the general fix does not slow down the > parsing too much, then I'm all for it. Nicolas might have better > insight here than me. With newly introduced parser cache, the cost is amortized when using `org-element-at-point' and `org-element-context'. With a little care, the overhead is negligible. Therefore, these functions should be used whenever possible. I'm slowly working on introducing these functions in basic parts of Org (e.g. fontification, indentation). Then I will target other functions not using them yet. There's a lot to do. Help is welcome. IMO, at the bare minimum, new or rewritten functions should use them. For example, a way to correctly find the property drawer associated to the current section is to use something like the following: (save-excursion (outline-previous-heading) (unless (bobp) (let ((limit (save-excursion (outline-next-heading) (point (catch 'exit (while (re-search-forward org-property-start-re limit t) (let ((drawer (org-element-at-point))) (when (eq (org-element-type drawer) 'property-drawer) ... (throw 'exit ... Regards, -- Nicolas Goaziou
Re: [O] adapted org-flag-drawer to hide newlines of consecutive drawers to save lines
Hi Nicolas, Nicolas Goaziou writes: > Bastien writes: > >> Beside, `org-flag-drawer' is currently under revision since Michael >> report on slowliness (and recent discussion with Tod and Aaron.) > > I rewrote `org-flag-drawer' a few days ago. It shouldn't be slow if > cache is activated. Is the cache activated by default? If so, does it come with some inconveniency? If not, should we simply activate it all the time? Thanks, -- Bastien
Re: [O] Bug: property drawers within code blocks interfere [8.2.2 (8.2.2-elpa @ /home/tod/.emacs.d/.cask/24.3.50.1/elpa/org-20131108/)]
Nicolas Goaziou writes: > I'm slowly working on introducing these functions in basic parts of Org > (e.g. fontification, indentation). Then I will target other functions > not using them yet. There's a lot to do. Help is welcome. IMO, at the > bare minimum, new or rewritten functions should use them. Well, I spent all my "time credits" with the merge of Org into Emacs, so I already know I won't be able to help in the next few weeks, but I hope some other core contributors will -- thanks a lot for undertaking this changes. -- Bastien
Re: [O] [PATCH] org-collector: enable specifying a default table-value as a parameter
Hi Mark, the patch is unreadable -- can you resend it as an attachment? Thanks! -- Bastien
Re: [O] org-insert-heading
Hi Thomas, t...@tsdye.com (Thomas S. Dye) writes: > With the following Org mode file, there is a dead space where > org-insert-heading doesn't do anything. In the following example, if the > point is on either of the empty lines marked [dead space] no heading is > created. > > Is this behavior intended? I can't reproduce it... anyone? -- Bastien
Re: [O] C-c ' and mail sources
Hi François, François Pinard writes: > Not a big problem, and I expect that someone on this list will reply > that this is an Org limitation (a way to say that the bug is innocuous > enough to not deserve a correction). I rather use the word limitation > for a bug which has been documented :-). In any case, this is a > bug. Not that I want to distract readers from the original issue, but being curious: do you have the same problem with #+BEGIN_SRC message ? Thanks, -- Bastien
Re: [O] A weird warning and a test (eager macro expansion) error
Hi Achim, Achim Gratz writes: > This patch fixes the error, but it looks strange (indentation is still > unchanged for clarity). Not sure if this an Ert or Emacs error, though. I suggest you handle this the way you prefer: either by committing this in Org before asking emacs-devel@, or by asking first then see of this needs to be fixed upstream? I won't have time to digg this issue further, sorry. -- Bastien
[O] Open linked file outside Emacs
Hello, how does org-mode 'decide' whether a linked filed (C-c C-l) should be opened (C-c C-o) inside an Emacs buffer or opened by an external program? I am using Emacs 24.3 for Windows and org-mode 8.2 PDF files are opened in Acrobat, but JPGs are opened in a buffer (but are not properly displayed, even if I switch doc-view on); but I'd prefer to open them with my standard viewer (Irfan). Thanks, Christof
[O] refernce to call results
Hi all, how do I reference the results of a #+call line? Here are my unsuccessful attempts: --8<---cut here---start->8--- * Test call results #+name: curdir #+begin_src sh echo "$PWD" #+end_src #+results: curdir : /home/andreas/tmp/junk/2013/11 #+name: curdircall #+call: curdir() #+results: curdircall : /home/andreas/tmp/junk/2013/11 #+begin_src sh :var test=curdircall echo "$test" #+end_src #+results: : nil #+begin_src sh :var test=curdircall() echo "$test" #+end_src #+results: : nil --8<---cut here---end--->8--- Regards, Andreas
Re: [O] Open linked file outside Emacs
Hi, Christof, Il Mercoledì 13 Novembre 2013 11:19, Christof Spitz ha scritto: > how does org-mode 'decide' whether a linked filed (C-c C-l) should be opened > (C-c C-o) inside an Emacs buffer or opened by an external > program? I am using Emacs 24.3 for Windows and org-mode 8.2 reading the /HOME/USER/.mailcap file. please, have a look at the FAQ: http://orgmode.org/worg/org-faq.html#text-external-application-launched-to-open-file-link cheers, Giovanni
Re: [O] refernce to call results
Andreas Leha wrote: > how do I reference the results of a #+call line? > > Here are my unsuccessful attempts: > > * Test call results > > #+name: curdir > #+begin_src sh > echo "$PWD" > #+end_src > > #+results: curdir > : /home/andreas/tmp/junk/2013/11 > > > #+name: curdircall > #+call: curdir() > > #+results: curdircall > : /home/andreas/tmp/junk/2013/11 > > #+begin_src sh :var test=curdircall > echo "$test" > #+end_src > > #+results: > : nil IIUC, #+CALL lines can't be named. See http://orgmode.org/manual/Structure-of-code-blocks.html#Structure-of-code-blocks vs http://orgmode.org/manual/Evaluating-code-blocks.html#Evaluating-code-blocks. Best regards, Seb -- Sebastien Vauban
Re: [O] refernce to call results
Andreas Leha wrote: > how do I reference the results of a #+call line? > > Here are my unsuccessful attempts: > > * Test call results > > #+name: curdir > #+begin_src sh > echo "$PWD" > #+end_src > > #+results: curdir > : /home/andreas/tmp/junk/2013/11 > > [...] > > #+begin_src sh :var test=curdircall() > echo "$test" > #+end_src > > #+results: > : nil Use the following: #+begin_src sh :var test=curdir() echo "$test" #+end_src Best regards, Seb -- Sebastien Vauban
Re: [O] adapted org-flag-drawer to hide newlines of consecutive drawers to save lines
Bastien writes: > Is the cache activated by default? Yes, it is. There's an emergency variable, `org-element-use-cache' to disable it, but it should be used for debugging purpose only. From the user point of view, if the cache appears to be corrupted due to a bug, it may be simpler to call `org-element-cache-reset'. > If so, does it come with some inconveniency? As every cache, you pay the full price the first time you fill it. For example, there may be a small overhead when opening an Org file. Most editing operations only remove the current element from the cache, but some of them (mostly operations on blocks and drawers boundaries) delete larger parts of it. As such, these are more expensive than the average. > If not, should we simply activate it all the time? We really should. Regards, -- Nicolas Goaziou
Re: [O] refernce to call results
"Sebastien Vauban" writes: > Andreas Leha wrote: >> how do I reference the results of a #+call line? >> >> Here are my unsuccessful attempts: >> >> * Test call results >> >> #+name: curdir >> #+begin_src sh >> echo "$PWD" >> #+end_src >> >> #+results: curdir >> : /home/andreas/tmp/junk/2013/11 >> >> >> #+name: curdircall >> #+call: curdir() >> >> #+results: curdircall >> : /home/andreas/tmp/junk/2013/11 >> >> #+begin_src sh :var test=curdircall >> echo "$test" >> #+end_src >> >> #+results: >> : nil > > IIUC, #+CALL lines can't be named. > > See > http://orgmode.org/manual/Structure-of-code-blocks.html#Structure-of-code-blocks > vs > http://orgmode.org/manual/Evaluating-code-blocks.html#Evaluating-code-blocks. > > Best regards, > Seb Hi Sebastian, they can be named now (see http://thread.gmane.org/gmane.emacs.orgmode/73811/focus=74096). Regards, Andreas
Re: [O] adapted org-flag-drawer to hide newlines of consecutive drawers to save lines
Thanks for the details. I think I've seen the cache corrupted several times, I didn't know it was this. Any direction on how to debug such problems? The symptoms were that moving around with M- and friends was completely erratic. -- Bastien
Re: [O] refernce to call results
"Sebastien Vauban" writes: > Andreas Leha wrote: >> how do I reference the results of a #+call line? >> >> Here are my unsuccessful attempts: >> >> * Test call results >> >> #+name: curdir >> #+begin_src sh >> echo "$PWD" >> #+end_src >> >> #+results: curdir >> : /home/andreas/tmp/junk/2013/11 >> >> [...] >> >> #+begin_src sh :var test=curdircall() >> echo "$test" >> #+end_src >> >> #+results: >> : nil > > Use the following: > > #+begin_src sh :var test=curdir() > echo "$test" > #+end_src > > Best regards, > Seb Hi Sebastien, thanks for that. I am aware of the workaround to use a full code block instead. But my question still stands. I found out how to do it. Rather simple and straight forward, blush... For future reference here it is: --8<---cut here---start->8--- #+name: curdir #+begin_src sh echo "$PWD" #+end_src #+results: curdir : /home/andreas/tmp/junk/2013/11 #+name: curdircall #+call: curdir() #+name: myname #+results: curdircall : /home/andreas/tmp/junk/2013/11 #+begin_src sh :var test=myname echo "$test" #+end_src --8<---cut here---end--->8--- Regards, Andreas
Re: [O] Open linked file outside Emacs
Worked! Great, thanks Christof 2013/11/13 Giovanni Ridolfi : > > Hi, Christof, > > Il Mercoledì 13 Novembre 2013 11:19, Christof Spitz > ha scritto: > >> how does org-mode 'decide' whether a linked filed (C-c C-l) should be >> opened (C-c C-o) inside an Emacs buffer or opened by an external >> program? I am using Emacs 24.3 for Windows and org-mode 8.2 > > reading the /HOME/USER/.mailcap file. > > please, have a look at the FAQ: > http://orgmode.org/worg/org-faq.html#text-external-application-launched-to-open-file-link > > cheers, > Giovanni
[O] [PATCH] org-collector: enable specifying a default table-value as a parameter
Hi Bastien, Sorry about the formatting -- that's annoying. I've attached the patch. Here's its description: Currently there isn't an easy way to have default cell values which differ from one propview block to another. This patch enables one to specify what a cell's default value for a block should be. For example, with this patch applied, you can do something like: #+BEGIN: propview :id " mytable" :defaultval "" :cols (PROP1 PROP2) in order to make the default value for this block to be "" instead of 0 in the case that PROP1 or PROP2 isn't contained as a property of a headline. Regards, Mark * contrib/lisp/org-collector.el (org-dblock-write:propview): if a 'defaultval' property has been set, then use this in place of org-propview-default-value. TINYCHANGE --- contrib/lisp/org-collector.el | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/contrib/lisp/org-collector.el b/contrib/lisp/org-collector.el index 60b9069..d62a462 100644 --- a/contrib/lisp/org-collector.el +++ b/contrib/lisp/org-collector.el @@ -121,6 +121,7 @@ preceeding the dblock, then update the contents of the dblock." (scope (plist-get params :scope)) (noquote (plist-get params :noquote)) (colnames (plist-get params :colnames)) + (defaultval (plist-get params :defaultval)) (content-lines (org-split-string (plist-get params :content) "\n")) id table line pos) (save-excursion @@ -133,9 +134,10 @@ preceeding the dblock, then update the contents of the dblock." (t (error "Cannot find entry with :ID: %s" id (unless (eq id 'global) (org-narrow-to-subtree)) (setq stringformat (if noquote "%s" "%S")) - (setq table (org-propview-to-table - (org-propview-collect cols stringformat conds match scope inherit - (if colnames colnames cols)) stringformat)) + (let ((org-propview-default-value (if defaultval defaultval org-propview-default-value))) + (setq table (org-propview-to-table + (org-propview-collect cols stringformat conds match scope inherit + (if colnames colnames cols)) stringformat))) (widen)) (setq pos (point)) (when content-lines
Re: [O] org-tree-to-indirect-buffer: multiple buffers; buffer name containing ID
Bastien writes: > The attached patch does name indirect buffers after the current tree > heading -- thanks for this idea. > > Would anyone else find this useful? I've now applied this patch, thanks Karl! -- Bastien
Re: [O] Using Multiple TODO Keywords
Bastien writes: > You can apply the patch you'll find here: > http://article.gmane.org/gmane.emacs.orgmode/78700 > > Then use C-- 1 C-c C-t to switch to a DONE state even for repeating > events. I'll surely apply the patch on master soon, I'm still waiting > for some feedback. It's now in master, thanks. -- Bastien
Re: [O] [PATCH] org-collector: enable specifying a default table-value as a parameter
Hi Mark, Mark Edgington writes: > Currently there isn't an easy way to have default cell values which > differ from one propview block to another. This patch enables one to > specify what a cell's default value for a block should be. For example, > with this patch applied, you can do something like: > > #+BEGIN: propview :id " mytable" :defaultval "" :cols (PROP1 PROP2) > > in order to make the default value for this block to be "" instead of 0 > in the case that PROP1 or PROP2 isn't contained as a property of a headline. Applied in master, thanks! -- Bastien
Re: [O] org-insert-heading
Hi Bastien, Bastien writes: > Hi Thomas, > > t...@tsdye.com (Thomas S. Dye) writes: > >> With the following Org mode file, there is a dead space where >> org-insert-heading doesn't do anything. In the following example, if the >> point is on either of the empty lines marked [dead space] no heading is >> created. >> >> Is this behavior intended? > > I can't reproduce it... anyone? I looked more closely and found that the behavior I described happens when the folded material ends in a list. If I end the list by adding some regular text, then I get the expected behavior. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] Date-stamps w/o time are shown with time on agenda
Hi! I am heavily using time-stamps. With (setq org-agenda-skip-additional-timestamps-same-entry nil) I see multiple time-stamps of the same heading on my agenda which I do like very much for obvious reasons. However, with a heading such as following I do have a problem: : ** <2013-12-19 Thu 19:00-23:59> X-Mas-Party : : - Email-invitation received: <2013-11-13 Wed> The thing is that on my agenda of <2013-11-13 Wed>, I do see the event as it is a normally scheduled event including a time-slot of 19:00-23:59. What I expect: on <2013-11-13 Wed> I would like to see it as an item without any association of any time-stamp/slot like a whole-day event. Is this (1) a matter of my configuration or (2) on purpose (why?) or (3) so far a wish of mine? :-) Thanks! PS: I am using Org-mode version from git from the day before yesterday or so. -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https://github.com/novoid/Memacs < https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
[O] org-reveal reaveal.js toc:nil option
Hello list, I'm making a presentation in reveal.js with the help of org-mode and org-reveal and was hoping I could get some help. I'm trying to remove the table of contents from my slides but the toc option does not seem to have any effect. A bare bone presentation on github can be seen in this repository: Xparx/midtimeseminar/blob/master/presentaion.txt Any help appreciated. regards A
Re: [O] refernce to call results
Hi Andreas, Andreas Leha wrote: > "Sebastien Vauban" writes: >> Andreas Leha wrote: >>> how do I reference the results of a #+call line? >>> >>> Here are my unsuccessful attempts: >>> >>> * Test call results >>> >>> #+name: curdir >>> #+begin_src sh >>> echo "$PWD" >>> #+end_src >>> >>> #+results: curdir >>> : /home/andreas/tmp/junk/2013/11 >> >> Use the following: >> >> #+begin_src sh :var test=curdir() >> echo "$test" >> #+end_src > > thanks for that. I am aware of the workaround to use a full code block > instead. But my question still stands. I don't understand what you mean: it's not a workaround, as you have to define your block once. Then, you simply use its name, instead of naming a call line, and using that name. You avoid one indirection, no? > I found out how to do it. Rather simple and straight forward, blush... > > For future reference here it is: > #+name: curdir > #+begin_src sh > echo "$PWD" > #+end_src > > #+results: curdir > : /home/andreas/tmp/junk/2013/11 > > #+name: curdircall > #+call: curdir() > > #+name: myname > #+results: curdircall > : /home/andreas/tmp/junk/2013/11 > > #+begin_src sh :var test=myname > echo "$test" > #+end_src I don't know if that's the solution, or simply a feature which works for now. I find this weird and unsound: - For code blocks, the results' name (curdir) is the code block's name (curdir). - For call lines, as you do above, you give another name to the results of a call line (myname) than the name of the call line itself (curdircall). This is not appealing to me, and confusing at least. Best regards, Seb -- Sebastien Vauban
Re: [O] Date-stamps w/o time are shown with time on agenda
Hi Karl, Karl Voit writes: > : ** <2013-12-19 Thu 19:00-23:59> X-Mas-Party > : > : - Email-invitation received: <2013-11-13 Wed> You need to use inactive timestamps in such cases. >From memory, we wanted to preserve the possibility to have multiple active timestamps in a subtree. HTH, -- Bastien
[O] [feature request] refernce to call results
Hi Sebastien, "Sebastien Vauban" writes: > Hi Andreas, > > Andreas Leha wrote: >> "Sebastien Vauban" writes: >>> Andreas Leha wrote: how do I reference the results of a #+call line? Here are my unsuccessful attempts: * Test call results #+name: curdir #+begin_src sh echo "$PWD" #+end_src #+results: curdir : /home/andreas/tmp/junk/2013/11 >>> >>> Use the following: >>> >>> #+begin_src sh :var test=curdir() >>> echo "$test" >>> #+end_src >> >> thanks for that. I am aware of the workaround to use a full code block >> instead. But my question still stands. > > I don't understand what you mean: it's not a workaround, as you have to define > your block once. Then, you simply use its name, instead of naming a call line, > and using that name. You avoid one indirection, no? > Sorry about the lame example. Let's assume, the original code block takes an argument. I want to 'get rid of' that argument, let's say to avoid typing. So, I have to name the result of calling that code block with a specific argument. There has to be at least one level of indirection here? IIUC, you propose to use a code block to provide that argument, and my idea was to use a #+call line. For me, a call line is the more natural way to accomplish this. >> I found out how to do it. Rather simple and straight forward, blush... >> >> For future reference here it is: >> #+name: curdir >> #+begin_src sh >> echo "$PWD" >> #+end_src >> >> #+results: curdir >> : /home/andreas/tmp/junk/2013/11 >> >> #+name: curdircall >> #+call: curdir() >> >> #+name: myname >> #+results: curdircall >> : /home/andreas/tmp/junk/2013/11 >> >> #+begin_src sh :var test=myname >> echo "$test" >> #+end_src > > I don't know if that's the solution, or simply a feature which works for now. > > I find this weird and unsound: > > - For code blocks, the results' name (curdir) is the code block's name > (curdir). > > - For call lines, as you do above, you give another name to the results of a > call line (myname) than the name of the call line itself (curdircall). > > This is not appealing to me, and confusing at least. I agree completely. So my question boils down to this feature request: Now, that #+call lines can be named, would it be possible to reference the results the same way as for code blocks? Regards, Andreas
Re: [O] Date-stamps w/o time are shown with time on agenda
* Bastien wrote: > Hi Karl, Hi Bastien! > Karl Voit writes: > >> : ** <2013-12-19 Thu 19:00-23:59> X-Mas-Party >> : >> : - Email-invitation received: <2013-11-13 Wed> > > You need to use inactive timestamps in such cases. This is my work-around so far :-) > From memory, we wanted to preserve the possibility > to have multiple active timestamps in a subtree. I am sorry - I do not see the contradiction here. Why not handle each time-stamp in a consistent manner: show each as whole-day items on the agenda and as items with an associated time (and duration)? -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https://github.com/novoid/Memacs < https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] org-tree-to-indirect-buffer: multiple buffers; buffer name containing ID
* Bastien wrote: > Bastien writes: > >> The attached patch does name indirect buffers after the current tree >> heading -- thanks for this idea. >> >> Would anyone else find this useful? > > I've now applied this patch, thanks Karl! Thank *you* for implementing this! It helps keeping overview in my list of open buffers! -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https://github.com/novoid/Memacs < https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] org-insert-heading
Hi Thomas, t...@tsdye.com (Thomas S. Dye) writes: > I looked more closely and found that the behavior I described happens > when the folded material ends in a list. If I end the list by adding > some regular text, then I get the expected behavior. Confirmed -- I quickly looked, it seems that `org-in-item-p' should do a better job when preceeded by invisible text. -- Bastien
Re: [O] org-reveal reaveal.js toc:nil option
Andreas writes: > Hello list, > > I'm making a presentation in reveal.js with the help of org-mode and > org-reveal and was hoping I could get some help. > > I'm trying to remove the table of contents from my slides but the toc option > does not seem to have any effect. > > A bare bone presentation on github can be seen in this repository: > Xparx/midtimeseminar/blob/master/presentaion.txt > > Any help appreciated. > #+OPTIONS: toc:nil seems to work for me. Nick
Re: [O] Date-stamps w/o time are shown with time on agenda
Hi Karl, Karl Voit writes: > I am sorry - I do not see the contradiction here. Sorry, I read too fast. > Why not handle each time-stamp in a consistent manner: show each > as whole-day items on the agenda and ddd HH:MM> as items with an associated time (and duration)? (setq org-agenda-search-headline-for-time nil) should do. When Org tries to associate a headline with a timestamp found in a subtree, it optionally tries to find a time string (like "HH:MM") in the headline if this option is `t' (the default.) Here it confuses the time string from the timestamp with a separate time string, hence the confusion. -- Bastien
Re: [O] Date-stamps w/o time are shown with time on agenda
* Bastien wrote: > Hi Karl, > > Karl Voit writes: > >> I am sorry - I do not see the contradiction here. > > Sorry, I read too fast. :-) >> Why not handle each time-stamp in a consistent manner: show each >> as whole-day items on the agenda and > ddd HH:MM> as items with an associated time (and duration)? > > (setq org-agenda-search-headline-for-time nil) should do. > > When Org tries to associate a headline with a timestamp found in a > subtree, it optionally tries to find a time string (like "HH:MM") > in the headline if this option is `t' (the default.) Perfect! With the line above, my issue is gone and with your description my knowledge is widened :-) -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https://github.com/novoid/Memacs < https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] Help on spreadsheet/calc references and improvements
Hi Carsten On Wed, Oct 30, 2013 at 6:59 PM, Michael Brand wrote: > On Fri, Oct 25, 2013 at 3:31 PM, Carsten Dominik > wrote: >> On 24.10.2013, at 22:47, Michael Brand wrote: >>> On Thu, Oct 24, 2013 at 8:18 AM, Carsten Dominik >>> wrote: Michael, would you like to have write access to the git repo? >>> >>> Thank you for the trust. As I would like anyway to have a review of my >>> patches before commit, I think it would not help when I would do the >>> commit myself. I hope that it is still ok when I prefer a review, >>> independent of the simplicity of the patch. >> >> Yes, reviews are always good! But with write access you can still >> install a patch yourself after a review, or make small doc fixes >> without review etc. > > Ok, I see that it would help when I "git push" those of my simple > changes that maybe don't need a review by a maintainer at any price to > the master branch myself. I already have write access to Worg, do you > still need my public key? The last paragraph has not been answered yet. Can I ask Jason Dunsmore directly to give me write access to Org? Michael
Re: [O] Help on spreadsheet/calc references and improvements
Hi Michael, Michael Brand writes: > The last paragraph has not been answered yet. Can I ask Jason Dunsmore > directly to give me write access to Org? Please send me your public key and I'll give you write access. Thanks! -- Bastien
Re: [O] C-c ' and mail sources
Hello François, 2013ko azaroak 13an, François Pinard-ek idatzi zuen: [...] > I do not know what would be the reasonable way to correct it: preventing > the shifting, or changing how highlighting interpret beginning of lines, > in case of Org? I have the following in my emacs init file to prevent the shifting of python code blocks: #+BEGIN_SRC emacs-lisp (defadvice org-edit-src-exit (around awe-org activate) (let ((org-edit-src-content-indentation org-edit-src-content-indentation)) (when (eq major-mode 'python-mode) (setq org-edit-src-content-indentation 0)) ad-do-it)) #+END_SRC You should be able to adapt this for mail mode by changing the (eg 'major-mode ...) test. Alternatively, if you never want any source blocks to be indented from the left margin, you can customize the org-edit-src-content-indentation variable to 0. -- Aaron Ecay
Re: [O] A weird warning and a test (eager macro expansion) error
Bastien writes: > I suggest you handle this the way you prefer: either by committing > this in Org before asking emacs-devel@, or by asking first then see > of this needs to be fixed upstream? I won't have time to digg this > issue further, sorry. I'll just keep the patch locally for the moment, at least until I've looked at Ert and/or made a test case that can be reoprted to emacs-bugs. If anybody wants to test on Emacs trunk, it is easy enough to apply the patch, I think. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] [BUG][PATCH] Marker points into wrong buffer
Bastien writes: > Feel free to install it, thanks! Applied to master. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] Lisp code blocks fail
Hi Tom,
Could you provide a minimal example? I'm unable to debug from the stack
trace alone.
Thanks,
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha all,
>
> With a recent pull, Lisp code blocks that I'm fairly certain were
> working previously started to fail. There is a backtrace below. The Lisp
> code executes correctly, but Babel doesn't appear to get the results in
> the form it expects (if I'm reading the backtrace correctly).
>
> Have I mucked up somehow?
>
> Debugger entered--Lisp error: (wrong-type-argument listp "((\"t2\" \"b\"))")
> byte-code("\211A@)\207" [result x] 2)
> org-babel-execute:lisp("(unless (boundp '*cycle-graph*)\n (defvar
> *cycle-graph*))\n(setq *cycle-graph* (populate (make-instance
> digraph)))\n(let ((r)\n (flag))\n (dolist (e edges r)\n (add-edge
> *cycle-graph*\n (list (read-from-string (first e))\n (read-from-string
> (second e\n (when (and (not flag) (setf flag (cycles
> *cycle-graph*))) (push e r" ((:comments . "") (:shebang . "")
> (:cache . "no") (:padline . "") (:noweb . "yes") (:tangle . "no")
> (:exports . "code") (:results . "silent") (:var edges ("t1" "a") ("a"
> "t2") ("b" "t1") ("t2" "b")) (:colnames . "yes") (:hlines . "no")
> (:session . "none") (:result-type . value) (:result-params "silent")
> (:rowname-names) (:colname-names (edges "older" "younger"
> org-babel-execute-src-block(nil)
> org-babel-execute-src-block-maybe()
> org-babel-execute-maybe()
> org-babel-execute-safely-maybe()
> run-hook-with-args-until-success(org-babel-execute-safely-maybe)
> org-ctrl-c-ctrl-c(nil)
> ad-Orig-call-interactively(org-ctrl-c-ctrl-c nil nil)
> (with-no-warnings (ad-Orig-call-interactively function record-flag keys))
> (setq ad-return-value (with-no-warnings (ad-Orig-call-interactively
> function record-flag keys)))
> (let ((ido-ubiquitous-next-override
> (ido-ubiquitous-get-command-override function))) (setq ad-return-value
> (with-no-warnings (ad-Orig-call-interactively function record-flag
> keys
> (ido-ubiquitous-with-override (ido-ubiquitous-get-command-override
> function) (setq ad-return-value (with-no-warnings
> (ad-Orig-call-interactively function record-flag keys
> (let (ad-return-value) (ido-ubiquitous-with-override
> (ido-ubiquitous-get-command-override function) (setq ad-return-value
> (with-no-warnings (ad-Orig-call-interactively function record-flag
> keys ad-return-value)
> call-interactively(org-ctrl-c-ctrl-c nil nil)
>
> All the best,
> Tom
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
Re: [O] Babel: the disappearing hline
Jarmo Hurri writes: > Rick Frankel writes: > > Greetings again. > >> Again, the solution is to globally set the :hline property to =yes= >> instead of the default =no=, and you will get the results you want. > > The issue I am trying to raise here is the consistency of the system, > not the way to solve this particular problem. Personally I think it > would be clearer if the handling of hlines in _output_ were consistent > _by default_, regardless of whether the call is made by direct > evaluation of a block; by a post(); or by a #+CALL. I found it very > weird when I bumped into this discrepancy - in a much more complicated > context than the examples I have shown here. > > But it is your system and you know what kind of qualities you want it to > have. I am just learning the ropes and sending you a message from the > trenches. > > All the best, > > Jarmo > I understand that this particular use case is confusing, however there are competing use cases and the case described here is not the most common. Take for example the following. #+name: data | header | || | one| | two| || | three | #+BEGIN_SRC sh :var in=data echo "$in" #+END_SRC #+RESULTS: | header | | one| | two| | three | In fact, hlines are *not* preserved by default with regular code blocks. And in practice only emacs-lisp code blocks tend to create hlines themselves. In general babel does a good deal of hline and colnames processing. #+name: with-a-header | numbers | |-| | one | | two | | three | | four| Strips both the header *and* the top hline by default. #+begin_src emacs-lisp :var in=with-a-header (mapcar (lambda (row) (mapcar #'length row)) in) #+end_src #+RESULTS: | 3 | | 3 | | 5 | | 4 | Applies the code block only to the body of the input table. #+begin_src emacs-lisp :var in=with-a-header :colnames yes (mapcar (lambda (row) (mapcar #'length row)) in) #+end_src #+RESULTS: | numbers | |-| | 3 | | 3 | | 5 | | 4 | Perhaps we should change `org-babel-default-inline-header-args' to include `(:hlines "yes")'. If there is no push back on that change I'd be happy to make it. Regards, -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] [feature request] refernce to call results
>
> I agree completely. So my question boils down to this feature request:
>
> Now, that #+call lines can be named, would it be possible to reference
> the results the same way as for code blocks?
>
I just pushed up a commit which should make this possible. E.g.,
* call by name
#+name: echo-input
#+begin_src sh :var input="original"
echo "input=$input"
#+end_src
#+RESULTS: echo-input
: input=original
#+name: echo-new
#+call: echo-input("new")
#+RESULTS: echo-new
: input=new
#+begin_src sh :var input=echo-new()
echo "this=$input"
#+end_src
#+RESULTS:
: this=input=new
Best,
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
Re: [O] Babel: the disappearing hline
On 2013-11-13 09:17, Eric Schulte wrote: Perhaps we should change `org-babel-default-inline-header-args' to include `(:hlines "yes")'. If there is no push back on that change I'd be happy to make it. I agree. It would probably make the behavior less confusing. rick
[O] [BUG] call results not creating #results
Eric- Since you're looking at call lines :)... there is a (fairly new i think) bug: When searching forward for results, following call lines are not being respected as stop points. For instance, given: #+BEGIN_SRC org ,* Call block test ,#+name: call-me ,#+BEGIN_SRC emacs-lisp :var v="one" v ,#+END_SRC ,#+RESULTS: call-me : one ,#+call: call-me(v="two") ,#+RESULTS: : two #+END_SRC If i insert a new call-block before "two" and execute it, the following occurs #+BEGIN_SRC org ,* Call block test ,#+name: call-me ,#+BEGIN_SRC emacs-lisp :var v="one" v ,#+END_SRC ,#+RESULTS: call-me : one ,#+call: call-me(v="three") ,#+call: call-me(v="two") ,#+RESULTS: : three #+END_SRC as you can see, it replaced the results for call-line two. Note that if i had named "two" and executed it before adding in call line "three", the results would be ok: #+BEGIN_SRC org ,* Call block test ,#+name: call-me ,#+BEGIN_SRC emacs-lisp :var v="one" v ,#+END_SRC ,#+RESULTS: call-me : one ,#+call: call-me(v="three") ,#+RESULTS: : three ,#+name: two ,#+call: call-me(v="two") ,#+RESULTS: two : two #+END_SRC rick
Re: [O] [bug] org-refile makes ido think that some candidates are directories
i have not been able to track this down further. has anybody taken a look at it? On 8/27/13, Samuel Wales wrote: > org-refile makes ido think that every entry that is in the > current buffer is a directory, while every entry that is > in another buffer is a file. > > === > > You can confirm by loading ido and doing this: > > (setq org-refile-use-outline-path t) > (setq org-outline-path-complete-in-steps nil) > (setq org-completion-use-ido t) > > Now do org-refile and look at the candidate list. Please > note the addition of the filename at the end of the entries > that are not in the current buffer, and probably a different > font. You can use the ido keys for navigating directories, > and they will only go to the entries in the current buffer. > > === > > The relevant part of org.el seems to be this, but I do not > understand it: > > (setq answ (funcall cfunc prompt tbl nil (not new-nodes) > nil 'org-refile-history (or cdef (car > org-refile-history > > This is FAR beyond my ability to debug, but I suspect > that the artificial distinction between the current buffer > and other buffers, treating one as a directory and the other > as a file, might be related to several long-standing, subtle > but extremely annoying bugs involving the default and > history. But I could be wrong about that. > > For example, if you previously refiled, there is always an > extra entry that has no marker and errors if you select it, > and it is often the default candidate :(. And it is > impossible to narrow to a subtree of the default subtree :(. > I have previously reported at least one of these bugs. > > === > > In any case, IMO, ido should treat all olpaths as if they > were files. Can anybody help track this down? > > Thanks. > > Samuel > > -- > The Kafka Pandemic: http://thekafkapandemic.blogspot.com > > The disease DOES progress. MANY people have died from it. ANYBODY can get > it. > > Denmark: free Karina Hansen NOW. > -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
[O] bug: "Please save the buffer to a file before refiling" when the buffer is already saved"
* computer ** emacs *** myorg I use ido. === i refile to "myorg" with the string "myorg" as an ido selector i save all files i refile to "emacs" i take a look before pressing ret ido shows me the wrong olpath it shows me myorg with the filename in parentheses after i wanted emacs the next candidates are emacs myorg without the filename i press ret, as if i wanted myorg anyway instead of emacs false error says Please save the buffer to a file before refiling === Note that myorg appears *twice* in the candidate list: (1) incorrect default with a filename appended that causes the bug, and (2) correct candidate without filename appended that is incorrectly not also the default. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] Help on spreadsheet/calc references and improvements
Hi Bastien On Wed, Nov 13, 2013 at 6:34 PM, Bastien wrote: > Please send me your public key and I'll give you write access. It works, thank you. I have pushed my patch myself now. When and how often is http://orgmode.org/manual/References.html updated? Michael
[O] Bug: HTML export problem [8.2.3b]
Dear org-mode team.
Hi
org-mode is gread major mode in my emacs life.
But, If this org-file is export to HTML, an indent will collapse.
I wish keep indents...
Best regards.
test.org
* Sample A
#+BEGIN_SRC C++
#include "Eigen/Core"
// Good layout.
// The indent is maintained.
int main() {
Eigen::Matrix3i m;
m << 1, 2, 3,
4, 5, 6,
7, 8, 9;
}
#+END_SRC
* Sample B
#+BEGIN_SRC C++
#include "Eigen/Core"
// Bad layout.
// The indent has collapsed.
int main() {
Eigen::Matrix3i m1;
m1 << 1, 2, 3,
4, 5, 6,
7, 8, 9;
}
#+END_SRC
こんにちは。
私にとって、org-modeはemacsの中でもっとも素晴らしいmajor modeです。
ところが、１つ問題があります。
このorgファイルをhtmlファイルにエクスポートすると、
ソースコードのレイアウトが崩れてしまう場合があります。
何が問題なのでしょうか??
お手数をおかけしますが、宜しくお願いします。
Emacs : GNU Emacs 24.3.1 (x86_64-apple-darwin13.0.0, Carbon Version 1.6.0
AppKit 1265)
of 2013-11-09 on Nishiyama-no-MacBook-Air.local
Package: Org-mode version 8.2.3b (8.2.3b-dist @ /Users/nishi/.emacs.d/lisp/)
current state:
==
(setq
org-hide-leading-stars t
org-agenda-log-mode-items '(closed clock state)
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-skip-timestamp-if-done t
org-occur-hook '(org-first-headline-recenter)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-log-done 'time
org-confirm-shell-link-function 'yes-or-no-p
org-read-date-popup-calendar nil
org-agenda-restore-windows-after-quit t
org-special-ctrl-a/e t
org-todo-keyword-faces '(("WAIT" :foreground "#FF" :weight bold) ("ABORT"
:foreground "#E000FF" :weight bold))
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-tags-column -115
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-mode-hook '(#[nil "\300\301\302\303\304$\207" [org-add-hook
change-major-mode-hook org-show-block-all append local] 5]
#[nil
"\300\301\302\303\304$\207" [org-add-hook change-major-mode-hook
org-babel-show-result-all append local] 5]
org-babel-result-hide-spec org-babel-hide-all-hashes org-mode-hooks)
org-stuck-projects '("+PROJECT&+LEVEL=2/-DONE" ("TODO" "NEXT" "NEXTACTION"
"WAIT" "ABORT") nil "")
org-agenda-time-grid '((daily today require-timed) #("" 0 16
(org-heading t)) (800 1000 1200 1400 1600 1800 2000 2200))
org-yank-adjusted-subtrees t
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-hide-inline-tasks org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-agenda-tags-column -130
org-archive-location "::* Archived Tasks"
org-agenda-after-show-hook '(my-org-agenda-after-show-hooks)
org-todo-keywords '((sequence "TODO" "WAIT" "|" "DONE" "ABORT"))
org-agenda-window-setup 'current-window
org-confirm-elisp-link-function 'yes-or-no-p
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-odd-levels-only t
org-insert-heading-respect-content t
org-agenda-mode-hook '(org-agenda-mode-hooks)
org-agenda-files '("~/to-do.org")
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
)
--
Nishiyama Nobuyuki
Mail: nishiy...@target-ent.com
Re: [O] Date-stamps w/o time are shown with time on agenda
nil might be a safer default? On 11/13/13, Karl Voit wrote: >> (setq org-agenda-search-headline-for-time nil) should do. -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] [feature request] refernce to call results
Hi Eric,
Eric Schulte writes:
>>
>> I agree completely. So my question boils down to this feature request:
>>
>> Now, that #+call lines can be named, would it be possible to reference
>> the results the same way as for code blocks?
>>
>
> I just pushed up a commit which should make this possible. E.g.,
>
> * call by name
>
> #+name: echo-input
> #+begin_src sh :var input="original"
> echo "input=$input"
> #+end_src
>
> #+RESULTS: echo-input
> : input=original
> #+name: echo-new
> #+call: echo-input("new")
> #+RESULTS: echo-new
> : input=new
> #+begin_src sh :var input=echo-new()
> echo "this=$input"
> #+end_src
>
> #+RESULTS:
> : this=input=new
>
thanks a lot! I confirm that it works. This was really fast!
Regards,
Andreas
[O] org-contacts, multi-line properties, postal addresses
Hello world, I'm just taking another look at org-contacts. I wonder what the best practice is for dealing with multi-line properties like postal addresses. I can just make them part of the entry, of course, not in a property, but that seems oddly different from the other properites. Have I overlooked something obvious? Be seeing you, norm -- Norman Walsh | A man may fulfill the object of his http://nwalsh.com/| existence by asking a question he | cannot answer, and attempting a task he | cannot achieve.--Oliver Wendell Holmes signature.asc Description: PGP signature
[O] bug#15887: Possibly incorrect custom :types
Package: org-mode cus-test.el suggests the following variables may have incorrect custom :types. (There may be some false positives.) This refers to Org mode in current Emacs trunk. Eg, org-texinfo-filename does not have "nil" as an option. org-agenda-deadline-leaders org-agenda-search-view-max-outline-level org-ascii-format-drawer-function org-ascii-format-inlinetask-function org-babel-latex-htlatex org-babel-latex-htlatex-packages org-babel-lob-files org-babel-python-None-to org-babel-python-mode org-babel-ruby-nil-to org-export-async-init-file org-export-with-creator org-html-format-drawer-function org-html-format-headline-function org-html-format-inlinetask-function org-html-with-latex org-latex-format-drawer-function org-latex-format-inlinetask-function org-log-note-headings org-mouse-1-follows-link org-odt-format-drawer-function org-odt-format-headline-function org-odt-format-inlinetask-function org-odt-with-latex org-plantuml-jar-path org-texinfo-filename org-texinfo-format-drawer-function org-texinfo-format-headline-function org-texinfo-format-inlinetask-function orgstruct-heading-prefix-regexp
[O] OpenDocument export
Hi all, since my update just a few minutes ago, I have problems exporting one of my documents to odt. The new behaviour is, that I get asked , | Buffer foo.org<2><2> modified; kill anyway? (yes or no) ` Regardless of my answer after that, a new (empty) buffer is opened, which has the name , | OpenDocument export failed: Lisp nesting exceeds `max-lisp-eval-depth' ` (This shows also up in the *Messages* buffer) I am not able to reproduce this with a simpler document and until now I have not been able to detect the responsible part of the offending document. So, I ask here already -- knowing that I provide very little details -- in case somebody can already point me to where to search next. Any ideas? Regards, Andreas
[O] Smart quotes not working with some languages?
Hi! I am using the latest org from git and I can't get org to export (I need LaTeX export particularly) files with smart quotes. The following example silently fails to produce smart quotes: #+OPTIONS: ':t #+LANGUAGE: ru This is a 'test' "file". * Headline with 'quotes' ** Subheading with "quotes". This is "some" 'text'. Using 'fr' yields different quotes, for example. Is there a way to use standard "english" smart quotes with different language? Right now my example is producing bad LaTeX. -- Sincerely yours, -- Daniil Frumin
Re: [O] OpenDocument export
Andreas Leha writes: > Hi all, > > since my update just a few minutes ago, I have problems exporting one of > my documents to odt. > > The new behaviour is, that I get asked > , > | Buffer foo.org<2><2> modified; kill anyway? (yes or no) > ` > > Regardless of my answer after that, a new (empty) buffer is opened, > which has the name > , > | OpenDocument export failed: Lisp nesting exceeds `max-lisp-eval-depth' > ` > (This shows also up in the *Messages* buffer) > > I am not able to reproduce this with a simpler document and until now I > have not been able to detect the responsible part of the offending > document. > > So, I ask here already -- knowing that I provide very little details -- > in case somebody can already point me to where to search next. > > Any ideas? The second problem is gone now. Do not ask me, what made it go away. I have no clue (no emacs restart, document stayed the same). But the first problem (the question on the modified buffer) still persists. Best, Andreas
Re: [O] Lisp code blocks fail
Hi Eric,
#+begin_src lisp
(+ 1 1)
#+end_src
Debugger entered--Lisp error: (wrong-type-argument listp "2")
byte-code("\211A@)\207" [result x] 2)
org-babel-execute:lisp("(+ 1 1)" ((:comments . "") (:shebang . "") (:cache .
"no") (:padline . "") (:noweb . "yes") (:tangle . "no") (:exports . "code")
(:results . "replace") (:session . "none") (:hlines . "no") (:result-type .
value) (:result-params "replace") (:rowname-names) (:colname-names)))
org-babel-execute-src-block(nil)
org-babel-execute-src-block-maybe()
org-babel-execute-maybe()
org-babel-execute-safely-maybe()
run-hook-with-args-until-success(org-babel-execute-safely-maybe)
org-ctrl-c-ctrl-c(nil)
ad-Orig-call-interactively(org-ctrl-c-ctrl-c nil nil)
(with-no-warnings (ad-Orig-call-interactively function record-flag keys))
(setq ad-return-value (with-no-warnings (ad-Orig-call-interactively function
record-flag keys)))
(let ((ido-ubiquitous-next-override (ido-ubiquitous-get-command-override
function))) (setq ad-return-value (with-no-warnings (ad-Orig-call-interactively
function record-flag keys
(ido-ubiquitous-with-override (ido-ubiquitous-get-command-override function)
(setq ad-return-value (with-no-warnings (ad-Orig-call-interactively function
record-flag keys
(let (ad-return-value) (ido-ubiquitous-with-override
(ido-ubiquitous-get-command-override function) (setq ad-return-value
(with-no-warnings (ad-Orig-call-interactively function record-flag keys
ad-return-value)
call-interactively(org-ctrl-c-ctrl-c nil nil)
Org-mode version 8.2.3b (release_8.2.3b-200-gb6522a @
/Users/dk/.emacs.d/src/org-mode/lisp/)
All the best,
Tom
Eric Schulte writes:
> Hi Tom,
>
> Could you provide a minimal example? I'm unable to debug from the stack
> trace alone.
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] org-reveal reaveal.js toc:nil option
I did some brute force bug tracking and manage to track down the problem. I made two different files: test1.org: #+TITLE: Test 1 #+OPTIONS: toc:nil #+INFOJS_OPT: * Header 1 * Header 2 ** Subheader 2.1 test2.org: #+TITLE: Test 1 #+OPTIONS: toc:nil * Header 1 * Header 2 ** Subheader 2.1 In the first example i have the header with #+INFOJS_OPT: empty, the other file lacks this line. The first file generates a toc while the other doesn't. I manage to track down the variable org-html-infojs-opts-table which has the Value: ((path PATH "http://orgmode.org/org-info.js";) (view VIEW "info") (toc TOC :with-toc) (ftoc FIXED_TOC "0") (tdepth TOC_DEPTH "max") (sdepth SECTION_DEPTH "max") (mouse MOUSE_HINT "underline") (buttons VIEW_BUTTONS "0") (ltoc LOCAL_TOC "1") (up LINK_UP :html-link-up) (home LINK_HOME :html-link-home)) It seems to me as a novice that the :with-toc is defined here and forces a table of contents to be displayed. Not sure if this is correct but at least it solved my problem. The toc option is not inserted in the reveal export template and now after testing it it looks like #+INFOJS_OPT: toc:nil also could have been used. The tutorial I looked at did not do it this way so I over looked it. regards A
Re: [O] Smart quotes not working with some languages?
Hi Daniil, Daniil Frumin writes: > Hi! I am using the latest org from git and I can't get org to export (I > need LaTeX export particularly) files with smart quotes. You need to add it to the variable org-export-smart-quotes-alist defined in ox.el. Put your cursor on the variable and do C-h v to read about it. Once you have added support for Russian, please make a patch and submit it here so that other people can benefit from your labor. Thanks, Rasmus -- Dung makes an excellent fertilizer
Re: [O] Help on spreadsheet/calc references and improvements
Hi Michael, Michael Brand writes: > On Wed, Nov 13, 2013 at 6:34 PM, Bastien wrote: >> Please send me your public key and I'll give you write access. > > It works, thank you. I have pushed my patch myself now. Thanks. > When and how often is > http://orgmode.org/manual/References.html > updated? It's updated when a new minor or major release is done. -- Bastien
Re: [O] Date-stamps w/o time are shown with time on agenda
Samuel Wales writes: > nil might be a safer default? This small feature would not be easily discovered if this option is turned to nil, so I'd say `t' makes sense here. But I don't feel strongly about this. -- Bastien
Re: [O] Bug: HTML export problem [8.2.3b]
Nishiyama Nobuyuki writes:
> Dear org-mode team.
>
> Hi
>
> org-mode is gread major mode in my emacs life.
>
> But, If this org-file is export to HTML, an indent will collapse.
>
> I wish keep indents...
>
I cannot reproduce it: the two code blocks render identically in my
test. What does the resulting HTML file look like?
Nick
Org-mode version 8.2.3a (release_8.2.3a-195-ge4984e @
/home/nick/elisp/org-mode/lisp/)
> Best regards.
>
>
> test.org
>
> * Sample A
>
> #+BEGIN_SRC C++
>
> #include "Eigen/Core"
>
> // Good layout.
> // The indent is maintained.
> int main() {
> Eigen::Matrix3i m;
> m << 1, 2, 3,
>4, 5, 6,
>7, 8, 9;
> }
>
> #+END_SRC
>
> * Sample B
>
> #+BEGIN_SRC C++
>
> #include "Eigen/Core"
>
> // Bad layout.
> // The indent has collapsed.
> int main() {
> Eigen::Matrix3i m1;
> m1 << 1, 2, 3,
> 4, 5, 6,
> 7, 8, 9;
> }
>
> #+END_SRC
>
Re: [O] bug: "Please save the buffer to a file before refiling" when the buffer is already saved"
Hi Samuel, Samuel Wales writes: > I use ido. I don't use ido so it's hard for me to mentally picture the problem correctly. Anyway, the error message was wrong in many circumstances, e.g. when the user tries to refile and only mention the headline/, not the target file. I've enhance the error message in these cases (in master.) -- Bastien
Re: [O] bug: "Please save the buffer to a file before refiling" when the buffer is already saved"
Thank you. Please note that the fact that it errors instead of refiling is a bug, even if the error message is more accurate. On 11/13/13, Bastien wrote: > Hi Samuel, > > Samuel Wales writes: > >> I use ido. > > I don't use ido so it's hard for me to mentally picture the problem > correctly. > > Anyway, the error message was wrong in many circumstances, e.g. when > the user tries to refile and only mention the headline/, not the > target file. I've enhance the error message in these cases (in > master.) > > -- > Bastien > -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] bug: "Please save the buffer to a file before refiling" when the buffer is already saved"
Samuel Wales writes: > Please note that the fact that it errors instead of refiling is a bug, > even if the error message is more accurate. In the cases I have in mind (which are probably not the same than yours), the target file is unspecified and refiling cannot happen because it needs to know the target file... so this is not a bug for me -- hopefully someone who does not use ido can hit the bug too and report it. -- Bastien
Re: [O] bug: "Please save the buffer to a file before refiling" when the buffer is already saved"
I suspect it is the arguments used for ido. I previously reported that Org incorrectly treats the current file differently from other files. This causes ido to think that some olpaths are files and others are directories. This might be related. On 11/13/13, Bastien wrote: > In the cases I have in mind (which are probably not the same than > yours), the target file is unspecified and refiling cannot happen > because it needs to know the target file... so this is not a bug > for me -- hopefully someone who does not use ido can hit the bug > too and report it. > > -- > Bastien > -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
[O] bug: wrong type argument exporting
This also actually corrupts the buffer by inserting footnotes at the end. Sometimes it leaves it in a narrowed state. Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil) goto-char(nil) (progn (goto-char link-end) (skip-chars-forward " ")) (setq post-blank (progn (goto-char link-end) (skip-chars-forward " ")) end (point)) (let ((begin ...) end contents-begin contents-end link-end post-blank path type raw-link link search-option application) (cond (... ...) (... ... ...) (... ...) (... ...)) (setq post-blank (progn ... ...) end (point)) (when (member type org-element-link-type-is-file) (cond ... ...) (when ... ...) (setq type "file")) (list (quote link) (list :type type :path path :raw-link ... :application application :search-option search-option :begin begin :end end :contents-begin contents-begin :contents-end contents-end :post-blank post-blank))) (save-excursion (let (... end contents-begin contents-end link-end post-blank path type raw-link link search-option application) (cond ... ... ... ...) (setq post-blank ... end ...) (when ... ... ... ...) (list ... ...))) org-element-link-parser() funcall(org-element-link-parser) (setq next (funcall (intern ...))) (if (or (not closest) (> ... origin)) (catch (quote found) (dolist ... ...)) (goto-char (cdr closest)) (setq next (funcall ...)) (when org-element-use-cache (push next ...) (or update-cache-flag ...))) (let ((closest ...)) (if (or ... ...) (catch ... ...) (goto-char ...) (setq next ...) (when org-element-use-cache ... ...))) (while t (when (and ... org-element-use-cache) (let ... ...)) (when (or next ...) (setq candidates ...) (when org-element-use-cache ... ...)) (let (...) (if ... ... ... ... ...)) (let (... ... ...) (cond ... ... ...))) (catch (quote exit) (while t (when ... ...) (when ... ... ...) (let ... ...) (let ... ...))) (prog1 (catch (quote exit) (while t ... ... ... ...)) (when (and update-cache-flag ...) (org-element-cache-put cache-key ...))) (let* ((restriction ...) (parent element) (candidates ...) (cache-key ...) (cache ...) objects-data next update-cache-flag) (prog1 (catch ... ...) (when ... ...))) (let* ((origin ...) (element ...) (type ...)) (cond (... ... ... ... ...) (... ...) (... ... ... ...) (... ...) (... ...) (t ...)) (goto-char (point-min)) (let* (... ... ... ... ... objects-data next update-cache-flag) (prog1 ... ...))) (save-restriction (widen) (let* (... ... ...) (cond ... ... ... ... ... ...) (goto-char ...) (let* ... ...))) (save-excursion (save-restriction (widen) (let* ... ... ... ...))) (org-with-wide-buffer (let* (... ... ...) (cond ... ... ... ... ... ...) (goto-char ...) (let* ... ...))) (catch (quote objects-forbidden) (org-with-wide-buffer (let* ... ... ... ...))) org-element-context() org-export-get-environment([cl-struct-org-export-backend html nil ((bold . org-html-bold) (center-block . org-html-center-block) (clock . org-html-clock) (code . org-html-code) (drawer . org-html-drawer) (dynamic-block . org-html-dynamic-block) (entity . org-html-entity) (example-block . org-html-example-block) (export-block . org-html-export-block) (export-snippet . org-html-export-snippet) (fixed-width . org-html-fixed-width) (footnote-definition . org-html-footnote-definition) (footnote-reference . org-html-footnote-reference) (headline . org-html-headline) (horizontal-rule . org-html-horizontal-rule) (inline-src-block . org-html-inline-src-block) (inlinetask . org-html-inlinetask) (inner-template . org-html-inner-template) (italic . org-html-italic) (item . org-html-item) (keyword . org-html-keyword) (latex-environment . org-html-latex-environment) (latex-fragment . org-html-latex-fragment) (line-break . org-html-line-break) (link . org-html-link) (node-property . org-html-node-property) (paragraph . org-html-paragraph) (plain-list . org-html-plain-list) (plain-text . org-html-plain-text) (planning . org-html-planning) (property-drawer . org-html-property-drawer) (quote-block . org-html-quote-block) (quote-section . org-html-quote-section) (radio-target . org-html-radio-target) (section . org-html-section) (special-block . org-html-special-block) (src-block . org-html-src-block) (statistics-cookie . org-html-statistics-cookie) (strike-through . org-html-strike-through) (subscript . org-html-subscript) (superscript . org-html-superscript) (table . org-html-table) (table-cell . org-html-table-cell) (table-row . org-html-table-row) (target . org-html-target) (template . org-html-template) (timestamp . org-html-timestamp) (underline . org-html-underline) (verbatim . org-html-verbatim) (verse-block . org-html-verse-block)) ((:html-extension nil nil org-html-extension) (:html-link-org-as-html nil nil org-html-link-org-files-as-html) (:html-doctype "HTML_DOCTYPE" nil org-html-doctype) (:html-container "HTML_CONTAINER" nil org-html-container-element) (:html-html5-fancy nil "html5-fancy" org-html-html5-fancy) (:html-link-use-abs-url nil "html-link-use-abs
[O] ellipses upon isearch
I am still getting ellipses upon isearch, despite setting all relevant variables to show the entire hierarchy, siblings, etc. Can isearch reveal canonically? Thanks.
Re: [O] Lisp code blocks fail
Hi Tom,
That example works for me. Perhaps you could edebug (C-u C-M-x) the
`org-babel-execute:lisp' function and then run that code block again to
see at which statement the error is thrown.
I'm not sure what the problem could be.
Best,
t...@tsdye.com (Thomas S. Dye) writes:
> Hi Eric,
>
> #+begin_src lisp
> (+ 1 1)
> #+end_src
>
> Debugger entered--Lisp error: (wrong-type-argument listp "2")
> byte-code("\211A@)\207" [result x] 2)
> org-babel-execute:lisp("(+ 1 1)" ((:comments . "") (:shebang . "")
> (:cache . "no") (:padline . "") (:noweb . "yes") (:tangle . "no")
> (:exports . "code") (:results . "replace") (:session . "none")
> (:hlines . "no") (:result-type . value) (:result-params "replace")
> (:rowname-names) (:colname-names)))
> org-babel-execute-src-block(nil)
> org-babel-execute-src-block-maybe()
> org-babel-execute-maybe()
> org-babel-execute-safely-maybe()
> run-hook-with-args-until-success(org-babel-execute-safely-maybe)
> org-ctrl-c-ctrl-c(nil)
> ad-Orig-call-interactively(org-ctrl-c-ctrl-c nil nil)
> (with-no-warnings (ad-Orig-call-interactively function record-flag keys))
> (setq ad-return-value (with-no-warnings (ad-Orig-call-interactively
> function record-flag keys)))
> (let ((ido-ubiquitous-next-override
> (ido-ubiquitous-get-command-override function))) (setq ad-return-value
> (with-no-warnings (ad-Orig-call-interactively function record-flag
> keys
> (ido-ubiquitous-with-override (ido-ubiquitous-get-command-override
> function) (setq ad-return-value (with-no-warnings
> (ad-Orig-call-interactively function record-flag keys
> (let (ad-return-value) (ido-ubiquitous-with-override
> (ido-ubiquitous-get-command-override function) (setq ad-return-value
> (with-no-warnings (ad-Orig-call-interactively function record-flag
> keys ad-return-value)
> call-interactively(org-ctrl-c-ctrl-c nil nil)
>
> Org-mode version 8.2.3b (release_8.2.3b-200-gb6522a @
> /Users/dk/.emacs.d/src/org-mode/lisp/)
>
> All the best,
> Tom
>
> Eric Schulte writes:
>
>> Hi Tom,
>>
>> Could you provide a minimal example? I'm unable to debug from the stack
>> trace alone.
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
Re: [O] [BUG] call results not creating #results
Fixed, thanks for reporting. Rick Frankel writes: > Eric- > > Since you're looking at call lines :)... > > there is a (fairly new i think) bug: > > When searching forward for results, following call lines are not > being respected as stop points. For instance, given: > > #+BEGIN_SRC org > ,* Call block test > ,#+name: call-me > ,#+BEGIN_SRC emacs-lisp :var v="one" > v > ,#+END_SRC > > ,#+RESULTS: call-me > : one > > ,#+call: call-me(v="two") > > ,#+RESULTS: > : two > #+END_SRC > > If i insert a new call-block before "two" and execute it, the following > occurs > > #+BEGIN_SRC org > ,* Call block test > ,#+name: call-me > ,#+BEGIN_SRC emacs-lisp :var v="one" > v > ,#+END_SRC > > ,#+RESULTS: call-me > : one > > ,#+call: call-me(v="three") > > ,#+call: call-me(v="two") > > ,#+RESULTS: > : three > #+END_SRC > > as you can see, it replaced the results for call-line two. > > Note that if i had named "two" and executed it before adding in call > line "three", the results would be > ok: > > #+BEGIN_SRC org > ,* Call block test > ,#+name: call-me > ,#+BEGIN_SRC emacs-lisp :var v="one" > v > ,#+END_SRC > > ,#+RESULTS: call-me > : one > > ,#+call: call-me(v="three") > > ,#+RESULTS: > : three > > ,#+name: two > ,#+call: call-me(v="two") > > ,#+RESULTS: two > : two > #+END_SRC > > rick -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] Babel: the disappearing hline
Rick Frankel writes: > On 2013-11-13 09:17, Eric Schulte wrote: >> Perhaps we should change `org-babel-default-inline-header-args' to >> include `(:hlines "yes")'. If there is no push back on that change I'd >> be happy to make it. > > I agree. It would probably make the behavior less confusing. > Done. > > rick > -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
