Re: [O] [bug] org-insert-link fails on special characters in headlines
On Sun, 06 Jan 2013 07:45:47 +0100, Bastien spake thus: Using org-store-link followed by, in another file, org-insert-link RET RET fails on the following headline : * [[http://www.anywho.com/][test]] Please try to apply the patch by Samuel and let us know if it fixes your issue: http://thread.gmane.org/gmane.emacs.orgmode/64203 I'm getting plenty of awful Invalid read syntax: ) even though I cannot be sure it's not just me not being able to apply a patch. I tried :')
Re: [O] [bug] org-insert-link fails on special characters in headlines
is there a known issue about accepted characters in headlines that I'm not aware of ? There should be none, please test master if you can and report any problem. Using org-store-link followed by, in another file, org-insert-link RET RET fails on the following headline : * [[http://www.anywho.com/][test]] with No match - create this as a new heading? If the link is created in the same file, then it fails by trying to open the badly parsed url: http://www.anywho.com/][test]] (the desired behavior being to jump to the headline, not following the link). Shouldn't links be put in titles, or shouldn't titles with links inside them be linked to ? O:-)
[O] Globally set categories overwhelm tree inheritance
Happy new year list :) Constructing a custom agenda using (org-entry-get (point) CATEGORY t) in an org-agenda-skip-function, I found a rare case of strangely inherited property, when a #+Category:foo line is present (at the top of the file) : If an entry has no property drawer, it correctly inherits its CATEGORY property from its hierarchy, but if it *has* one, *not* featuring a category property, then the #+Category one supersedes that of the entry's hierarchy. I know #+Category is obsolete, and for subtree-category differentiation properties are the way to go, but I thought of it as a file-local fallback value, and apparently it's not reliable for this either, as it infringes inheritance logic when property drawers are present. Reporting just in case someone else still uses #+Category and bumps into it.
[O] [bug] org-insert-link fails on special characters in headlines
it looks like captured links won't take into account header text after or , hence capturing links to headlines featuring these will fail, is there a known issue about accepted characters in headlines that I'm not aware of ? There should be none, please test master if you can and report any problem. Using org-store-link followed by org-insert-link RET RET fails on the following headline : ** TODO Special chars in titles ! [[*Special%20chars%20in%20titles%20][Special chars in titles !]] The link ignores what follows the greater-than sign () and thus the inserted link is still-broken. Prior to this, I had some working tests with , it seems both and are treated differently. -- On Mon, 24 Dec 2012 01:56:24 +0100, Bastien spake thus: I suggest the priority is removed from the captured link. This is now the case in master, it will be part of 8.0. Great :)
[O] Priority cookies in org-store-link
Hi all, As for a recent git version, calling org-store-link on a subtree records its priority cookie in the link, which therefore breaks if the said priority is changed (“no match - create this as a new heading ?”) Links not featuring the priority succeed at finding the headline which has such a priority mark, so I suggest the priority is removed from the captured link. -- As a side note, testing to ask this, it looks like captured links won't take into account header text after or , hence capturing links to headlines featuring these will fail, is there a known issue about accepted characters in headlines that I'm not aware of ?
[O] Indenting into lists
Hi list, I often structure notes into (multi-level) lists, and copy-paste multi-line text into them, some of which gets pasted on column zero. For it to be part of the list item, it needs to be indented as such, which I'd like tab to do. ┏[ tab runs the command org-cycle ] ┃ When point is not at the beginning of a headline, execute the global binding ┃ for TAB, which is re-indenting the line. ┗ Problem is tab only indents to the first possible level, that is, until the bullets, like so: * heading - list item on many lines HERE is not enough to be in the list. So in order to achieve the desired behaviour, I have to press space and tab alternatively until the line reaches where it belongs (for that combination makes it be indented more and more), which becomes tedious when indenting a few lines across nested lists. Is there a better way to indent to the maximum point ? (Could tab cycle between all indenting points, like is automagical in python ? That would be truly awesome.) Thanks in advance
Re: [O] agenda view of repeated time-ranges
On Fri, 26 Oct 2012 15:05:07 +0200, Philipp Kroos spake thus: I want some events to show up every week with start and end-time in the agenda. Is it possible to combine a time-range with a repeater? I think I tried every combination of range and repeater, but I can only get one of both to work. Hi :) Did you try 2012-10-31 Mi 15:00-17:00 +1w ? #+begin_src org ** Weekly meeting 2012-10-31 Mi 15:00--2012-10-31 Mi 17:00 this doesn't repeat #+end_src org
[O] [BUG] Parsing consecutive stars
Hi list,
It looks like the stars parser has a problem with 2 consecutive stars, hence
with bold in 2nd level headers.
The following sums up all the relevant tests I performed. Only 3rd and 4th
lines seem to be related, in a strange fashion, even, but I couldn't find
anything else that would indicate lines not being independant.
* Test *it* !
* *Test thouroughly* !
** try deleting these : ** *** ** * ** *** **
** Is *this* bold ?
Note that anytime it is, editing the line gets the failure back.
*** From here, it all *seems* to *works* *fine*.
*** Only ** *here* it *doesn't !*
*** *More* ** so *even*.
I can try with text, it doesn't *change* ** *anything*.
*** Darn. ** Even if I add many words it *fails* !
Hope ! ** Even if I add many words it only *fails* *once* !
But ** *sadly* it ** can *fail* *many times* !
*** If I try with *** *more* stars, it's totally *fine*
It ** actually *** *helps*, *even*
You *do* ** need * *a few*.
But ** ** *two* is *enough*
While constructing this, I was using (recent git version, and)
(setq org-emphasis-regexp-components
'( \t('\{ - \t.,:!?;'\)}\\ \t\r\n,\' . 2))
but reverting to default with
(setq org-emphasis-regexp-components
'( \t('\{ - \t.,:!?;'\)}\\ \t\r\n,\' . 1))
showed no improvement regarding the weird behavior. (I do imagine things could
go a lot worse with hugher values, though ^_^)
(problem raised on
http://stackoverflow.com/questions/12736868/cant-use-bold-face-on-2nd-level-outline-in-emacs-org-mode)
[O] org today's entension
Hi all, Acknowledging that C-h v org-extend-today-until is a feature whose implementation is and likely will remain incomplete. Really, it is only here because past midnight seems to be the favorite working time of John Wiegley :-) I'm still dearly wishing it'd be developed further : Sometimes, I set appointments past midnight (it's, errr, the timezone's fault, I swear), and I'd rather have them displayed in the agenda on the day before, not to forget about them in daily view. (Even better, at the bottom of the day.) I guess it'll wait until I learn something of lisp, but where to start in order to implement that ? Kind regards, William
[O] Subtasks cookies out of export
Hi list, I use subtasks cookies in titles, as described in http://orgmode.org/manual/Breaking-down-tasks.html, along with todo keywords, when writing a document to be exported, and I'd like then NOT to be exported (for they're org metadata). Exporting to pdf, still using the default exporter. I would have guess there would be an #+option for that (removing the progress cookies), but I didn't find it in the export options page. How much is that possible ? Thanks in advance.
Re: [O] Shouldn't comment-region protect from export ?
On Thu, 02 Aug 2012 18:40:04 +0200, Bastien spake thus: William LÉCHELLE william.leche...@ens-lyon.fr writes: Using org-mode for export (to pdf), I find myself using comment-region often enough, in sections meant to be exported, on indented text lines (e.g. for drafting). This inserts # at the beginning of the line, after the indentation, thus not achieving what I wanted comment-region to do (i.e. don't export this). This is fixed now, thanks. Having just pulled from git, comment-region still gets me indented # lines, which still get exported (using the default exporter). How is it supposed to be fixed ?
Re: [O] Shouldn't comment-region protect from export ?
On Mon, 27 Aug 2012 11:24:21 +0200, Nicolas Goaziou spake thus: Having just pulled from git, comment-region still gets me indented # lines, which still get exported (using the default exporter). How is it supposed to be fixed ? I have pushed a patch against current exporter. Inlined comments should be properly removed now. Thanks, indeed, these no longer appear. Only now, my #+latex_header: is not properly exported, and rather protected and displayed in the document. I didn't check before the patch, but I guess it worked all right. I'm using subtree export, in case that matters.
Re: [O] Subtasks cookies out of export
On Mon, 27 Aug 2012 11:41:56 +0200, Nicolas Goaziou spake thus: I use subtasks cookies in titles, as described in http://orgmode.org/manual/Breaking-down-tasks.html, along with todo keywords, when writing a document to be exported, and I'd like then NOT to be exported (for they're org metadata). Exporting to pdf, still using the default exporter. I would have guess there would be an #+option for that (removing the progress cookies), but I didn't find it in the export options page. How much is that possible ? In the default exporter, you can add a function to `org-export-preprocess-hook' which will carefully remove every statistics cookie en the buffer. In the next exporter, you can still use that hook (named `org-export-before-parsing-hook' this time) or use the following: snip So, it [is] quite simple already to ignore them. I'm convinced, only I (still) lack the lisp knowledge to write such functions :/ Do you (and other users) think it's worth to add a customizable variable and an entry in the #+OPTIONS: line (perhaps with a stat:nil value) to achieve the same? I don't know how much is this feature used, nor specifically for exporting, but I do believe such an entry belongs to the #+OPTIONS line (just like priorities, tags, etc.) Thanks for dealing with this, William
Re: [O] Shouldn't comment-region protect from export ?
On Mon, 27 Aug 2012 12:16:22 +0200, Nicolas Goaziou spake thus: William Léchelle william.leche...@ens-lyon.fr writes: Only now, my #+latex_header: is not properly exported, and rather protected and displayed in the document. I didn't check before the patch, but I guess it worked all right. I'm using subtree export, in case that matters. I knew I shouldn't have messed again with old exporter... Anyway, I pushed a fix to the fix. Does it behave as expected now? Yes, it works perfectly, thank you very much ! -- William
[O] Shouldn't comment-region protect from export ?
Hi list :) Using org-mode for export (to pdf), I find myself using comment-region often enough, in sections meant to be exported, on indented text lines (e.g. for drafting). This inserts # at the beginning of the line, after the indentation, thus not achieving what I wanted comment-region to do (i.e. don't export this). I suggest #+ to be inserted instead, for that seems to me to be the correct prefix for indented comments. I'd rather keep it all indented and not having # at position 0 (breaking what follows' default indentation, æsthetics apart). I don't remember having overridden any comment-prefix variable of any sort (but maybe I did, I just don't know what that variable would be). Am I doing something wrong, or are my expectations misplaced ? (is there a meaning to comment for org text I can't think of that # satisfies and #+ wouldn't, maybe ?) William
Re: [O] text to plain list
Hi Marvin, Is there quick method for converting a bunch of text to plain list ? C-u C-c - makes every line of the active region a list item (C-c - makes the region one item, the bullet on the first line) If you want each word to become an item, what I usually do is replace (optionnaly by regexp if you master that) spaces by a newline (C-q C-j) and a dash, and then, org-moving-around the list nicens it up, typically. (C-M-% SPC * C-q C-j * [A-z] … … …)
Re: [O] Selective export of Babel code blocks
On Mon, Jun 18, 2012 at 6:50 PM, John Hendy jw.he...@gmail.com wrote: #+name: preamble #+begin_src R :exports none tikzDevice(file-name) #+end_src Are you trying to use file-name as a variable? if so I think the source block header should include this: :var file-name and the source block can refer to the variable as $file-name. It seems to me one of both ,[ insert preamble ] | preamble | with the preamble having the header | :var file-name=file_1.tex ` or ,[ eval preamble ] | preamble(file-name=file_1.tex) | without any :var header ` would be correct syntax, but using :var variable without assigning it should fail (though I didn't test it). Both wouldn't give the same result… And by the org-mode Babel documentation it looks like I can do something like: preamble(file-name=file_1.tex) I'm not sure about this. The syntax seems correct but I don't quite understand the following statement from the manual: It is possible to include the _results_ of a code block rather than the body. This is done by appending parenthesis to the code block name which may optionally contain arguments to the code block as shown below. code-block-name(optional arguments) … as I read this as the noweb reference will expand in either 1. The litteral of the code-block if there are no parenthesis 2. The results of the block (as obtained with C-c C-c or org-babel-execute-src-block) (which may depend of a :results header, maybe), if parenthesis are present. So if the OP wants to call the preamble block with an argument in the noweb reference, then the preamble block might have to be more like #+name: preamble #+begin_src R :results output print(tikzDevice(file-name)) #+end_src called with preamble(file-name=file_1.tex) (but I don't know any R either, I just went myself through variable substitution over the weekend) Last alternative, which I use, is putting the file name in some named table, and then passing it as an argument to ,[ insert preamble ] | preamble | with the preamble having the header | :var file-name=some-table[0,1] ` (Like #+tblname: some-table | file| file_1.tex | ) HTH, William
Re: [O] Cannot use #+call correctly with babel
At Sat, 16 Jun 2012 18:31:53 +0200, Benoit Bayol wrote: All the mixes on headers I tried have been failures. Here is my example source : http://pastebin.com/63uHDvZH Does anyone see why I cannot have the output of the code and the results in the last sections ? Hi Benoit, I may be wrong, but I ran into problems with #+call-s and header positions also recently, and most of it was solved when I understood the manual #+CALL: name(arguments) required the empty parenthesis() even if no argument were provided. I now use : #+CALL: name-of-block[:results output]() :results replace So maybe you lack parenthesis (or maybe I misunderstood it), and maybe you should try to put your headers in end header arguments, after the parenthesis. HTH,
Re: [O] Scheduling: Finishing a task 'Yesterday' OR Repeat on the same day
org-mode thinks I finished it for 'today' because it's after 0AM and schedules it for 'tomorrow'. This way, I'll forget it for one day. Is there a simple day to say: I finished this task yesterday without me having to manually change every date in the tree, the PROPERTIES drawer, and in the Logbook? Is the org-extend-today-until variable what you're searching for ? (Assuming you don't do anything past midnight you don't consider to be done the day before.)
Re: [O] python/babel inline images
At Tue, 05 Jun 2012 08:57:19 -0600,
Eric Schulte wrote:
henry atting nsmp...@online.de writes:
Hi,
I do not succeed in generating an inline image as a result of a
python code block. The code itself works, C-c C-c generates the
according picture, but only in my home directory. The code block:
-*- org-babel-python-command: python3 -*-
#+begin_src python
import csv
import matplotlib.pyplot as plot
x = []
y = []
csv_reader = csv.reader(open('csv_data.csv'))
for line in csv_reader:
x.append(int(line[0]))
y.append(float(line[1]))
plot.plot(x, y, label=r'exp', color='green')
plot.legend(loc='lower right')
plot.savefig(exp_csv.svg)
#+end_src
It tried different combinations of `:exports results', `:results
file', `:file filename'
I'm not python expert, but the code block should be run in your current
directory, e.g., the following outputs the current working path expected
for me.
#+begin_src sh
pwd
#+end_src
If you want to explicitly pass the current directory to your code block
as an argument, you could try something like the following
#+begin_src python :var mydir=(file-name-directory (buffer-file-name))
return mydir
#+end_src
I guess if it's a paths' problem, the python equivalent would be os.getcwd(),
from the os module, and a solution to have the picture in the right place
could be os.chdir(path) (or maybe plot.savefig can take a full path as an
argument), but I think the OP (and I'm very interested too) wants org-babel to
manage the python output somehow to inline the image automatically.
I don't see that possible, because I don't think the results of plot.savefig
is the value of the image, but rather an i/o operation somehow (and I may well
be wrong) (and nothing goes to stdout). But maybe to output a link could do ?
#+begin_src python :results output file
stuff
path = exp_csv.svg
plot.savefig(path)
print path
#+end_src
HTH
Re: [O] plain text best practice?
I'd go the first way if you don't need/use much markup, but if you want to structure more deeply your document, you can have subheadings without actually giving them a title (just the stars and a blank space are enough for a heading) It's also a matter of what you want to do with the document, if you plan to export it, the subheadings will change the result in ways you may like or dislike. (You don't seem to have any usage of lists, so simply don't go for them.) At Tue, 5 Jun 2012 22:38:13 -0500, scraw...@gmail.com wrote: howdy guys, I want to use org-mode for writing documents that don't necessarily have very many headings or sub-headings. I could do: * Chapter One lots of text * Chapter Two lots more text or: * Chapter One - lots of text * Chapter Two - lots more text or: * Chapter One ** paragraph 1 lots of text ** paragraph 2 lots of text * Chapter Two ...but I'm not sure which to use. It almost seems like the last format is the best, but I don't want to type paragraph headings. Maybe the first few words of the paragraph could be a heading after the fact, but not as I write. Apologies for such a basic question, but I how can I leverage org-mode to just write? What do you do? thanks
