Re: [O] result of code evaluation
Am 19.08.2011 21:06, schrieb Henri-Paul Indiogine: Greetings! I am just now starting to use babel in my org-mode files. I am intrigued by its capabilities, but I encountered a strange phenomenon: 8---8- #+srcname: test #+begin_src sh :results value #!/bin/bash echo hello #+end_src #+results: test : hello ---8-8 Why is there a : at the beginning of the results line? Can I get rid of it? Thanks, Henri-Paul I dont know, but the example on http://orgmode.org/guide/Working-With-Source-Code.html also includes a ':' at the beginning of the line.
[O] exporting to HTML: strong instead of b for *bold text*
Hi. Exporting org to HTML, is there a way to use the strong-tag instead of b for *bold text* and em instead of i for /italic text/? Thanks in advance. Bye.
[O] *bold*text
Hi. *bold*text or /italic/text doesn't work unless you seperate those words. You can work it around with @bfoo@/bbar but that'd neither be generic nor work on multiple export-backends. It'd be great if that'd work =) (Thanks to Thumper_ from #orgmode for the work-around.) Bye.
Re: [O] *bold*text
Am 14.08.2011 18:20, schrieb Bastien: Hi, imi...@ymail.comimi...@ymail.com writes: *bold*text or /italic/text doesn't work unless you seperate those words. You can work it around with @bfoo@/bbar but that'd neither be generic nor work on multiple export-backends. It'd be great if that'd work =) See the docstring of `org-emphasis-regexp-components': , | Components used to build the regular expression for emphasis. | This is a list with five entries. Terminology: In an emphasis string | like *strong word* , we call the initial space PREMATCH, the final | space POSTMATCH, the stars MARKERS, s and d are BORDER characters | and trong wor is the body. The different components in this variable | specify what is allowed/forbidden in each part: | | pre Chars allowed as prematch. Beginning of line will be allowed too. | post Chars allowed as postmatch. End of line will be allowed too. | border The chars *forbidden* as border characters. | body-regexp A regexp like . to match a body character. Don't use | non-shy groups here, and don't allow newline here. | newline The maximum number of newlines allowed in an emphasis exp. ` HTH, thank you very much!
Re: [O] exporting to HTML: strong instead of b for *bold text*
Am 14.08.2011 18:06, schrieb Nicolas Goaziou: Hello, imi...@ymail.comimi...@ymail.com writes: Exporting org to HTML, is there a way to use thestrong-tag instead ofb for *bold text* andem instead ofi for /italic text/? See `org-emphasis-alist'. Regards, thank you very much!
Re: [O] exporting to HTML: strong instead of b for *bold text*
Am 14.08.2011 18:19, schrieb Bastien: imi...@ymail.comimi...@ymail.com writes: Exporting org to HTML, is there a way to use thestrong-tag instead of b for *bold text* andem instead ofi for /italic text/? You want to customize `org-emphasis-alist'. HTH, thank you very much!
[O] html-export: Unique, non-enumerated heading-IDs according to heading
Hi. Usually, when you export an org-document to HTML, the headings get enumerated IDs (which are in particular important for anchors) like this: * this is my first heading * the second one This org-code (more or less) becomes: h2 id=sec-1this is my first heading/h2 h2 id=sec-2the second one/h2 But this behaviour is not always ideal: If you add a heading the ID of all following headings changes -- unless you didn't set the CUSTOM_ID property manually. So, this e-mail requests the feature that it should be possible to make Org automatically set the ID according to the content of the heading. E.g.… * foobar * this heading includes lots of spaces and some other special characters like §$%/() … would become this: h2 id=foobarfoobar/h2 h2 id=this_heading_includes_lots_of_spaces_and_some_other_special_characters_like_this heading includes lots of spaces and some other special characters like §$%/()/h2 What do you think? Wouldnt that be nice? I think you should be able to switch between these two behaviours -- both have their own advantages. Having said this, Goodbye.
Re: [O] Hyperlink handling broken
Am 21.07.2011 19:29, schrieb Marcelo de Moraes Serpa: Hi guys, Hyperlink handling for org is kind of broken for me. Each time I click a hyperlink in an org file, it will create a new instance of Firefox. Does someone know how to change the browser (to Chrome, for example) and make it open subsequent links in the same browser instance, as tabs? Thanks in advance, - Marcelo. Hi, as far as I know this is a general Emacs-issue, not an orgmode-issue; nevertheless, here's my (working) solution: In your ~/.emacs, insert this (or something similar): (setq browse-url-browser-function 'browse-url-generic browse-url-generic-program firefox) This opens a new Firefox-tab for me.
