[O] org-edit-special behavior
Dear org-ers, I am using babel more often. The way I do it is together with R and LaTeX. That means I have a certain window layout with .org, .r, ESS, latex output, etc. buffers. All in all that makes around 6 buffers. Now when I use C-c ' to edit a babel src block in a temporary buffer, my layout gets shadowed, presenting me with the org buffer from where org-edit-special was called and the editing buffer. How can I change that behavior so that org-edit-special uses the existing layout or can it be told which window to use? Best Regards, Michael
Re: [O] odt export error
Hi, Looking into your styles.xml, it seems openoffice is choking on the representation of the bullet character. Exporting your org document with the default stylesheet in Org 7.8 works (result attached), with a valid unicode bullet character in the styles.xml. It is likely that you are running an old bleeding-edge development version of the ODT exporter. If you can update to Org 7.8, you should do that; as of this week, the ODT exporter is part of core Org. (And when you update, clean out old versions of org-odt from your load-path and your .emacs.) hope this helps, Christian On 12/14/11 4:03 AM, Kevin Emerson wrote: Hello all, I am relatively new to org-mode, but I am certainly a convert - a great piece of work! I usually export things as html, but my employer always wants updates in doc format. I was hoping to use the new odt export functionality and then I can save the odt as a doc file. This works for me sometimes - but not always. I can not pinpoint exactly what yields the error, but it reads Format error discovered in the file in sub-document styles.xml at 415,108(row,col) when the file attempts to open in openoffice 3.2. I am using org-mode 7.6. I have attached my org file and the resulting odt file. Any thoughts would be greatly appreciated. Cheers, Kevin 2011-12-13-periodAnnotationTranscriptome2.odt Description: application/vnd.oasis.opendocument.text
Re: [O] ePub construction
Alan L Tyree alanty...@gmail.com writes: On 14/12/11 12:42:38, Nick Dokos wrote: Interesting - I downloaded the epub validator, ran Calibre on a silly little org-produced HTML file and duplicated your lang problem. AFAICT, all of the problems you mention above are legal HTML4, so either the epub spec (which I have not looked at: do you have a pointer?) is made to trip people up by enforcing restrictions that they dreamed up, or the validator is not quite as smart as it should be. Yes, the org export file validates at w3c as a valid XHTML1.0 file. The ePub spec is here: http://idpf.org/epub but I admit fatigue in trying to wade through it, so I don't know what XHTML1.0 constructions it objects to. It seems like the kind of document that nobody has ever read: sort of like EULAs and express warranties. I took a quick look through http://idpf.org/epub/20/spec/OPS_2.0.1_draft.htm and right to the beginning http://idpf.org/epub/20/spec/OPS_2.0.1_draft.htm#Section1.3 1.3: Relationship to Other Specifications it says: This specification combines subsets and applications of other specifications. Next, in http://idpf.org/epub/20/spec/OPS_2.0.1_draft.htm#Section1.3.4 1.3.4: Relationship to XHTML and DTBook it talks about ..., the Preferred Vocabularies do not include all XHTML 1.1 elements and attributes. So, even if you have a valid XHTML file, only a subset of it might be valid for an epub book. Same goes for CSS. Lazy as I am, I haven't looked through the other epub parts, since this seems not relevant here. Another interesting epub checker might be http://code.google.com/p/epubcheck/, which uses ... schemas that were developed by IDPF and DAISY. ... according to their website. Regards, Olaf
Re: [O] [PATCH] customize latex table export
Christophe Rhodes cs...@cantab.net writes: Christophe Rhodes cs...@cantab.net writes: Carsten Dominik carsten.domi...@gmail.com writes, a long time ago: would it be better to be able to set these parameters on a per-table basis with ATTR_LaTeX ? Would you like to try to prepare a patch to this effect? Find attached a patch to this effect. Is there anything else that I can do to encourage this patch into the upstream org-mode? Again, is there anything more I can do to get this functionality (customizing header lines of tables in LaTeX export, in case everyone has lost the context) into org-mode? Best, Christophe
Re: [O] http://libremanuals.net (ikiwiki+org) to translate the Org Guide
Bastien, thanks for the announce. For now, I've enabled english, spanish and french in the libremanual ikiwiki, but if someone wants translate the org compact guide ( http://www.libremanuals.net/orgguide/index.en.html) to another language, let me know and I'll enable a new language. Best. El 13 de diciembre de 2011 20:48, Bastien b...@altern.org escribió: Dear all, another announcement about translation : David Arroyo Menéndez (who already translated David O'Toole's tutorial) is launching LibreManuals to help with translating/publishing FLOSS book. Libremanuals uses ikiwiki (http://ikiwiki.info/) a wiki compiler. It builds static HTML pages for a wiki, from source in the ikiwiki/Markdown language (or others, such as texinfo or org-mode), and writes it out to destination. Libremanuals is using org-mode files to manage the tasks to do in an integrated way with ikiwiki thanks to the org ikiwiki plugin http://www.golden-gryphon.com/software/misc/org.pm.html Please check the website and contribute on it (it's a wiki) or through the git repository: having the Org Guide in several languages would be great! Thanks to David for setting this up, and to you all for your attention! (And I'm done with announcements.) Best, -- Bastien -- David Arroyo Menéndez http://www.davidam.com
Re: [O] http://libremanuals.net (ikiwiki+org) to translate the Org Guide
Dear David, Hi. I have organized a translation project into Japanese. We work hard to translate the org manual, and near future, we are going to start On 2011/12/14, at 8:29, David Arroyo Menéndez wrote: Bastien, thanks for the announce. For now, I've enabled english, spanish and french in the libremanual ikiwiki, but if someone wants translate the org compact guide (http://www.libremanuals.net/orgguide/index.en.html) to another language, let me know and I'll enable a new language. Best. El 13 de diciembre de 2011 20:48, Bastien b...@altern.org escribió: Dear all, another announcement about translation : David Arroyo Menéndez (who already translated David O'Toole's tutorial) is launching LibreManuals to help with translating/publishing FLOSS book. Libremanuals uses ikiwiki (http://ikiwiki.info/) a wiki compiler. It builds static HTML pages for a wiki, from source in the ikiwiki/Markdown language (or others, such as texinfo or org-mode), and writes it out to destination. Libremanuals is using org-mode files to manage the tasks to do in an integrated way with ikiwiki thanks to the org ikiwiki plugin http://www.golden-gryphon.com/software/misc/org.pm.html Please check the website and contribute on it (it's a wiki) or through the git repository: having the Org Guide in several languages would be great! Thanks to David for setting this up, and to you all for your attention! (And I'm done with announcements.) Best, -- Bastien -- David Arroyo Menéndez http://www.davidam.com signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] http://libremanuals.net (ikiwiki+org) to translate the Org Guide
Dear all and David, Sorry I sent an incomplete mail, it's my mistake. please ignore the previous e-mail. David Near future, I'll contribute a Japanese translation. Could you setup the libremanual ikiwiki for Japanese? Best regards, Takaaki Ishikawa @takaxp signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] odt export error
Kevin Emerson kemer...@uoregon.edu writes: Hello all, I am relatively new to org-mode, but I am certainly a convert - a great piece of work! I usually export things as html, but my employer always wants updates in doc format. I was hoping to use the new odt export functionality and then I can save the odt as a doc file. This works for me sometimes - but not always. I can not pinpoint exactly what yields the error, but it reads Format error discovered in the file in sub-document styles.xml at 415,108(row,col) when the file attempts to open in openoffice 3.2. I am using org-mode 7.6. I had this error when I first tried the odt exporter. I think you may wish to upgrade to a more recent version of org; 7.6 is quite old, especially for ODT export. The file you attached exports fine for me in org 7.8.02. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.02 (release_7.8.02.2.g490d6a)
Re: [O] Refresh of http://orgmode.org
Bastien b...@altern.org writes: Viktor Rosenfeld listuse...@googlemail.com writes: - The old homepage had all the easily accessible information on one page. So you could go to the homepage, search for manual or mailing list and go on from there. (I sometimes work like that.) The new homepage only contains screenshots (that don't convey a lot of meaningful information) and the org-mode mission statement. Useful information is available but the links are somewhat hidden in the description of what org is about and some are hard to find. (E.g. the manual is linked with the text documented extensively.) I believe that people quickly scan web pages for relevant information and the current format makes that hard. I somehow agree that it was good to have everything in one page, but I don't think that page was *that* readable. In any case, you can always I agree with Bastien here. In fact, I used to use the old website in the manner the new one requires: using the left index to go to the bit I wanted. The new one is more obvious in this regard. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.02 (release_7.8.02.2.g490d6a)
Re: [O] Refresh of http://orgmode.org
Bastien b...@altern.org writes: Hi Eric, Hi Bastien! Eric S Fraga e.fr...@ucl.ac.uk writes: The only thing I don't particularly care for is the twitter box. If I have the browser visible visiting this page, as I do right now, and especially on a separate monitor, I keep getting distracted by motion in my peripheral vision! It's almost worse because of the faint display of the box when not hovering over it. Minor point, mind you; I just don't like animations on web sites... others will of course disagree! If people want to get rid of this box in the index* pages, no objection. But.. wait.. why do you keep the index.html page open then? I don't make oops-here-is-another-stupid-bugfix-releases *that* often :) Very true! I guess I was in a pedantic or picky mood last night... :( Ignore my rant. The site looks very nice otherwise! -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.02 (release_7.8.02.2.g490d6a)
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Christian Moe m...@christianmoe.com writes: 2. I see where the default styles are and I am happy with these generally. However, as a libreoffice n00b, how do I create my own style file that would be appropriate for the ODT exporter? It's not so much about the creating of style files (although help in that regard would not be sniffed at ;-) but about whether there is a list of paragraph styles that can be customised somewhere? The easiest way is now described in the manual: write your document in Thanks Christian! Org, including all the sorts of stuff you might want to have styles for, then export it to ODT, open it in LibreOffice, and tweak the styles you find there. Because you exported it from Org, you can be sure that the styles have the names the exporter uses. You can customize any style, no limits. Okay, that makes perfect sense. When your LibreOffice document looks like you want it to, simply save it somewhere smart. The next time you export from Org, point org-export-odt-styles-file to that file as your style template. Straightforward. Of course, getting libreoffice to do what I want is another story... ;-) I imagine I'll have to use a mouse :-( Give me latex any day! Thanks again, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.02 (release_7.8.02.2.g490d6a)
Re: [O] Refresh of http://orgmode.org
Hi Eric, Eric Schulte eric.schu...@gmx.com writes: +1 for preferring the old screenshot, for exactly those reasons mentioned above. While it is fun for me to look at random screenshots from Worg, part of the purpose of this site is as a gateway to Org-mode, and I fear many of these random screenshots are meaningless (or even intimidating) unless you already have a good understanding of Org-mode. Again, I agree. Patch welcome! - I don't like the fixed top bar with the Org-Mode motto and the random quote. It takes up about 20% of vertical screen space of my laptop. A complete waste in my view. The black background also does not cover the text behind it -- one or two pixel of the text are visible above the bar. I also find that (in part because of the new larger screenshots) I can't see any content upon first loading the page (see this screenshot [1]). Mh.. your screen seems quite small. If you can fix the .css to display the website better on your screen, please do, I don't have time at hand now to do it myself. - The old homepage had all the easily accessible information on one page. So you could go to the homepage, search for manual or mailing list and go on from there. (I sometimes work like that.) The new homepage only contains screenshots (that don't convey a lot of meaningful information) and the org-mode mission statement. Useful information is available but the links are somewhat hidden in the description of what org is about and some are hard to find. (E.g. the manual is linked with the text documented extensively.) I agree that the manual should be linked with the term manual, as (unfortunately IMO) it seems many Emacs and Org-mode users aren't comfortable using the build in Emacs info system and prefer to use the online manual exclusively. Well, the manual is two clicks away: 1) Documentation 2) The online manual I find it good to gather every available documentation in one single page, that people will later be exposed to when looking for orgmode documentation. That's also the benefit of having one page. And one Google Search away: http://www.google.fr/search?ie=UTF-8q=orgmode+manual - http://orgmode.org/org.html Aside from those items mentioned above I do generally like the style of the new site. Thanks! -- Bastien
Re: [O] [PATCH] customize latex table export
Hi Christophe, Christophe Rhodes cs...@cantab.net writes: Again, is there anything more I can do to get this functionality (customizing header lines of tables in LaTeX export, in case everyone has lost the context) into org-mode? I saw your patch, thanks for it. I'm willing to apply it, but I will do when I have a good idea of how it interacts with Niels proposal, and maybe a generalization of Niels idea, where it would be possible to set a default #+ATTR for tables, images, etc. Best, -- Bastien
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Of course, getting libreoffice to do what I want is another story... ;-) I imagine I'll have to use a mouse :-( Well, you can always author your own styles file in plain XML conforming to the ODF specification. No mouse required!... ;-) Christian
Re: [O] http://libremanuals.net (ikiwiki+org) to translate the Org Guide
Done! Please send me your public ssh key to make an unix account and can do git clone and git push Best El 14 de diciembre de 2011 10:44, Takaaki ISHIKAWA tak...@ieee.orgescribió: Dear all and David, Sorry I sent an incomplete mail, it's my mistake. please ignore the previous e-mail. David Near future, I'll contribute a Japanese translation. Could you setup the libremanual ikiwiki for Japanese? Best regards, Takaaki Ishikawa @takaxp -BEGIN PGP SIGNATURE- iQEcBAEBAgAGBQJO6HAWAAoJEFwinLr9JisS07EIAJPq12t2fA+D1NgfMTY2afyJ YeXCblrm3e8YBlh+HCCHDtMNo9lUfm83z/I5wopNTYzDUED3N7MnCou1jaz+W0eR wXjSlL+sQj9TtvazcdSypwtHAGUdiw5xyTP0nQ+D3RXFEwzv5/8TrOX5UraSDz/9 0ywKrz1Hw++GIaiL+R+ARZkEKqJElJ5oBhchLTUweV98COY2CT033Qc/mdf9wIOB PYfZigtqb42m51AmGB8lDQT+IUwBOXgifZIHWeSnpLh4WZGEnQzCkpyR82pQElaT Ps8nioKvKsRvugSKigYMv9vv7zDUjeUObpJpjfIo13J6jshd0LM5GXjbwi3VLp0= =nL5d -END PGP SIGNATURE- -- David Arroyo Menéndez http://www.davidam.com
Re: [O] Refresh of http://orgmode.org
Hi Bastien, Bastien wrote: - The old screenshot conveyed what org-mode was all about. Outlining and project planning. The new screenshots take a lot longer to load and even if you click on them, their content is not always accessible. I agree. Feel free to contribute to Worg with relevant screenshots that we can select as featured on the index page. Also add title and caption for these screenshots. I think the old screenshot was good enough. A link beneath it to the screenshot page on Worg would be useful. - I don't like this particular type writer font. On a Mac it's very thin compared to the serifless font that makes up the normal text. But that's just aesthetics. - I don't like the fixed top bar with the Org-Mode motto and the random quote. It takes up about 20% of vertical screen space of my laptop. A complete waste in my view. The black background also does not cover the text behind it -- one or two pixel of the text are visible above the bar. Can you make an alternate .css with non-fixed top bar and a better font? Maybe on the weekend, but I can't promise anything. - The old homepage had all the easily accessible information on one page. So you could go to the homepage, search for manual or mailing list and go on from there. (I sometimes work like that.) The new homepage only contains screenshots (that don't convey a lot of meaningful information) and the org-mode mission statement. Useful information is available but the links are somewhat hidden in the description of what org is about and some are hard to find. (E.g. the manual is linked with the text documented extensively.) I believe that people quickly scan web pages for relevant information and the current format makes that hard. I somehow agree that it was good to have everything in one page, but I don't think that page was *that* readable. In any case, you can always pull the website (it's just a git repository) and you have everything in one directory. I agree that the old page wasn't very readable as it did contain a lot of information. I just don't feel that the new layout is better, on the contrary. Cheers, Viktor
Re: [O] Refresh of http://orgmode.org
Dear Viktor, dear Bastien, On 13.12.2011, at 22:50, Viktor Rosenfeld wrote: [...]- I don't like this particular type writer font. On a Mac it's very thin compared to the serifless font that makes up the normal text. But that's just aesthetics. - I don't like the fixed top bar with the Org-Mode motto and the random quote. It takes up about 20% of vertical screen space of my laptop. A complete waste in my view. The black background also does not cover the text behind it -- one or two pixel of the text are visible above the bar. I really like the new web site look (thanks, Bastien!): I tested it on a Mac with recent versions of Firefox, Safari and Opera and was (so far) very pleased with both usability and aesthetics. However, that was on a machine with a large screen and I can imagine that some layout and font decisions could be improved for smaller systems - it does not work so well on the iPhone where I also did some testing. Almost every web site has that problem - the solution usually is to provide more than one stylesheet and provide a suitable one depending on the browser identification; this works well with most SmartPhones and the iPad. We have some institute-internal services that do this (not difficult to implement with PHP) - is this an option for the current orgmode-site? Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Head of IT group Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 Email: voll...@nf.mpg.de http://www.nf.mpg.de smime.p7s Description: S/MIME cryptographic signature
Re: [O] ePub construction
Olaf Dietsche olaf+list.orgm...@olafdietsche.de wrote: ... Another interesting epub checker might be http://code.google.com/p/epubcheck/, which uses ... schemas that were developed by IDPF and DAISY. ... according to their website. I'm pretty sure it's the same checker as the online checker that Alan pointed to. Nick
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Christian Moe m...@christianmoe.com wrote: Of course, getting libreoffice to do what I want is another story... ;-) I imagine I'll have to use a mouse :-( Well, you can always author your own styles file in plain XML conforming to the ODF specification. No mouse required!... ;-) ... or write an elisp function to snag the XML style file from wherever libreoffice squirrels it into emacs, where you can edit it - testing might be a bit more painful though... Nick
[O] org-column face
Hello. Why org-column has a different font, than default? It's event not monospace! (DejaVu Sans in my case (foncofig's default)) OK. I want to set org-column font to same as default font. How should I do this? (set-face-font 'org-column (face-font 'default)) Doesn't work, is says: error: Invalid face, org-column OK, but (add-hook 'org-mode-hook (lambda () (set-face-font 'org-column (face-font 'default also doesn't work, without any error. (add-hook 'org-mode-hook (lambda () (set-face-font 'org-column terminus-10))) works, but I don't want to write terminus-10 twice in my config. -- sergio.
[O] reftex setup problem
Hi,
Problems incorporating references/citations in .org-files.
I have set up a refs.bib-file for my references using jabref 2.6.
In org-mode 7.7 I have used the suggestion in FAQ for Marios reftex
setup in my .emacs:
(defun org-mode-reftex-setup ()
(load-library reftex)
(and (buffer-file-name)
(file-exists-p (buffer-file-name))
(reftex-parse-all))
(define-key org-mode-map (kbd C-c )) 'reftex-citation))
(add-hook 'org-mode-hook 'org-mode-reftex-setup)
In my .org-file I put the path to my refs.bib-file:
\bibliography{/home/nikolai/Dokument/Artiklar/refs}
When I use the Cc) in my .org-file I get:
Regex { Regex...}: in the minibuffer
Trying to type the bibtexkey in the minibuffer it finds no match.
If I manually enter:
\cite{Bursi2010}
and export I get:
LaTeX Warning: Citation `Bursi2010' on page 1 undefined on input line 33.
LaTeX Warning: There were undefined references.
Where is the problem hidden?
bibtex-file, reftex setup, org-mode, or emacs?
Nikolai
Re: [O] org-column face
On 12/14/2011 06:25 PM, sergio wrote: Why org-column has a different font, than default? I just realized (thank to Nick, who answered personally to me), that if I write: (set-face-font 'default terminus-10) org-column uses this font, but I want to define default font so: (setq default-frame-alist '( ... (font . terminus-10) ... )) -- sergio.
Re: [O] http://libremanuals.net (ikiwiki+org) to translate the Org Guide
Hi David, Thanks a lot! I'll send you the key directory soon. Best regards, Takaaki On 2011/12/14, at 20:19, David Arroyo Menéndez wrote: Done! Please send me your public ssh key to make an unix account and can do git clone and git push Best El 14 de diciembre de 2011 10:44, Takaaki ISHIKAWA tak...@ieee.org escribió: Dear all and David, Sorry I sent an incomplete mail, it's my mistake. please ignore the previous e-mail. David Near future, I'll contribute a Japanese translation. Could you setup the libremanual ikiwiki for Japanese? signature.asc Description: Message signed with OpenPGP using GPGMail
[O] Defining new structural markup element
Hi, I'm a relative org newbie and I expect that this question is answered somewhere in the manual, but I've searched and I can't find the answer. I would like to define a new structural markup element for an org file and specify its translation into latex. e.g., I'd like to be able to put in my document #+begin_foo bar #+end_foo and have this translated into LaTeX as something like \em bar \em but I'd like to be able to flexibly specify the LaTeX commands inserted at the beginning and end of the foo block. Is there an easy way to do this? Best many thanks in advance! Roger
[O] ODT export custom link colors?
I use custom links like [[bgcolor:red][Warning!]] to add some color to my
documents. I can export those colors to HTML and LaTeX like this:
(org-add-link-type
bgcolor nil
(lambda (path desc format)
(cond
((eq format 'html)
(formatspan style=\background-color:%s;\%s/span path desc))
((eq format 'latex)
(format\\colorbox{%s}{%s} path desc))
(t
(formatBGCOLOR LINK (%s): {%s}{%s} format path desc)
... but as you can see in the odt case I don't know what to put to get my
colors to come through. Is there anything I can do there? Is it some kind
of XML styling stanza?
(By the way, before I added my 't' case above, it returned nil, which
caused the odt exporter to blow up with an unhelpful error. Would a patch
for that be considered too much of a corner-case? I'd be happy to submit
one.)
--
-- Gary
Re: [O] [bug] Commit 6f8ea8e breaks the build
Jambunathan K kjambunat...@gmail.com writes: I pushed one more fix which does a (require 'htmlfontify nil t) instead of (require 'htmlfontify). Requiring htmlfontify seems to spawn a shell while byte-compiling (I've not looked further into why it would do this). That makes is a bit difficult to set up correctly when cross-compiling from a Cygwin make with an NTemacs -- SHELL is having a Cygwin/UNIX path, and NTemacs then does not understand how to start the shell. I've managed to get around this by modifying the SHELL variable before starting NTemacs from make, but it's not something very obvious to do. Do you really require the package to be loaded (i.e. actually run compile-time macros from htmlfontify) or do you just need to have the functions and variables declared? If the latter, please consider removing the rquire statement and replacing with the appropriate declarations. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] Defining new structural markup element
Levy, Roger rl...@ucsd.edu wrote:
Hi,
I'm a relative org newbie and I expect that this question is answered somew=
here in the manual, but I've searched and I can't find the answer.
I would like to define a new structural markup element for an org file and =
specify its translation into latex. e.g., I'd like to be able to put in my=
document
#+begin_foo
bar
#+end_foo
and have this translated into LaTeX as something like=20
\em
bar
\em
but I'd like to be able to flexibly specify the LaTeX commands inserted at =
the beginning and end of the foo block. Is there an easy way to do this?
Not sure I understand completely what you are trying to do, but you can
do something like this:
--8---cut here---start-8---
* foo
#+LATEX: \begin{foo}
bar
#+LATEX: \end{foo}
--8---cut here---end---8---
to insert arbitrary LaTeX markup at the indicated places when exporting
to latex. Other exporters will just omit the markup.
Nick
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Nick Dokos nicholas.do...@hp.com writes: Christian Moe m...@christianmoe.com wrote: Of course, getting libreoffice to do what I want is another story... ;-) I imagine I'll have to use a mouse :-( Well, you can always author your own styles file in plain XML conforming to the ODF specification. No mouse required!... ;-) ... or write an elisp function to snag the XML style file from wherever libreoffice squirrels it into emacs, where you can edit it - testing might be a bit more painful though... Ahh, two challenges; just what I need for the xmas break... ;-) If I get really really bored, maybe an org - xml exporter with pre-defined templates for ODT styles... No, I don't think I'll get that bored! -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.02 (release_7.8.02.2.g490d6a)
Re: [O] http://libremanuals.net (ikiwiki+org) to translate the Org Guide
On Tue, 13 Dec 2011 20:48:57 +0100, Bastien b...@altern.org wrote: Dear all, another announcement about translation : David Arroyo Menéndez (who already translated David O'Toole's tutorial) is launching LibreManuals to help with translating/publishing FLOSS book. Libremanuals uses ikiwiki (http://ikiwiki.info/) a wiki compiler. It builds static HTML pages for a wiki, from source in the ikiwiki/Markdown language (or others, such as texinfo or org-mode), and writes it out to destination. Libremanuals is using org-mode files to manage the tasks to do in an integrated way with ikiwiki thanks to the org ikiwiki plugin http://www.golden-gryphon.com/software/misc/org.pm.html Hi Bastien, You might have seen this already, but I recently announced a different approach to compiling org files with ikiwiki. It isn't exactly stable yet, but you might want to keep an eye on https://github.com/chrismgray/ikiwiki-org-plugin. It currently has features that Manoj's plugin does not have, such as properly setting the title of the page, and allowing images (currently only absolute urls are tested, but that should be improved soon) and wikilinks. Anyway, I think you are probably making the right decision in using Manoj's plugin for now, but mine is being more actively developed, so it might be the better choice fairly soon. Cheers, Chris
Re: [O] Defining new structural markup element
Hi, the Worg page on LaTeX publishing covers this under Block-level Markup and Inline Markup: http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-2 http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-3 Haven't tried it myself so far (but planning to do so). Cheers, Viktor Levy, Roger wrote: Hi, I'm a relative org newbie and I expect that this question is answered somewhere in the manual, but I've searched and I can't find the answer. I would like to define a new structural markup element for an org file and specify its translation into latex. e.g., I'd like to be able to put in my document #+begin_foo bar #+end_foo and have this translated into LaTeX as something like \em bar \em but I'd like to be able to flexibly specify the LaTeX commands inserted at the beginning and end of the foo block. Is there an easy way to do this? Best many thanks in advance! Roger
Re: [O] Bastiens talk
Hi Rustom, Rustom Mody rustompm...@gmail.com writes: I was wondering if there is any brief index into the talk? [I thought I saw something yesterday but cant seem to find it today :-) ] Not sure what you mean by index -- some timeline with timecodes and related topics? -- Bastien
Re: [O] Refresh of http://orgmode.org
Hi all, Old School Org screenshots are back in orgmode.org. Enjoy! -- Bastien
[O] [PATCH] * doc/org.texi (Agenda commands): Document org-clock-report-include-clocking-task
Add reference to this variable when describing the agenda clock report.
---
Here's the documentation patch. I won't be offended if you decide not
to apply it since we don't document every customizable variable in
org-mode.
Regards,
Bernt
doc/org.texi |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 93c8c5a..04fa199 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -7969,6 +7969,7 @@ press @kbd{v a} again.
@c
@orgcmdkskc{v R,R,org-agenda-clockreport-mode}
@vindex org-agenda-start-with-clockreport-mode
+@vindex org-clock-report-include-clocking-task
Toggle Clockreport mode. In Clockreport mode, the daily/weekly agenda will
always show a table with the clocked times for the timespan and file scope
covered by the current agenda view. The initial setting for this mode in new
@@ -7976,7 +7977,8 @@ agenda buffers can be set with the variable
@code{org-agenda-start-with-clockreport-mode}. By using a prefix argument
when toggling this mode (i.e.@: @kbd{C-u R}), the clock table will not show
contributions from entries that are hidden by agenda filtering@footnote{Only
-tags filtering will be respected here, effort filtering is ignored.}.
+tags filtering will be respected here, effort filtering is ignored.}. See
+also the variable @code{org-clock-report-include-clocking-task}.
@c
@orgkey{v c}
@vindex org-agenda-clock-consistency-checks
--
1.7.8
Re: [O] [PATCH] * doc/org.texi (Agenda commands): Document org-clock-report-include-clocking-task
Bernt Hansen be...@norang.ca writes: Add reference to this variable when describing the agenda clock report. Applied, thanks. Here's the documentation patch. I won't be offended if you decide not to apply it since we don't document every customizable variable in org-mode. I think this one is important. Thanks, -- Bastien
Re: [O] Refresh of http://orgmode.org
Viktor Rosenfeld listuse...@googlemail.com writes: Can you make an alternate .css with non-fixed top bar and a better font? Maybe on the weekend, but I can't promise anything. Thanks in advance for this! -- Bastien
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Just wanted to say the latest version is working perfectly for me -- well done! ODT export is fine and LaTeX is still working too (some things have changed recently that made me have to change some of my code *around* org-mode, but that's as expected.) -- -- Gary
Re: [O] Defining new structural markup element
Thanks so much, Viktor, this is exactly what I wanted! Best Roger On Dec 14, 2011, at 1:08 PM EST, Viktor Rosenfeld wrote: Hi, the Worg page on LaTeX publishing covers this under Block-level Markup and Inline Markup: http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-2 http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-3 Haven't tried it myself so far (but planning to do so). Cheers, Viktor Levy, Roger wrote: Hi, I'm a relative org newbie and I expect that this question is answered somewhere in the manual, but I've searched and I can't find the answer. I would like to define a new structural markup element for an org file and specify its translation into latex. e.g., I'd like to be able to put in my document #+begin_foo bar #+end_foo and have this translated into LaTeX as something like \em bar \em but I'd like to be able to flexibly specify the LaTeX commands inserted at the beginning and end of the foo block. Is there an easy way to do this? Best many thanks in advance! Roger -- Roger Levy Email: rl...@ucsd.edu Assistant Professor Phone: 858-534-7219 Department of Linguistics Fax: 858-534-4789 UC San DiegoWeb: http://idiom.ucsd.edu/~rlevy
Re: [O] Refresh of http://orgmode.org
+1 for preferring the old screenshot, for exactly those reasons mentioned above. While it is fun for me to look at random screenshots from Worg, part of the purpose of this site is as a gateway to Org-mode, and I fear many of these random screenshots are meaningless (or even intimidating) unless you already have a good understanding of Org-mode. Again, I agree. Patch welcome! Ah, I should have known to hold my tongue! :) I pushed a patch up to a new old-image branch in the orgweb repository, but it seems you've now taken care of this independently so please feel free to delete that branch. - I don't like the fixed top bar with the Org-Mode motto and the random quote. It takes up about 20% of vertical screen space of my laptop. A complete waste in my view. The black background also does not cover the text behind it -- one or two pixel of the text are visible above the bar. I also find that (in part because of the new larger screenshots) I can't see any content upon first loading the page (see this screenshot [1]). Mh.. your screen seems quite small. If you can fix the .css to display the website better on your screen, please do, I don't have time at hand now to do it myself. One of my preferred layout looks something like the following, which can lead to a small windows for Firefox. ++---+ || | || | | Firefox | Emacs | || | || | ++---+ | Terminal | ++ There is a huge difference in readability between those websites which take variable window size into consideration and those which assume a large screen (or a full screen browser). I'll take a shot at changing the CSS in the orgweb repository to facility smaller layouts (I guess some special CSS for mobile browsers may also make sense). ...looking... It looks like making the Org-mode website responsive to the viewers window size should be as simple as adding a couple of @media guards [1] to the css page. I may have time to tackle this over the weekend. I do need some help compiling the Org-mode web page from the git repository. Is there an org-mode publishing project which I should define locally? In general how are the many file in orgweb compiled into the site? Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte/ Footnotes: [1] http://www.w3.org/TR/css3-mediaqueries/
Re: [O] ODT export custom link colors?
Hi,
I'm not sure about this, because I don't really know the ODT spec, but
I *think* you will have to define an ODT Character style for *each*
color you want to use, using a consistent convention for naming these
styles.
For instance, in the LibreOffice Styles and Formatting window, choose
the Character styles tab, right-click on Default, select New. Name
your style (e.g.) Bgcolor red. Right-click it, select Modify, in the
Background tab give it a red background.
Repeat for other colors you use, e.g. Bgcolor blue, Bgcolor yellow...
Now, modify your custom link code as follows:
(org-add-link-type
bgcolor nil
(lambda (path desc format)
(cond
((eq format 'html)
(formatspan style=\background-color:%s;\%s/span path desc))
((eq format 'latex)
(format\\colorbox{%s}{%s} path desc))
((eq format 'odt)
(format text:span text:style-name=\Bgcolor
%s\%s/text:span path desc))
(t
(formatBGCOLOR LINK (%s): {%s}{%s} format path desc)
(You can change the style-name in the format string to follow whatever
naming convention you've adopted for your styles. If you want to call
them simply red, blue and so on, it would be text:style-name=\%s\.)
(Judging from the manual, if you have space in your style names, like
above, you should perhaps escape the spaces with _20_, but the
Bgcolor %s above seems to work fine.)
Please report back if this works for you. If so, and depending on what
Jambunathan might have to add, I'll look into updating the Worg examples.
(By the way, before I added my 't' case above, it returned nil, which
caused the odt exporter to blow up with an unhelpful error. Would a
patch for that be considered too much of a corner-case? I'd be happy
to submit one.)
I don't know what others think, but I think the habit of always
providing one's custom links with an explicit fallback should be
encouraged, if necessary by rude reminders from failing exporters...
:-)
hth,
Christian
[O] sort strategy within org-agenda-custom-commands
Hey, I have a few items in org-agenda-custom-commands that call org-agenda-sorting-strategy. For example: (f Phone Calls tags +@PHONE/-DONE ((org-agenda-sorting-strategy '(time-up (E E-mail tags +@EMAIL/-DONE ((org-agenda-sorting-strategy '(time-up Yet when I run the agenda for these (e.g., C-a f), the result appears to be sorted by the (standard) value of org-agenda-sorting-strategy [which is: ((agenda habit-down time-up priority-down category-keep) (todo priority-down category-keep) (tags priority-down category-keep) (search category-keep)) ] I need help with this, and I don't know what to do next to diagnose the problem. Is there some variable I've set that has overridden this feature of setting a special sorting strategy in these custom commands? Thanks, Dan -- Dan Griswold Rochester, NY dgris...@rochester.rr.com
[O] centering blocks cause latex export to crash
I am using the latest org from git. The attached org-mode file causes latex export to crash with an error of unbalanced begin/end center blocks with This did work, as recently as a month ago, so something relatively recent has broken it. best, r #+TITLE: center-export-bug.org #+AUTHOR:Robert P. Goldman #+EMAIL: rpgold...@sift.info #+DATE: 2011-12-14 Wed #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: #+TAGS: noexport #+begin_center Not Cleared for Public Release #+end_center * Problem with centering block. My document fails to export successfully to latex with the above =center= block in it.
Re: [O] centering blocks cause latex export to crash
Robert Goldman rpgold...@sift.info wrote: I am using the latest org from git. The attached org-mode file causes latex export to crash with an error of unbalanced begin/end center blocks with This did work, as recently as a month ago, so something relatively recent has broken it. best, r Indeed, but note that the latex exporter has always been a little flaky with stuff before the first headline. As a workaround, if you add a headline before the block, it works. Nick
Re: [O] reftex setup problem
Nikolai,
I'm guessing, but you could try finding the .aux file, run bibtex on it
then try the latex export again.
Myles
On Wed, 14 Dec 2011 14:28:01 +0100, nikolai stenfors said:
Hi, Problems incorporating references/citations in .org-files.
I have set up a refs.bib-file for my references using jabref 2.6.
In org-mode 7.7 I have used the suggestion in FAQ for Marios reftex
setup in my .emacs:
(defun org-mode-reftex-setup () (load-library reftex) (and
(buffer-file-name) (file-exists-p (buffer-file-name))
(reftex-parse-all)) (define-key org-mode-map (kbd C-c ))
'reftex-citation)) (add-hook 'org-mode-hook 'org-mode-reftex-setup)
In my .org-file I put the path to my refs.bib-file:
\bibliography{/home/nikolai/Dokument/Artiklar/refs}
When I use the Cc) in my .org-file I get: Regex { Regex...}: in
the minibuffer
Trying to type the bibtexkey in the minibuffer it finds no match.
If I manually enter:
\cite{Bursi2010}
and export I get:
LaTeX Warning: Citation `Bursi2010' on page 1 undefined on input
line 33. LaTeX Warning: There were undefined references.
Where is the problem hidden? bibtex-file, reftex setup, org-mode,
or emacs?
Nikolai
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Bastien b...@altern.org writes: as the subject says. Please all test this heavily and report any problems. This will be part of Org 7.8 and soon in Emacs. Thanks a lot to Jambunathan for all this efforts, let's make sure everything is smooth before the release! I installed Org 7.8.02 by downloading the tarball, untarring it, running make, then make install install-info. When I run org-export-as-odt by C-c C-e o, I get this message: Cannot find factory styles file. Check package dir layout Setting debug-on-error, I get this traceback. Debugger entered--Lisp error: (error Cannot find factory styles file. Check package dir layout) signal(error (Cannot find factory styles file. Check package dir layout)) error(Cannot find factory styles file. Check package dir layout) byte-code(ÄÅ\ÄÆ\ÃÇ
Re: [O] centering blocks cause latex export to crash
On 12/14/11 Dec 14 -3:06 PM, Robert Goldman wrote: I am using the latest org from git. The attached org-mode file causes latex export to crash with an error of unbalanced begin/end center blocks with This did work, as recently as a month ago, so something relatively recent has broken it. I got in the debugger, and the problem is that the regular expression for the end of the centering block, computed as inner-re in org-export-blocks-preprocess fails to match my #+end_center inner-re is: (inner-re (format [\r\n][ \t]*#\\+\\(begin\\|end\\)_%s (regexp-quote (downcase (match-string 2) I don't understand why this is happening: I haven't been able to tell if the regular expression is incorrectly written, so it fails to find the ending of the center block, or if somehow the logic in the while loop (which counts begins and ends to make sure they match) is counting wrong. Cheers, r
[O] file name prefix in agenda view
Hello. Is it possible to turn of file prefix (file:) in agenda view? I use the only one file for agenda and don't plan to use more than one. -- sergio.
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
On Wed, Dec 14, 2011 at 21:28, Dave Marquardt davem...@us.ibm.com wrote: When I run org-export-as-odt by C-c C-e o, I get this message: Cannot find factory styles file. I believe this is fixed in the git head. -- Suvayu Open source is the future. It sets us free.
Re: [O] centering blocks cause latex export to crash
On 12/14/11 Dec 14 -3:13 PM, Nick Dokos wrote: Robert Goldman rpgold...@sift.info wrote: I am using the latest org from git. The attached org-mode file causes latex export to crash with an error of unbalanced begin/end center blocks with This did work, as recently as a month ago, so something relatively recent has broken it. best, r Indeed, but note that the latex exporter has always been a little flaky with stuff before the first headline. As a workaround, if you add a headline before the block, it works. Nick Thanks. But the workaround is not ideal here --- the centering block is supposed to say Not Cleared for Public Release for reasons of conditions on my research grant, and that really is not supposed to be in a heading. I have another work-around, but I think the general principle is that forbidding text before the first header is not an ideal constraint. If there's a way to have a header that doesn't produce output (a la noexport), but that doesn't suppress its children, that might be a handy way to accomplish this. I don't know if that's possible (that would also be handy for outlines where you want the outline structure to fade away and just leave you with the text that the outline inspired). Best, r
[O] Org-drill doesn't work...
hi all, i'm trying to set up org-drill for learning some russian vocabulary, but i'm not very successful... i've created an org file that meets the requirements of a proper org-drill file. i have a bunch of entries that look like this: #+BEGIN_EXAMPLE ** Nomen :drill: :PROPERTIES: :DRILL_CARD_TYPE: twosided :ID: 9927d8c4-1692-4784-9afc-9e4a770a62c8 :END: *** Deutsch Herbst *** Russisch о́сень (f) *** Beispiele im *Herbst* о́сенью nächsten *Herbst* сле́дующей *о́сенью* letzten *Herbst* про́шлой о́сенью #+END_EXAMPLE of course, the ID was added by org-drill, not by me. after creating the file, the first run of org-drill seemed to be fine. i was prompted for a couple of items, maybe five or so, and after i had finished, emacs told me the results. however, trying to run org-drill the next day, i got the following message: #+BEGIN_EXAMPLE 0 items reviewed. Session duration 0:00:00. Recall of reviewed items: Excellent (5): 0% | Near miss (2):0% Good (4):0% | Failure (1): 0% Hard (3):0% | Abject failure (0): 0% You successfully recalled 0% of reviewed items (quality 2) 0/1 items still await review (0 failed, 0 overdue, 0 new, 0 young, 0 old). Tomorrow, 0 more items will become due for review. Session finished. Press a key to continue... #+END_EXAMPLE i wasn't prompted for any new items and the message tomorrow, 0 more items will become due for review worries me. also, running org-drill-again gives me the same message. i'm sure i'm doing something wrong, but i can't figure out what... would appriciate any help pointing me in the right direction. Org-mode version 7.8.02 (and org-drill included with it), GNU Emacs 23.3.1. TIA Joost btw, i noticed that some of the customize items in org-drill.el are incorrectly defined. for example, the :type declaration in org-drill-spaced-repetition-algorithm is: :type '(choice (const 'sm2) (const 'sm5) (const 'simple8)) but the symbols shouldn't be quoted: :type '(choice (const sm2) (const sm5) (const simple8)) there are one or two more cases like this. they're labelled in the customize buffer as MISMATCH. -- Dr. Joost Kremers Georg-August-Universität Seminar für Deutsche Philologie Käte-Hamburger-Weg 3 D-37073 Göttingen
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
On 15/12/11 08:35:20, suvayu ali wrote: On Wed, Dec 14, 2011 at 21:28, Dave Marquardt davem...@us.ibm.com wrote: When I run org-export-as-odt by C-c C-e o, I get this message: Cannot find factory styles file. I believe this is fixed in the git head. I'm not so sure. I just pulled the latest and get the same error message: Debian Squeeze, emacs 23.2.1, LibreOffice 3.4.3. Alan -- Suvayu Open source is the future. It sets us free. -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: [O] Refresh of http://orgmode.org
Hi, Bastien wrote: Viktor Rosenfeld listuse...@googlemail.com writes: Can you make an alternate .css with non-fixed top bar and a better font? Maybe on the weekend, but I can't promise anything. Thanks in advance for this! What's the git URL of the homepage repository? Thanks, Viktor
Re: [O] centering blocks cause latex export to crash
Robert Goldman rpgold...@sift.info wrote:
Thanks. But the workaround is not ideal here --- the centering block is
supposed to say Not Cleared for Public Release for reasons of
conditions on my research grant, and that really is not supposed to be
in a heading.
Can it be in a watermark? Something like this perhaps:
#+LATEX_HEADER: \usepackage{draftwatermark}
#+LATEX_HEADER: \SetWatermarkText{Not Cleared for Public Release}
#+LATEX_HEADER: \SetWatermarkFontSize{42pt}
I have another work-around, but I think the general principle is that
forbidding text before the first header is not an ideal constraint. If
there's a way to have a header that doesn't produce output (a la
noexport), but that doesn't suppress its children, that might be a handy
way to accomplish this. I don't know if that's possible (that would
also be handy for outlines where you want the outline structure to fade
away and just leave you with the text that the outline inspired).
Agreeed - I believe it's a long standing weakness in the implementation
of the exporter and I also believe we'll see a reimplementation (soon?)
based on Nicolas's parser. BTW, I wonder what the parser says about text
before the first headline.
Nick
Re: [O] Refresh of http://orgmode.org
What's the git URL of the homepage repository? git clone git://orgmode.org/orgweb.git -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] http://libremanuals.net (ikiwiki+org) to translate the Org Guide
El 14 de diciembre de 2011 19:07, Chris Gray chrismg...@gmail.comescribió: On Tue, 13 Dec 2011 20:48:57 +0100, Bastien b...@altern.org wrote: Dear all, another announcement about translation : David Arroyo Menéndez (who already translated David O'Toole's tutorial) is launching LibreManuals to help with translating/publishing FLOSS book. Libremanuals uses ikiwiki (http://ikiwiki.info/) a wiki compiler. It builds static HTML pages for a wiki, from source in the ikiwiki/Markdown language (or others, such as texinfo or org-mode), and writes it out to destination. Libremanuals is using org-mode files to manage the tasks to do in an integrated way with ikiwiki thanks to the org ikiwiki plugin http://www.golden-gryphon.com/software/misc/org.pm.html Hi Bastien, You might have seen this already, but I recently announced a different approach to compiling org files with ikiwiki. It isn't exactly stable yet, but you might want to keep an eye on https://github.com/chrismgray/ikiwiki-org-plugin. It currently has features that Manoj's plugin does not have, such as properly setting the title of the page, and allowing images (currently only absolute urls are tested, but that should be improved soon) and wikilinks. Anyway, I think you are probably making the right decision in using Manoj's plugin for now, but mine is being more actively developed, so it might be the better choice fairly soon. Cheers, Chris Thanks for the work. It sounds interesting. Now, I'm watching the project. -- David Arroyo Menéndez http://www.davidam.com
[O] [babel] PROPERTY doesn't do what BABEL did
I would like to get the same behavior as when I export a file with (say) these three lines: #+begin_src emacs-lisp :var foo=1 :var bar=2 :results value :exports both (+ foo bar) #+end_src But I'd like to set a buffer wide PROPERTY to achieve that as with a file with these lines: #+property: var foo=1 #+property: var+ bar=2 #+begin_src emacs-lisp :results value :exports both (+ foo bar) #+end_src it throws an error under 7.8.02 (downloaded as tar.gz) when I try to export it with 'C-c C-e a yes RET' : progn: Symbol's value as variable is void: foo Other trials seem to show that #+PROPERTY: is ignored by the src blocks I'd really like to get something that does what BABEL used to do as I have a lot of code that relies on that behavior. :-( Chuck ---
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Hi Alan and Dave, On Wed, Dec 14, 2011 at 22:56, Alan L Tyree alanty...@gmail.com wrote: On 15/12/11 08:35:20, suvayu ali wrote: On Wed, Dec 14, 2011 at 21:28, Dave Marquardt davem...@us.ibm.com wrote: When I run org-export-as-odt by C-c C-e o, I get this message: Cannot find factory styles file. I believe this is fixed in the git head. I'm not so sure. I just pulled the latest and get the same error message: Debian Squeeze, emacs 23.2.1, LibreOffice 3.4.3. I was mistaken in saying it has been fixed. Its actually a setup problem reported originally by Christian. Take a look at the following thread. http://thread.gmane.org/gmane.emacs.orgmode/49846/focus=50001 In case you still think its a bug causing the issue in your case, it would be help if you could post an ECM (minimal complete example in French) which replicates the problem. -- Suvayu Open source is the future. It sets us free.
Re: [O] ePub construction
Hi Alan, On Tue, Dec 13, 2011 at 23:45, Alan L Tyree alanty...@gmail.com wrote: I will be happy to add a fuller description to worg if someone will point me to some instructions. Here is the latest announcement from Jason: http://thread.gmane.org/gmane.emacs.orgmode/49704 -- Suvayu Open source is the future. It sets us free.
Re: [O] ePub construction
On 15/12/11 10:24:16, suvayu ali wrote: Hi Alan, On Tue, Dec 13, 2011 at 23:45, Alan L Tyree alanty...@gmail.com wrote: I will be happy to add a fuller description to worg if someone will point me to some instructions. Here is the latest announcement from Jason: http://thread.gmane.org/gmane.emacs.orgmode/49704 Thanks for that - I had seen the thread but didn't recognise its significance. Duh! Alan -- Suvayu Open source is the future. It sets us free. -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
On 15/12/11 10:20:44, suvayu ali wrote: Hi Alan and Dave, On Wed, Dec 14, 2011 at 22:56, Alan L Tyree alanty...@gmail.com wrote: On 15/12/11 08:35:20, suvayu ali wrote: On Wed, Dec 14, 2011 at 21:28, Dave Marquardt davem...@us.ibm.com wrote: When I run org-export-as-odt by C-c C-e o, I get this message: Cannot find factory styles file. I believe this is fixed in the git head. I'm not so sure. I just pulled the latest and get the same error message: Debian Squeeze, emacs 23.2.1, LibreOffice 3.4.3. I was mistaken in saying it has been fixed. Its actually a setup problem reported originally by Christian. Take a look at the following thread. http://thread.gmane.org/gmane.emacs.orgmode/49846/focus=50001 In case you still think its a bug causing the issue in your case, it would be help if you could post an ECM (minimal complete example in French) which replicates the problem. That solved the problem. I was loading an old version. This makes me feel stupid enough to go back to MS Word. Well, maybe not THAT stupid! Thanks, Alan -- Suvayu Open source is the future. It sets us free. -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
[O] Org website for Japanese
Dear all, I'm pleased to announce that Japanese translated Org website has been opened. http://orgmode.org/ja/ Thanks Bastien! It's done with your great help. And I'd like to say thanks to a Japanese translation team that I organized. Best regards, Takaaki Ishikawa @takaxp signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] [babel] PROPERTY doesn't do what BABEL did
cbe...@tajo.ucsd.edu writes: I would like to get the same behavior as when I export a file with (say) these three lines: #+begin_src emacs-lisp :var foo=1 :var bar=2 :results value :exports both (+ foo bar) #+end_src But I'd like to set a buffer wide PROPERTY to achieve that as with a file with these lines: #+property: var foo=1 #+property: var+ bar=2 #+begin_src emacs-lisp :results value :exports both (+ foo bar) #+end_src The above works on my system. You may want to try C-c C-c on one of the property lines so that Org-mode re-reads them (it does this automatically upon opening an Org-mode file). Best, it throws an error under 7.8.02 (downloaded as tar.gz) when I try to export it with 'C-c C-e a yes RET' : progn: Symbol's value as variable is void: foo Other trials seem to show that #+PROPERTY: is ignored by the src blocks I'd really like to get something that does what BABEL used to do as I have a lot of code that relies on that behavior. :-( Chuck --- -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] Possibly Bug in function org-scan-tags
Hi, The variable org-map-continue-from is not reset to nil after the funcall to action in function org-scan-tags. Heres the patch which works diff --git a/lisp/org.el b/lisp/org.el index 8a1fbd3..54ab5fb 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -12848,7 +12848,8 @@ only lines with a TODO keyword are included in the output. (setq org-map-continue-from nil) (save-excursion (setq rtn1 (funcall action)) - (push rtn1 rtn))) + (push rtn1 rtn)) + (setq org-map-continue-from nil)) (t (error Invalid action))) ;; if we are to skip sublevels, jump to end of subtree To see the error in action assume that we want to archive all the DONE states in the file /tmp/test.org which contains the following lines. * s1 ** DONE ss1 ** NEXT ss2 (defun my-org-archive-subtree () (setq org-map-continue-from (point-at-bol)) (org-archive-subtree)) (org-map-entries 'my-org-archive-subtree /DONE (list /tmp/test.org)) While the org-scan-tags funciton parses the first subheading(**DONE ss1) the match is successful and the function my-org-archive-subtree is called which sets the variable org-map-continue-from value to *beginning of line* and this variable is not set back to nil after the function call ends, which leads to infinite loop while parsing the subsequent headlines which does not match the DONE state(**NEXT ss2). Regards, Balamayam
[O] [BUG] org-agenda-switch-to fails with void function org-pop-to-buffer-same-window
Recently did a fresh pull, which seems to have broken org-agenda-switch-to. To reproduce, open an agenda buffer, navigate to a line you want to inspect, press [RET]. On my machine, this calls autopair, then falls back to org-agenda-switch-to. Autopair doesn't seem to be causing the problem, since it persists even if I call =M-x org-agenda-switch-to= instead of pressing [RET]. Org-mode version 7.8.02 (release_7.8.02.3.gfb8c) GNU Emacs 24.0.90.3 (i386-apple-darwin9.8.0, NS apple-appkit-949.54) of 2011-12-14 on braeburn.aquamacs.org - Aquamacs Distribution 3.xdev Can anyone reproduce? ,[ Full Backtrace ] | Debugger entered--Lisp error: (void-function | org-pop-to-buffer-same-window) (org-pop-to-buffer-same-window | buffer) (let* ((marker (or (org-get-at-bol (quote org-marker)) | (org-agenda-error))) (buffer (marker-buffer marker)) (pos | (marker-position marker))) (org-pop-to-buffer-same-window buffer) | (and delete-other-windows (delete-other-windows)) (widen) (goto-char | pos) (when (eq major-mode (quote org-mode)) (org-show-context (quote | agenda)) (save-excursion (and (outline-next-heading) | (org-flag-heading nil))) (when (outline-invisible-p) (show-entry | (if (and org-return-follows-link (not (org-get-at-bol (quote | org-marker))) (org-in-regexp org-bracket-link-regexp)) | (org-open-link-from-string (match-string 0)) (let* ((marker (or | (org-get-at-bol (quote org-marker)) (org-agenda-error))) (buffer | (marker-buffer marker)) (pos (marker-position marker))) | (org-pop-to-buffer-same-window buffer) (and delete-other-windows | (delete-other-windows)) (widen) (goto-char pos) (when (eq major-mode | (quote org-mode)) (org-show-context (quote agenda)) (save-excursion | (and (outline-next-heading) (org-flag-heading nil))) (when | (outline-invisible-p) (show-entry) org-agenda-switch-to() | call-interactively(org-agenda-switch-to) (let ((cua-delete-selection | (not autopair-autowrap)) (blink-matching-paren (not | autopair-action))) (call-interactively beyond-autopair)) (let* | ((autopair-emulation-alist nil) (beyond-cua (let ((cua--keymap-alist | nil)) (autopair-original-binding))) (beyond-autopair | (autopair-original-binding))) (when autopair-autowrap (setq | autopair-wrap-action (autopair-calculate-wrap-action))) (setq | this-original-command beyond-cua) (when (and (featurep (quote | paredit)) (string-match paredit (symbol-name beyond-cua))) (setq | autopair-action nil)) (let ((cua-delete-selection (not | autopair-autowrap)) (blink-matching-paren (not autopair-action))) | (call-interactively beyond-autopair))) autopair-fallback( ) (let | ((pair (autopair-find-pair (char-before (when (and pair (eq | (char-syntax pair) 41) (eq (char-after) pair)) (setq autopair-action | (list (quote newline) pair (point (autopair-fallback (kbd | RET))) autopair-newline() call-interactively(autopair-newline nil | nil) ` -- Jeffrey Horn http://www.failuretorefrain.com/jeff/
Re: [O] [bug] Org link dialog escapes URL spaces incorrectly
On Sun, Nov 13, 2011 at 12:32, Nick Dokos nicholas.do...@hp.com wrote: Good enough for me. I don't remember whether you supplied a patch for this (sorry, no time to check atm) but if you did, maybe the OP can test it and make sure that it does what he expected (or maybe he's done that already - I can't remember and I'm completely discombobulated right now, even more than usual). I was sorry to hear about your family emergency. I hope you are feeling better. I just tried with the latest source, and the problem still exists for me. Org-mode version 7.8.02 (release_7.8.02.3.gfb8c) GNU Emacs 24.0.90.3 (i386-apple-darwin9.8.0, NS apple-appkit-949.54) of 2011-12-14 on braeburn.aquamacs.org - Aquamacs Distribution 3.xdev -- Jeffrey Horn http://www.failuretorefrain.com/jeff/
Re: [O] Org website for Japanese
Takaaki ISHIKAWA tak...@ieee.org writes: Dear all, I'm pleased to announce that Japanese translated Org website has been opened. http://orgmode.org/ja/ This looks cool. Thank you Ishikawa-san. Now I can recommend org to my friends. Thanks Bastien! It's done with your great help. And I'd like to say thanks to a Japanese translation team that I organized. Best regards, Takaaki Ishikawa @takaxp -- YYR
Re: [O] [PATCH] * doc/org.texi (Agenda commands): Document org-clock-report-include-clocking-task
Bastien b...@altern.org writes: Bernt Hansen be...@norang.ca writes: Add reference to this variable when describing the agenda clock report. Applied, thanks. Thanks - I think... I'm not sure what happened to my subject line on that patch but I obviously blew that badly :( Too late now... Regards, Bernt
Re: [O] Bastiens talk
On Wed, Dec 14, 2011 at 11:08 PM, Bastien b...@altern.org wrote: Hi Rustom, Rustom Mody rustompm...@gmail.com writes: I was wondering if there is any brief index into the talk? [I thought I saw something yesterday but cant seem to find it today :-) ] Not sure what you mean by index -- some timeline with timecodes and related topics? Yeah yeah... I remember seeing something like that a day ago -- just 3-4 lines -- Bastien
Re: [O] Refresh of http://orgmode.org
Mh.. your screen seems quite small. If you can fix the .css to display
the website better on your screen, please do, I don't have time at hand
now to do it myself.
The attached three patches to the orgweb repository change the CSS for
smarter rendering on narrow screens (they don't address screen height).
The changes include...
- scale down images on narrow screens
- decrease the width of the left link bar on narrow screens
- decrease the padding around the title on narrow screens
- shrink the paypal link on smaller screens -- I would like to move this
button on really small screens, but somehow that doesn't seem possible
- remove the Org-mode image on really small screens
- remove the twitter feed on narrow screens -- for some reason I was
unable to change the size of this widget, so I just hide it on a tiny
screen
These changes make the new website work on my system, and should improve
the reading experience for everyone who keeps their browser screens less
than 1400 pixels wide.
If these look good please apply them.
Thanks,
From 9bb86f8c206e2b749c9c49c4ad33f11e07e4f3fc Mon Sep 17 00:00:00 2001
From: Eric Schulte eric.schu...@gmx.com
Date: Wed, 14 Dec 2011 20:30:02 -0700
Subject: [PATCH 1/3] ignoring exported html indices
---
.gitignore |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
create mode 100644 .gitignore
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000..dcaf716
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+index.html
--
1.7.8
From e262903d6d21173d786c15d4e4db155d466c8407 Mon Sep 17 00:00:00 2001
From: Eric Schulte eric.schu...@gmx.com
Date: Wed, 14 Dec 2011 20:30:28 -0700
Subject: [PATCH 2/3] shrink links and remove twitter on narrow screens
---
org.css | 147 +++
1 files changed, 82 insertions(+), 65 deletions(-)
diff --git a/org.css b/org.css
index cce24dd..ad6785e 100644
--- a/org.css
+++ b/org.css
@@ -96,50 +96,87 @@ h1.title {
font-family: Courier New;
}
-#linklist
-{
-position: fixed;
-font-size: 13pt;
-font-family: Courier New;
-padding-top: 0px;
-padding-right: 0px;
-top: 107px;
-left: 0px;
-margin-top: 0px;
-width: 180px;
-background-color: #fff;
-color: black;
-box-shadow: 8px 8px 12px #ccc;
--webkit-border-bottom-right-radius: 10px;
--moz-border-radius-bottomright: 10px;
-z-index: 100;
-}
-
-#linklist a {
-color: black;
-font-weight: normal;
-text-decoration: none;
-display:block;
-padding: 7pt;
-}
-
-#linklist ul {
-margin: 0;
-padding: 0;
-}
-
-#linklist li {
-text-align: right;
-margin: 0;
-}
-
-.timestamp {
-font-family: Courier New;
-color: #88;
-}
-
-#linklist li:hover {
-border-left: 7px solid #537d7b;
+@media all {
+#linklist
+{
+position: fixed;
+font-size: 13pt;
+font-family: Courier New;
+padding-top: 0px;
+padding-right: 0px;
+top: 107px;
+left: 0px;
+margin-top: 0px;
+width: 180px;
+background-color: #fff;
+color: black;
+box-shadow: 8px 8px 12px #ccc;
+-webkit-border-bottom-right-radius: 10px;
+-moz-border-radius-bottomright: 10px;
+z-index: 100;
+}
+
+#linklist a {
+color: black;
+font-weight: normal;
+text-decoration: none;
+display:block;
+padding: 7pt;
+}
+
+#linklist ul {
+margin: 0;
+padding: 0;
+}
+
+#linklist li {
+text-align: right;
+margin: 0;
+}
+
+.timestamp {
+font-family: Courier New;
+color: #88;
+}
+
+#linklist li:hover {
+border-left: 7px solid #537d7b;
+}
+
+#twit {
+/* -moz-opacity:.2; */
+/* opacity: .2; */
+/* filter:alpha(opacity=20); */
+position: fixed;
+top: 362px;
+box-shadow: 8px 8px 12px #ccc;
+-webkit-border-bottom-right-radius: 10px;
+-moz-border-radius-bottomright: 10px;
+z-index: 100;
+}
+
+.outline-2 {
+position: relative;
+top: 105px;
+left: 215px;
+width: 75%;
+padding-bottom: 5pt;
+}
+}
+
+@media all and (max-width: 700px){
+#linklist{
+width: 130px;
+}
+#linklist a{
+font-size: 10pt;
+}
+#twit{
+display: none;
+}
+.outline-2 {
+left: 145px;
+}
}
pre {
@@ -176,26 +213,6 @@ pre {
filter:alpha(opacity=100);
}
-.outline-2 {
-position: relative;
-left: 215px;
-top: 105px;
-width: 75%;
-padding-bottom: 5pt;
-}
-
-#twit {
-/* -moz-opacity:.2; */
-/* opacity: .2; */
-/* filter:alpha(opacity=20); */
-position: fixed;
-top: 362px;
-box-shadow:
Re: [O] [babel] PROPERTY doesn't do what BABEL did
Eric Schulte eric.schu...@gmx.com writes: cbe...@tajo.ucsd.edu writes: I would like to get the same behavior as when I export a file with (say) these three lines: #+begin_src emacs-lisp :var foo=1 :var bar=2 :results value :exports both (+ foo bar) #+end_src But I'd like to set a buffer wide PROPERTY to achieve that as with a file with these lines: #+property: var foo=1 #+property: var+ bar=2 #+begin_src emacs-lisp :results value :exports both (+ foo bar) #+end_src The above works on my system. You may want to try C-c C-c on one of the property lines so that Org-mode re-reads them (it does this automatically upon opening an Org-mode file). Eric, That did it. So when editting #+PROPERTY lines, C-c C-c on one of them to update the settings. I see this documented in org-ctrl-c-ctrl-c now. But I missed it in the manual. Thanks, Chuck Best, it throws an error under 7.8.02 (downloaded as tar.gz) when I try to export it with 'C-c C-e a yes RET' : progn: Symbol's value as variable is void: foo Other trials seem to show that #+PROPERTY: is ignored by the src blocks I'd really like to get something that does what BABEL used to do as I have a lot of code that relies on that behavior. :-( Chuck ---
Re: [O] Bastiens talk
On 15 December 2011 08:22, Rustom Mody rustompm...@gmail.com wrote: On Wed, Dec 14, 2011 at 11:08 PM, Bastien b...@altern.org wrote: Hi Rustom, Rustom Mody rustompm...@gmail.com writes: I was wondering if there is any brief index into the talk? [I thought I saw something yesterday but cant seem to find it today :-) ] Not sure what you mean by index -- some timeline with timecodes and related topics? Yeah yeah... I remember seeing something like that a day ago -- just 3-4 lines Are you referring to the Google+ links Bastien posted? https://plus.google.com/u/0/102778904320752967064/posts/LQHZRPa1RJE https://plus.google.com/u/0/102778904320752967064/posts/C1PYiVKwGT8 HTH -- Bastien -- Sankalp
Re: [O] Bastiens talk
On Thu, Dec 15, 2011 at 11:03 AM, Sankalp sankalpkh...@gmail.com wrote: On 15 December 2011 08:22, Rustom Mody rustompm...@gmail.com wrote: On Wed, Dec 14, 2011 at 11:08 PM, Bastien b...@altern.org wrote: Hi Rustom, Rustom Mody rustompm...@gmail.com writes: I was wondering if there is any brief index into the talk? [I thought I saw something yesterday but cant seem to find it today :-) ] Not sure what you mean by index -- some timeline with timecodes and related topics? Yeah yeah... I remember seeing something like that a day ago -- just 3-4 lines Are you referring to the Google+ links Bastien posted? https://plus.google.com/u/0/102778904320752967064/posts/LQHZRPa1RJE https://plus.google.com/u/0/102778904320752967064/posts/C1PYiVKwGT8 HTH Ok so its linked from the above to http://vimeo.com/30721952 where it is in the footnote: First eight minutes are a general introduction... etc I'll try and flesh out the rest and post it here
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
1. How do I tell the exporter to include the AUTHOR and DATE fields in the exported output? Pushed a fix for this. 2. I see where the default styles are and I am happy with these generally. However, as a libreoffice n00b, how do I create my own style file that would be appropriate for the ODT exporter? It's not so much about the creating of style files (although help in that regard would not be sniffed at ;-) but about whether there is a list of paragraph styles that can be customised somewhere? Ok. Can you be more specific? Jambunathan K. --
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
There is an implicit association between OpenDocument formats and MS Word. I see no reason why this association should continue to linger amidst masses even to this day where governments are actually clamouring for open standards. OpenDocument format has really nothing to do with MS Word. --
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Give me latex any day! Ok. Take it. http://en.wiktionary.org/wiki/to_each_his_own. --
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Dave Marquardt davem...@us.ibm.com writes: Bastien b...@altern.org writes: as the subject says. Please all test this heavily and report any problems. This will be part of Org 7.8 and soon in Emacs. Thanks a lot to Jambunathan for all this efforts, let's make sure everything is smooth before the release! I installed Org 7.8.02 by downloading the tarball, untarring it, running make, then make install install-info. When I run org-export-as-odt by C-c C-e o, I get this message: Cannot find factory styles file. Check package dir layout Setting debug-on-error, I get this traceback. Did the suggestions in the followup posts work for you? Could you please confirm. Debugger entered--Lisp error: (error Cannot find factory styles file. Check package dir layout) signal(error (Cannot find factory styles file. Check package dir layout)) error(Cannot find factory styles file. Check package dir layout) byte-code(दध\दन\थऩ Interesting to see Hindi here characters ... --
Re: [O] The Org-ODT exporter is now in Org's core (latest git)
Alan That solved the problem. I was loading an old version. If you had copied etc/styles dir by hand to the installation dir I would consider that a bug. This copying should happen auto-magically. I hope things work auto-magically now without any manual intervention. --
Re: [O] ODT export custom link colors?
Christian Moe m...@christianmoe.com writes:
Hi,
I'm not sure about this, because I don't really know the ODT spec,
LibreOffice is my friend.
For instance, in the LibreOffice Styles and Formatting window, choose
the Character styles tab, right-click on Default, select New. Name
your style (e.g.) Bgcolor red. Right-click it, select Modify, in the
Background tab give it a red background.
I usually put the cursor on the text that I am interested in, press F11
and switch to char styles or whatever category. The right style would be
highlighted which you can directly inherit from.
Repeat for other colors you use, e.g. Bgcolor blue, Bgcolor yellow...
Now, modify your custom link code as follows:
(org-add-link-type
bgcolor nil
(lambda (path desc format)
(cond
((eq format 'html)
(formatspan style=\background-color:%s;\%s/span path desc))
((eq format 'latex)
(format\\colorbox{%s}{%s} path desc))
((eq format 'odt)
(format text:span text:style-name=\Bgcolor
%s\%s/text:span path desc))
(t
(formatBGCOLOR LINK (%s): {%s}{%s} format path desc)
The exact scenario you describe here is documented in the manual.
(info (org) Creating one-off styles)
^ C-x C-e here
Look at item 1.
The same node is here:
http://orgmode.org/org.html#Creating-one_002doff-styles
Instead of using an inline markup you can do something like this.
#+begin_src emacs-lisp
(org-odt-format-fontify This text is in red red-style)
#+end_src
It will mark the text in red-style. You can similarly use this or this
for marking text in bold.
#+begin_src emacs-lisp
(org-odt-format-fontify This text is in red 'bold)
#+end_src
I believe you get the drift now.
Note: There are lot more convenience functions that start with
org-odt-format-* that I use internally to emit OpenDocument tags on the
go.
If you look at OrgOdtStyles.xml (C-h v org-odt-styles-dir) and you can
see a bunch of styles marked as Org Agenda Styles. These are used for
marking TODO in red and DONE in green etc.
Copy paste those styles, fix the name and background color and you are
done.
(You can change the style-name in the format string to follow whatever
naming convention you've adopted for your styles. If you want to call
them simply red, blue and so on, it would be
text:style-name=\%s\.)
(Judging from the manual, if you have space in your style names, like
above, you should perhaps escape the spaces with _20_, but the
Bgcolor %s above seems to work fine.)
Please report back if this works for you. If so, and depending on what
Jambunathan might have to add, I'll look into updating the Worg
examples.
(By the way, before I added my 't' case above, it returned nil, which
caused the odt exporter to blow up with an unhelpful error. Would a
patch for that be considered too much of a corner-case? I'd be happy
to submit one.)
I don't know what others think, but I think the habit of always
providing one's custom links with an explicit fallback should be
encouraged, if necessary by rude reminders from failing exporters...
:-)
hth,
Christian
--
Re: [O] odt export error
I can not pinpoint exactly what yields the error, but it reads Format error discovered in the file in sub-document styles.xml at 415,108(row,col) when the file attempts to open in openoffice 3.2. I am using org-mode 7.6. What is your default coding system. As christian points out, the bullet char is not representable in the specific coding system that you use. As a consequence, the file is clobbered. If you are averse to upgrading to latest org -- odt exporter is not available in the standard GNU ELPA packages -- you can switch your org file to utf-8 encoding. That could help a bit. --
Re: [O] [BUG] Various problems with org-odt export
A small side-note. While styles file have moved to root/etc/styles the schema files are still in contrib. One can customize org-export-odt-schema-dir if one sees that auto-validation of xml files doesn't happen anymore. (schema files are in contrib because it will not be checked-into Emacs proper.)
Re: [O] how to bind keys in orgtbl-mode
Hi Carsten, Carsten Dominik wrote: On 9.12.2011, at 22:36, Uwe Brauer wrote: I would like to have the same binding as in org-mode (local-set-key [(control c) (control w)] 'org-table-wrap-region) We could just add this to the standard orgtbl bindings - don't know why this is not the case. OK, I just did that. (local-set-key [(control c) (control h)] 'org-table-insert-hline) This one on the other hand violates Emacs conventions, so we cannot do this by default. FMI, why is the second violating Emacs conventions? I don't really grap a difference between both, and I'm not aware of the convention which would become broken there. Best regards, Seb -- Sebastien Vauban
