Re: [Orgmode] Re: DocBook exporter code (version 1.0)
Hi Baoqui, thank you very much for creating this exporter, and for contributing it to Org. Do you have a copyright assignment with the FSF that would cover Org- mode? If not, would you be willing to sign one? This will give us the freedom to add the file to Emacs at some point. Another small issue: Any files that go into Emacs must, in order to be consistent with the old 8+3 DOS file names, be unique names within the first 8 characters. Even though I like org-export-docbook as a name, I think we need to call it org-docbook.el. At least that gives you the option to do more things with docbook besides export, should you want to. Maybe we should rename org-export-latex to org-latex, for consistency, but this is hard after such a long time. - Carsten On Mar 9, 2009, at 5:46 AM, Baoqiu Cui wrote: Hi Carsten, Carsten Dominik writes: Hi Baoqui, thanks for the link to the code. Forgive me for so far staying quiet on this subject. When you first posted the announcement, I had some mixed feelings. No problem at all. This is totally understandable. First of all, I don't really know docbook, and I have never used it. Then: One of the really weak features in Org's design is that exporting is not implemented in a generic way. All exporters share a preprocessing step that turns Org format into something a little more sane and consistent. Then each exporter goes its own way. This setup makes maintenance sort of a nightmare, because each change to Org syntax needs to be implemented in all exporters separately. ... Yes, it would be nice to have a generic exporting framework in Org. When I just started working on the DocBook exporter, I tried to follow org-export-latex.el first but hit some limitation in org-list-to- generic after a short time. Then I switched to the style of org-export-as- html, and found its line-based exporting very easy to use. ... Maybe you have read my swearing when I was trying to fix the LaTeX exporter which I did not understand completely at first - it was written by Bastien. I haven't read about this, but I can imagine what kind of difficulty you might have... I had really hoped that the next step in exporting Org would be to rewrite the exporter from scratch, in a generic way, that will then make supporting different formatters more stable and easy. Adding a new exporter does not get us closer to that idea. Agreed. If Org documents can be parsed into tree representations by the generic exporter, and each individual exporter only needs to configure the tags (or formatting methods) for all components in the tree, writing different exporters would be much easier. Not sure if this can be easily done in Org. And I had feared that your exporter would be a badly hacked attempt reinventing lots of wheels, that could never become a really complete export. I have misjudged severely, the exporter you made looks quite complete, you have based it very heavily on the XHTML exporter and in this way it seems to be able to handle the entire Org syntax, if I see correctly. ... Yes, DocBook exporter is heavily based on the XHTML exporter. Both exporters shares a lot of processing, but differ at other areas. Some internal functions used by these two exporters could be merged in the future. ... So I have now made the changes you require in org-exp.el, and I would like to include the exporter, once you are satisfied, into our contrib directory or even, depending on copyright assignment, into the core. Thanks a lot for making the changes in org-exp.el! I've removed the modified version of org-exp.el from my repository on Google Code. I'll try to do more testing (including testing it on XEmacs) and incorporate any comments that other people may have before you can put this exporter into Org release. However, I need to make clear that I have no time to maintain another exporter, so I would hope that you would be willing to to the necessary work to keep it up to date and working. I won't have any problem with maintaining this exporter. Thanks, Baoqiu Best wishes - Carsten On Mar 8, 2009, at 6:10 AM, Baoqiu Cui wrote: Hi, I just posted the code for DocBook exporter to Google Code. You can use the following link to get access to the code and example files: http://code.google.com/p/bcui-emacs/source/browse/#svn/trunk/org- docbook Here is the README: = = = = # # File: org-docbook/README # # $Id$ # This is the DocBook exporter for Org-mode, a tool written in Emacs Lisp to export text files written in Org-mode to DocBook. This directory contains: README This file. org-export-docbook.el The main part of DocBook exporter code. org-exp.el Slightly modified version of file org-exp.el that is part of Org-mode. Currently this file is synced up with Org-mode 6.24. test.org An Org file used for testing. It includes all the features that
[Orgmode] Re: done-ing a repeating scheduled task now inserts closed timestamp?
Sorry for the pause (I was pretty busy last week): > Another idea to get this: > > Turn on state change notes or at least time stamps. Either globally, > or locally for this entry with a LOGGING property: > > ** TODO Check backups > SCHEDULED: <2009-03-05 Thu 11:00 +2d> > :PROPERTIES: > :LOGGING: DONE(!) > :END: > > (yes, scheduled, thanks Bernt...) > Then each time you go through the DONE state, a time stamp > will be recorded like this (I am assuming that you have > org-log-into-drawer set...) > > ** TODO Check backups > SCHEDULED: <2009-04-28 Tue 11:00 +2d> > :LOGBOOK: > - State "DONE" from "TODO" [2009-03-04 Wed 14:25] > - State "DONE" from "TODO" [2009-03-02 Mon 14:25] > - State "DONE" from "TODO" [2009-02-28 Sat 14:25] > - State "DONE" from "TODO" [2009-02-26 Thu 14:25] > :END: > :PROPERTIES: > :LOGGING: DONE(!) > > In the agenda, if you press `C-u l', these state notes > will become visible. > > I believe this will take care of it, right?? Yes, this is much closer than what one would like. And having those "done states" together could be useful. However, I have to say that though that after trying to adapt to these settings I cannot bend my mind to find the behavior comfortable, specially comparing to how normal tasks work. For me it is confusing that when I do "t" on such a task it goes to "DONE" as I would expect (i.e., like a normal TODO task) but when I refresh the agenda it disappears (unlike normal DONE tasks, at least with my settings --I use archiving to make done tasks disappear and "v" to toggle viewing archived tasks). Actually, I think it goes to DONE only for the first repeat, for the following repeats it stays as TODO, at least with my settings. I guess I can use org-agenda-skip-scheduled-if-done to get the non-repeating tasks to disappear also when marked as done (so that there is more orthogonality) but, again, it will only work if I remember to use "SCHEDULED" for them, and, also, I do not want them to disappear yet! ;-) Also, I feel I have to remember too many things for, say, a simple weekly meeting: a) putting SCHEDULED, b) setting the properties, c) making sure org-log-into-drawer is set, etc. Ideally any simple TODO entry with a repeating timestamp should behave well when marked as done, right? > to me this sounds like a pretty convincing argument *not* > to copy entries... Yes, I guess this is a problem (although in my case all repeating entries --which are regular meetings, classes, birthdays, etc.-- are typically one liners so it would not make a difference if they were copied...). Sorry to insist, but I still think copying the tasks would produce a more orthogonal behavior. Perhaps it could be made optional? Man -- --- Manuel Hermenegildo | Prof., C.S.Dept., T.U. Madrid (UPM) Director, IMDEA-Software and CLIP Group | +34-91-336-7435 (W) -352-4819 (Fax) --- ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-annotate on windows
One more thing: The backslash in the bookmarklet makes FF barf In any case the spaces transform into %20 which makes it much more unwieldy and ugly so the bookmarklet that I paste (and works as far as I know) is just: javascript:location.href='remember://'+location.href+'::remember::'+escape(document.title)+'::remember::'+escape(window.getSelection()) (no newlines or spaces anywhere) ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: Fwd: [Orgmode] ascii export of url part of links possible?
See thread for more details. * test export this is a test[fn:36]. it is also a test[fn:37]. and it has a link [[googlelink.com][google link one]]. and another [fn:38] and another [[yahoolink.com][yahoo link two]].[fn:39] footnotes [fn:36] one [fn:37] two [fn:38] three [fn:39] four On Tue, Mar 3, 2009 at 02:40, Giovanni Ridolfi wrote: > [snip quoted text] > > I don't understand the problem! > > Samuel, please > could show us the *org* test file.? > > eg: > file--- > ** test > his is a test[1]. it is also a test[2]. and it > has a link [google link one]. and another [3] and another > [yahoo link two].[4] > > footnotes > [fn:39] four > [1] one > > [2] two > > [3] three > > [4] [fn:39] > *** > [google link one]: googlelink.com > [yahoo link two]: yahoolink.com > > > __ > Do You Yahoo!? > Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto > spazio gratuito per i tuoi file e i messaggi > http://mail.yahoo.it > > -- Myalgic encephalomyelitis denialism is causing death (decades early; Jason et al. 2006) and severe suffering, pain, and disability (worse than nearly all other serious diseases studied; Schweitzer et al. 1995) and grossly corrupting science. The denialism is worse than it ever was with even AIDS or MS. http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: done-ing a repeating scheduled task now inserts closed timestamp?
Hi Manuel, first of all, you don't need to take notes into the LOGBOOK drawer. If that is off, notes will be just added after the heading. Second, setting the properties for logstate or lognotestate is actually not necessary at all, my mistake. It is sufficient to have org-log-repeat set, and the default is `time', so you should automatically get a time stamp each time an entry repeats. Don't you? About the behavior in the agenda, I think it is already very nice of me :-) to show you the task as DONE until the next refresh - because in the original buffer, is is actually already TODO again. If you always want to see state changes when you press `l' in the agenda (i.e. by default, without pressing `C-u l'), then you can configure the variable org-agenda-log-mode-items to include also the symbol `state'. For the copying, I think we really need to make a difference between a single task that repeats, and many similar tasks, which is what you are talking about. A single task that repeats is the current behavior, and I still believe it makes sense this way. Why, if you want to have many tasks instead of one, don't you just create many directly, with different dates. A keyboard macro would work for this, or a little function that does the copying and time shifting. I may make a function that copies a task N times with a certain date shift. The more I think about the automatic copying when DONE, the less sense it makes to me, I am afraid. - Carsten On Mar 8, 2009, at 7:25 PM, Manuel Hermenegildo wrote: Sorry for the pause (I was pretty busy last week): Another idea to get this: Turn on state change notes or at least time stamps. Either globally, or locally for this entry with a LOGGING property: ** TODO Check backups SCHEDULED: <2009-03-05 Thu 11:00 +2d> :PROPERTIES: :LOGGING: DONE(!) :END: (yes, scheduled, thanks Bernt...) Then each time you go through the DONE state, a time stamp will be recorded like this (I am assuming that you have org-log-into-drawer set...) ** TODO Check backups SCHEDULED: <2009-04-28 Tue 11:00 +2d> :LOGBOOK: - State "DONE" from "TODO" [2009-03-04 Wed 14:25] - State "DONE" from "TODO" [2009-03-02 Mon 14:25] - State "DONE" from "TODO" [2009-02-28 Sat 14:25] - State "DONE" from "TODO" [2009-02-26 Thu 14:25] :END: :PROPERTIES: :LOGGING: DONE(!) In the agenda, if you press `C-u l', these state notes will become visible. I believe this will take care of it, right?? Yes, this is much closer than what one would like. And having those "done states" together could be useful. However, I have to say that though that after trying to adapt to these settings I cannot bend my mind to find the behavior comfortable, specially comparing to how normal tasks work. For me it is confusing that when I do "t" on such a task it goes to "DONE" as I would expect (i.e., like a normal TODO task) but when I refresh the agenda it disappears (unlike normal DONE tasks, at least with my settings --I use archiving to make done tasks disappear and "v" to toggle viewing archived tasks). Actually, I think it goes to DONE only for the first repeat, for the following repeats it stays as TODO, at least with my settings. I guess I can use org-agenda-skip-scheduled-if-done to get the non-repeating tasks to disappear also when marked as done (so that there is more orthogonality) but, again, it will only work if I remember to use "SCHEDULED" for them, and, also, I do not want them to disappear yet! ;-) Also, I feel I have to remember too many things for, say, a simple weekly meeting: a) putting SCHEDULED, b) setting the properties, c) making sure org-log-into-drawer is set, etc. Ideally any simple TODO entry with a repeating timestamp should behave well when marked as done, right? to me this sounds like a pretty convincing argument *not* to copy entries... Yes, I guess this is a problem (although in my case all repeating entries --which are regular meetings, classes, birthdays, etc.-- are typically one liners so it would not make a difference if they were copied...). Sorry to insist, but I still think copying the tasks would produce a more orthogonal behavior. Perhaps it could be made optional? Man -- --- Manuel Hermenegildo | Prof., C.S.Dept., T.U. Madrid (UPM) Director, IMDEA-Software and CLIP Group | +34-91-336-7435 (W) -352-4819 (Fax) --- ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Show parent header in agenda
På Fri, 06 Mar 2009 19:27:19 +0100, skrev Richard Riley : Eric S Fraga writes: On 2009-03-06, Ivan Nedrehagen wrote: Hi, org-mode is the best organizer in the world. To bad I cant fit emacs in my filofax ;) This is currently my personal holy grail... I'm constantly scouring the web-sphere for any small computer that will (a) fit in my jacket pocket and (b) run emacs! I want something to replace my old Psion 3s which is what I used until the last one died and I switched to org-mode instead. Having now gotten used (addicted, methinks) to org-mode, the bar has been raised and I cannot consider any computer that won't run Emacs as a result. There are a couple of contenders just appearing on the market, or which *may* be appearing, including the umid m1 and the openpandora project. I do fully expect something appropriate and hopefully affordable will appear on the market this year. At the moment, I use my Asus eee PC (the original model) as my organizer (typing this message on it, in fact) but it's a little large to fit in any jacket pocket unfortunately. I have been looking too, but cant help feeling anything smaller than an netbook just wont have the keyboard needed for emacs. That is the real problem. I have a Neo Freerunner (Open smartphone) capable of running most linux programs. But with a onscreen keyboard, emacs wouldn't do much good. Instead I am writing an python application that can sync and display my headers from my org file. It is not the same, but it extends the "reach" of my org-file. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: R: [Orgmode] Show parent header in agenda
På Fri, 06 Mar 2009 16:14:17 +0100, skrev : --- Ven 6/3/09, Ivan Nedrehagen ha scritto: skrev Giovanni Ridolfi : > Why don't you use tags? One real header: * TODO [#A] Spindle axis calibration: Disconnect sensor before rotating If you ask me, that is quite a large tag. what about pressing "b" in the agenda to display the subtree ? Giovanni __ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it The b gives me the subtree, but not the super tree from +1 level. It might seem like this is something that must be programmed. Elisp isn't the language I am most at home with, but i'll add a item for it in my org-file, It might just be my first contribution to the org-mode. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: Re: R: [Orgmode] Show parent header in agenda
--- Lun 9/3/09, Ivan Nedrehagen ha scritto: > skrev : > > --- Ven 6/3/09, Ivan Nedrehagen > >> skrev Giovanni Ridolfi : > > > > what about pressing "b" in the agenda to display the > subtree ? > The b gives me the subtree, but not the super tree from +1 > level. please, read more carefully the manual on section 10.5. use C-u N[1] b [1] with N the number of headings you want to go up cheers, Giovanni __ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: R: [Orgmode] Show parent header in agenda
Also, SPC will show the entry in its environment. And "f" will toggle follow-mode, an automatic way to show the entry at point in it environment. - Carsten On Mar 9, 2009, at 10:47 AM, Giovanni Ridolfi wrote: --- Lun 9/3/09, Ivan Nedrehagen ha scritto: skrev : --- Ven 6/3/09, Ivan Nedrehagen skrev Giovanni Ridolfi : what about pressing "b" in the agenda to display the subtree ? The b gives me the subtree, but not the super tree from +1 level. please, read more carefully the manual on section 10.5. use C-u N[1] b [1] with N the number of headings you want to go up cheers, Giovanni __ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: Re: R: [Orgmode] Show parent header in agenda
please, read more carefully the manual on section 10.5. use C-u N[1] b [1] with N the number of headings you want to go up Yes indeed, C-u 1 b shows the parent header in another buffer. It does not give me quite the overview that I am looking for but it is a decent alternative. But I think Ill give my Elisp a shot. I am thinking of a solution that would fit me. If I have a TODO that is covered by subtopics, I mark it with the todo string IN PROGRESS (an alternative would be a tag) Ill make some option so that, if there is a header marked IN PROGRESS (or tag) it will display it and a filtered selection of the subheaders. So that my agenda will look like this: mygtd: ...IN PROGRESS A main topic mygtd: ...+TODO Fix me mygtd: ...+TODO Fix me too mygtd: ...+NEXT Fix me first or something like that. But in the meantime ill just make a shortcut to C-u 1 b ;) Thanks ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] GOAL keyword with DEADLINE semantics?
Hi Austin, since you want to use the same semantics as for deadlines, i.e. the same warning period etc, this really is a psychological issue :-) It is trouble to implement a new keyword or number of keywords. New commands needed to insert this new keyowrd, for example, and many regular expressions to generalize. What I would do if I was bothered by this would be (setq org-deadline-string "DUE:") which captures both the colors of DEADLINE and GOAL pretty well, I think. In fact, I wish I had made this the default from beginning, a much shorter and nicer word. Now it is too late to change this, I am afraid. - Carsten On Mar 8, 2009, at 4:36 PM, Austin Frank wrote: Hi all! Currently we can use the DEADLINE keyword to indicate a target date for an item to be finished. By my way of thinking, deadlines make sense for externally imposed constraints. I also try to set goals for myself for when an item will be completed. These are softer than deadlines, but I think they could share the same semantics for creation, display, and export. Would it be possible to make `org-deadline-string' a list of strings that get handled in the same way as DEADLINE is currently handled? That way I could do things like * TODO write first chapter GOAL: <2009-03-09 Mon> * TODO submit manuscript GOAL: <2009-05-15 Fri> DEADLINE: <2009-06-01 Mon> Where the first represents my own planning process and the second contains my target completion date (trying to work ahead!) and the hard constraint imposed by whoever I'm submitting to. In all cases, I'd like agenda notification as the date approaches, I'd like to know if I've passed it by, and I'd like the option of including it in ical export. Or maybe I should just learn to treat my GOALs like DEADLINEs and stop letting myself off the hook so easily ;) Do other people think about things this way? Would you have a use for a customizable list of keywords that all had the same semantics that DEADLINE currently has? Thanks for considering it, /au -- Austin Frank http://aufrank.net GPG Public Key (D7398C2F): http://aufrank.net/personal.asc ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: alter all subtrees containing specific tag
writes:
>
> Just discovered a bug in my previously posted function. It doesn't work
> too well if you have lower level subtrees tagged for encryption.
I also forgot to mention that you need to have pgg pre-loaded.
This will ensure that:
(defun my-func-org-toggle-encryption (rcpts passphrase)
(interactive (list (split-string (read-string "Recipients (default is none):
") "[ \t,]+")
(pgg-read-passphrase "GnuPG passphrase: ")))
(require 'pgg)
(show-all)
(org-map-entries '(let (start end teststring)
(org-outline-level)
(next-line)
(org-beginning-of-line)
(setq start (point))
(setq teststring (buffer-substring start (+ start 27)))
(outline-get-next-sibling)
(if (not (equal (point) (point-max)))
(previous-line))
(org-end-of-line)
(setq end (point))
(if (equal teststring "-BEGIN PGP MESSAGE-")
(if (pgg-decrypt-region start end passphrase)
(pgg-display-output-buffer start end t)
(message "Can't decrypt region!"))
(if (equal rcpts '(""))
(pgg-encrypt-symmetric-region start end passphrase)
(pgg-encrypt-region start end rcpts nil passphrase))
(pgg-display-output-buffer start end t)))
"+ENCRYPT"))
--
aleblanc
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: GOAL keyword with DEADLINE semantics?
Carsten Dominik writes: > (setq org-deadline-string "DUE:") > > which captures both the colors of DEADLINE and GOAL pretty well, I > think. > > In fact, I wish I had made this the default from beginning, > a much shorter and nicer word. Now it is too late to change this, I > am afraid. Is it really too late? Could you maybe make the REGEXP that matches the deadline look for both DEADLINE: and DUE: but make new deadlines use DUE: ? As long as you don't force everyone to s/DEADLINE:/DUE:/ in their existing setup I don't think there's a huge impact with this change. Just my two cents. -Bernt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-annotate on windows
Strangely I cant get it to work on my linux box though it works on windows. Linux clicking the bookmarklet gives me firefox does not know how to open this address because the protocol (remember) is not associated with any program. Note my config settings has network-protocol-handler.app.remember is string oah network-protocol-handler.external.remember is boolean true where oah is the shell script youve given and runs from a shell prompt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: changes to return-follows-link
> On Fri, 6 Mar 2009 18:15:25 +0100, Carsten Dominik > said: CD> RET in the agenda is supposed to go to the location that triggered CD> the entry, in your case the scheduling time stamp. I did not even CD> know that it used to follow a link. It did ;-) CD> The direct command to follow a link from the agenda is `C-c C-o', CD> `org-agenda-open-link'. Ok, thanks. I'll either switch to that or bind some other key to it. Thanks! -- "In the bathtub of history the truth is harder to hold than the soap, and much more difficult to find." -- Terry Pratchett ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] org-oddmuse.el
Hi all, I have develop org-oddmuse.el for convert Org-mode text to Oddmuse Wiki format. Detail describe at: http://www.emacswiki.org/emacs/OrgOddmuse File at: http://www.emacswiki.org/cgi-bin/emacs/org-oddmuse.el Enjoy! -- Andy ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: DocBook exporter code (version 1.0)
Hi Carsten, Carsten Dominik writes: > Hi Baoqui, > > thank you very much for creating this exporter, and for contributing > it to Org. > > Do you have a copyright assignment with the FSF that would cover Org- > mode? > If not, would you be willing to sign one? This will give us the freedom > to add the file to Emacs at some point. I don't have a copyright assignment with FSF yet. I will sign one and send it to FSF and you. > Another small issue: Any files that go into Emacs must, > in order to be consistent with the old 8+3 DOS file names, > be unique names within the first 8 characters. Even though > I like org-export-docbook as a name, I think we need to call it > org-docbook.el. At least that gives you the option to do > more things with docbook besides export, should you want to. This sounds good to me. I have renamed the file to org-docbook.el. Thanks, Baoqiu ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Is column view buggy?
El dj, mar 05 2009, Carsten Dominik va escriure: >> >> 1. The cursor isn't visible sometimes when it is over a header which has the >> ellipsis (...) at the end. > > I have never seen this one. > Of course, because it's invisible! :-) I think it has to do with the colors for the ellipsis or cursor. But I could not reproduce it today. >> >> 2. When I press the up/down arrows, the cursor goes to the upper/ >> lower line, but 1 cell to the right. This happens just for the first up/down >> movement after a left/right one. > > Yes, this I have seen, and now fixed. > Thanks, it seems to work in the normal case. There are still some strange jumps; see below. >> >> 3. Sometimes the cursor is locked in a cell and I can't move it down with the >> down arrow key (however, up/left/right work). > > I have not seen that either, maybe you can create a reproducible test case? > I can reproduce this bug in column view mode simply using this .emacs --- (add-to-list 'load-path "/w/org-mode/lisp") (require 'org-install) (setq org-startup-truncated nil) --- , Emacs 23.0.91.2, org-mode 6.24a, and this test file: --- #+COLUMNS: %10ITEM %3TODO %40name %34title %47comment * test column view ** TODO one :PROPERTIES: :name: ttt ttt :title:mmm m :comment: c cc c c c c c cc :END: ** two :PROPERTIES: :name: ggg ggg :title:zzz z :comment: p pp p p p p p pp :END: ** DONE three :PROPERTIES: :name: TTT TTT :title:MMM M :comment: C CC C C C C C CC :END: --- You must have lines longer than the window so that they span two visual lines each. 1. Enter column mode in the first heading 2. Press down arrow. It doesn't move Another: 1. Click in first or second item line 2. Press down arrow until you reach the third item 3. Press up arrow. It can't move up Another way: 1. Expand the three item with TAB so that you see the :PROPERTIES: line for each 2. Click the middle one in the g 3. You cannot move down 4. Click the field to the right (z) 5. You cannot move neither up nor down with the arrow keys This seems only one bug. I suppose that the (next-line) should move by real lines instead of by logical lines. Thanks, Daniel ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error
Carsten,
Attached text file with original table.org and associated backtrace. This
was run on 6.24a fresh from git.
Slight delay in that I could not get back to my Linux machine for a few
days. Also the org-reload does not work as it seems neither my windows or
ubuntu machine recognize find-library-name (definition-is-void) so this may
be the cause of the above problem.
Thank you for looking into this.
Andrew
On Thu, Mar 5, 2009 at 10:28 AM, Carsten Dominik wrote:
> Please make a backtrace with uncompiled code:
>
> Reload Org with
>
> C-u C-c C-x r
>
> and hit the error again.
>
> Thanks.
>
> - Carsten
>
>
> On Mar 4, 2009, at 7:48 PM, andrew dasys wrote:
>
> Trying to org-export-latex-... any table in 6.23trans and 6.23b results
>> both on WinXP and Ubuntu results in an error. Sending to html works great.
>> Any guidance would be greatly appreciated.
>>
>> Table is as simple As I could think of:
>>
>> * MASH
>> | id | Actor | Character |
>> |+---+---|
>> | 1 | Allan Alda| "Hawkeye" Benjamin Pierce |
>> | 2 | Gary Burghoff | "Radar" Walter O'Reilly |
>> | 3 | Loretta Switt | "Hotlips" Margaret Hoolihan |
>>
>>
>> Results in following error:
>>
>> Exporting to LaTeX...
>> setq: Wrong number of arguments: #[(string &optional separators)
>> ^E^@^Y^ZESC^\
>> ^L
>>
>> &^...@^kǔu&^...@^k^mgw&^...@^kt'^...@^k#y...@ǔ^mgwY^@^Rǔ=S
>> ^...@ǔ=k...@ǔ^k=s...@^m^kǔo
>> B^QǕ^S^...@^k^mg=g...@^m^kOB^Q
>> ," [separators list notfirst start rexp string "[ ^L
>> ^M^K]+" 0 nil string-match ...] 5 1390318], 3
>> ./tmp/table.org (END)
>>
>>
>>
>> Does not seem to be resolved by Manish's comments from:
>> http://lists.gnu.org/archive/html/emacs-orgmode/2009-02/msg00354.html
>>
>> P.S Continue to be amazed by Org - great work thank you.
>> P.P.S thread on variable usage was great way to see how others were using
>> Org.
>> ___
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
>
* MASH
| id | Actor | Character |
|+---+---|
| 1 | Allan Alda| "Hawkeye" Benjamin Pierce |
| 2 | Gary Burghoff | "Radar" Walter O'Reilly |
| 3 | Loretta Switt | "Hotlips" Margaret Hoolihan |
Debugger entered--Lisp error: (wrong-number-of-arguments #[(string &optional
separators) "?? ??
??& U??&
GW??& T??' #??Y
GW??Y ????=??S =??K =??S
O B??
G=??g
??OB ??,??" [separators list notfirst start rexp string "[
]+" 0 nil string-match t] 5 1390318] 3)
split-string(#("| id | Actor | Character
|\n|+---+---|\n| 1 | Allan Alda
| ``Hawkeye'' Benjamin Pierce |\n| 2 | Gary Burghoff | ``Radar'' Walter
O'Reilly |\n| 3 | Loretta Switt | ``Hotlips'' Margaret Hoolihan |\n" 0 2
nil 2 4 (org-label nil org-attributes nil org-caption nil fontified nil) 4 7
nil 7 12 (org-label nil org-attributes nil org-caption nil fontified nil) 12 23
nil 23 32 (org-label nil org-attributes nil org-caption nil fontified nil) 32
113 nil 113 114 (org-label nil org-attributes nil org-caption nil fontified
nil) 114 117 nil 117 127 (org-label nil org-attributes nil org-caption nil
fontified nil) 127 133 nil 133 135 (org-protected t) 135 141 (org-label nil
org-attributes nil org-caption nil fontified nil) 141 142 (org-protected t
fontified nil org-caption nil org-attributes nil org-label nil) 142 144
(org-protected t) 144 160 (org-label nil org-attributes nil org-caption nil
fontified nil) 160 168 nil 168 169 (org-label nil org-attributes nil
org-caption nil fontified nil) 169 172 nil 172 185 (org-label nil
org-attributes nil org-caption nil fontified nil) 185 188 nil 188 190
(org-protected t) 190 194 (org-label nil org-attributes nil org-caption nil
fontified nil) 194 195 (org-protected t fontified nil org-caption nil
org-attributes nil org-label nil) 195 197 (org-protected t) 197 213 (org-label
nil org-attributes nil org-caption nil fontified nil) 213 223 nil 223 224
(org-label nil org-attributes nil org-caption nil fontified nil) 224 227 nil
227 240 (org-label nil org-attributes nil org-caption nil fontified nil) 240
243 nil 243 245 (org-protected t) 245 251 (org-label nil org-attributes nil
org-caption nil fontified nil) 251 252 (org-protected t fontified nil
org-caption nil org-attributes nil org-label nil) 252 254 (org-protected t) 254
272 (org-label nil org-attributes nil org-caption nil fontified nil) 272 275
nil) "\n" t)
(setq lines (split-string raw-table "\n" t))
(progn (setq caption (org-find-text-property-in-string ... raw-table) attr
(org-find-text-property-in-string ... raw-table) label
(org-find-text-property-in-string ... raw-table) longtblp (and attr ... ...)
al
[Orgmode] Bug? M-S-RET on a line
Hi, Suppose I have an org file with following lines: * Test1 Test2 Now if I put the cursor at the beginning of the "Test2" line and press "M-S-RET" (Alt-Shift-Return on my machine), I got this: * Test1 * Test2TODO The "TODO" keyword was inserted at the end instead of the beginning of the task text. This seems a bug to me. I am using the latest release, 6.24a. Thanks for confirmation and investigation. Wanrong ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error
andrew dasys wrote:
>
> * MASH
> | id | Actor | Character |
> |+---+---|
> | 1 | Allan Alda| "Hawkeye" Benjamin Pierce |
> | 2 | Gary Burghoff | "Radar" Walter O'Reilly |
> | 3 | Loretta Switt | "Hotlips" Margaret Hoolihan |
>
> [export to latex gets error]
I cannot reproduce this - the export succeeds (but see below). Version info:
GNU Emacs 23.0.91.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2009-03-06 on
alphaville.usa.hp.com
Org-mode version 6.24
>
> Debugger entered--Lisp error: (wrong-number-of-arguments #[(string &optional
> separators) "Â ÃÃÃÂ Ã
> Â& ÃÂUÂ&
GWÂ& TÂ' #ÂY ÃÂ
GWÂY ÃÃÂÃ=ÂS ÃÂÃÂ=ÂK ÃÂ =ÂS
ÃÂO BÃÂÂ
G=Âg
ÃOB Â,Â" [separators list notfirst start rexp string "[
>
]+" 0 nil string-match t] 5 1390318] 3)
> split-string(#("| id | Actor | Character
> |\n|+---+---|\n| 1 | Allan Alda
> | ``Hawkeye'' Benjamin Pierce |\n| 2 | Gary Burghoff | ``Radar'' Walter
> O'Reilly |\n| 3 | Loretta Switt | ``Hotlips'' Margaret Hoolihan |\n" 0 2
> nil 2 4 (org-label nil org-attributes nil org-caption nil fontified nil) 4 7
> nil 7 12 (org-label nil org-attributes nil org-caption nil fontified nil) 12
> 23 nil 23 32 (org-label nil org-attributes nil org-caption nil fontified nil)
> 32 113 nil 113 114 (org-label nil org-attributes nil org-caption nil
> fontified nil) 114 117 nil 117 127 (org-label nil org-attributes nil
> org-caption nil fontified nil) 127 133 nil 133 135 (org-protected t) 135 141
> (org-label nil org-attributes nil org-caption nil fontified nil) 141 142
> (org-protected t fontified nil org-caption nil org-attributes nil org-label
> nil) 142 144 (org-protected t) 144 160 (org-label nil org-attributes nil
> org-caption nil fontified nil) 160 168 nil 168 169 (org-label nil
> org-attributes nil org-caption nil fontified nil) 169 172 nil 172 185
> (org-label nil org-attributes nil org-caption nil fontified nil) 185 188 nil
> 188 190 (org-protected t) 190 194 (org-label nil org-attributes nil
> org-caption nil fontified nil) 194 195 (org-protected t fontified nil
> org-caption nil org-attributes nil org-label nil) 195 197 (org-protected t)
> 197 213 (org-label nil org-attributes nil org-caption nil fontified nil) 213
> 223 nil 223 224 (org-label nil org-attributes nil org-caption nil fontified
> nil) 224 227 nil 227 240 (org-label nil org-attributes nil org-caption nil
> fontified nil) 240 243 nil 243 245 (org-protected t) 245 251 (org-label nil
> org-attributes nil org-caption nil fontified nil) 251 252 (org-protected t
> fontified nil org-caption nil org-attributes nil org-label nil) 252 254
> (org-protected t) 254 272 (org-label nil org-attributes nil org-caption nil
> fontified nil) 272 275 nil) "\n" t)
> (setq lines (split-string raw-table "\n" t))
... and this looks very strange to me: split-string is similar to AWK's or
Python's
split() function, which is supposed to split a string using the given separator,
and return a list of substrings. The argument to split-string is correct (the
raw table
as a string), as is the separator ("\n"). So where does split-string get the
ungodly
mess shown above? Is it possible that you have redefined split-string somehow?
Or perhaps
some matching function that split-string uses?
What happens if you evaluate the following (just press C-x C-e after the
closing paren or cut-and-paste the expression into the *scratch* buffer
and press C-j)? What happens if you restart your emacs with -Q and
evaluate the same expression? In my setup, I can evaluate the following
with no errors:
(split-string #("| id | Actor | Character
|\n|+---+---|\n| 1 | Allan Alda
| ``Hawkeye'' Benjamin Pierce |\n| 2 | Gary Burghoff | ``Radar'' Walter
O'Reilly |\n| 3 | Loretta Switt | ``Hotlips'' Margaret Hoolihan |\n" 0 2
nil 2 4 (org-label nil org-attributes nil org-caption nil fontified nil) 4 7
nil 7 12 (org-label nil org-attributes nil org-caption nil fontified nil) 12 23
nil 23 32 (org-label nil org-attributes nil org-caption nil fontified nil) 32
113 nil 113 114 (org-label nil org-attributes nil org-caption nil fontified
nil) 114 117 nil 117 127 (org-label nil org-attributes nil org-caption nil
fontified nil) 127 133 nil 133 135 (org-protected t) 135 141 (org-label nil
org-attributes nil org-caption nil fontified nil) 141 142 (org-protected t
fontified nil org-caption nil org-attributes nil org-label nil) 142 144
(org-protected t) 144 160 (org-label nil org-attributes nil org-caption nil
fontified nil) 160 168 nil 168 169 (org-label nil org-attributes nil
org-caption nil fontified nil) 169 172 nil 172 185 (org-label nil
org-attributes nil org-caption nil fontified nil) 185 188 nil 188 190
(org-protected t) 190
latex exporting strangeness [was: Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error]
[replying to my own mail] Nick Dokos wrote: > > I said above that the export succeeds and it does, in the sense that I > get no errors. However, the exported latex looks strange - the table > comes *before* the "MASH" section. Is this a bug or is it a peculiarity > of my configuration? Can somebody please try it and let me know? > I seem to recall that this has come up before: basically, an empty line at the beginning of the org file restores sanity. So even if it is a bug, there is an easy workaround. Sorry for the noise, Nick ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error
Nick,
thank you for looking at this.
I am running Emacs 21.4.1 Nothing bleeding edge here.
The help for split-string looks reasonable (compiled Lisp comes from "subr"
) (complete output attached)
A bit of debugging gets me to the point where split-string works fine if you
only include the text that is in the table so from
"|id . Hoolihan |\n"
if you add any of the other text starting at:
0 2 nil 2 4 (org-label nil org
then I get the error.
On Mon, Mar 9, 2009 at 6:22 PM, Nick Dokos wrote:
> andrew dasys wrote:
>
> >
> > * MASH
> > | id | Actor | Character |
> > |+---+---|
> > | 1 | Allan Alda| "Hawkeye" Benjamin Pierce |
> > | 2 | Gary Burghoff | "Radar" Walter O'Reilly |
> > | 3 | Loretta Switt | "Hotlips" Margaret Hoolihan |
> >
> > [export to latex gets error]
>
> I cannot reproduce this - the export succeeds (but see below). Version
> info:
>
> GNU Emacs 23.0.91.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2009-03-06
> on alphaville.usa.hp.com
> Org-mode version 6.24
>
> >
> > Debugger entered--Lisp error: (wrong-number-of-arguments #[(string
> &optional separators) " † ÆÇȉÉ
> > ƒ& ǔUƒ&
> GWƒ& T‚' #ƒY ǔ
> GWƒY Ê Ç”Ç=„S ǔǕ=ƒK ǔ =„S
> ǔO B Ǖ ‚
> G=„g
> ÈOB Ÿ,‡" [separators list notfirst start rexp string "[
> >
> ]+" 0 nil string-match t] 5 1390318] 3)
> > split-string(#("| id | Actor | Character
> |\n|+---+---|\n| 1 | Allan Alda
>| ``Hawkeye'' Benjamin Pierce |\n| 2 | Gary Burghoff | ``Radar''
> Walter O'Reilly |\n| 3 | Loretta Switt | ``Hotlips'' Margaret Hoolihan
> |\n" 0 2 nil 2 4 (org-label nil org-attributes nil org-caption nil fontified
> nil) 4 7 nil 7 12 (org-label nil org-attributes nil org-caption nil
> fontified nil) 12 23 nil 23 32 (org-label nil org-attributes nil org-caption
> nil fontified nil) 32 113 nil 113 114 (org-label nil org-attributes nil
> org-caption nil fontified nil) 114 117 nil 117 127 (org-label nil
> org-attributes nil org-caption nil fontified nil) 127 133 nil 133 135
> (org-protected t) 135 141 (org-label nil org-attributes nil org-caption nil
> fontified nil) 141 142 (org-protected t fontified nil org-caption nil
> org-attributes nil org-label nil) 142 144 (org-protected t) 144 160
> (org-label nil org-attributes nil org-caption nil fontified nil) 160 168 nil
> 168 169 (org-label nil org-attributes nil org-caption nil fontified nil) 169
> 172 nil 172 185 (org-label nil org-attributes nil org-caption nil fontified
> nil) 185 188 nil 188 190 (org-protected t) 190 194 (org-label nil
> org-attributes nil org-caption nil fontified nil) 194 195 (org-protected t
> fontified nil org-caption nil org-attributes nil org-label nil) 195 197
> (org-protected t) 197 213 (org-label nil org-attributes nil org-caption nil
> fontified nil) 213 223 nil 223 224 (org-label nil org-attributes nil
> org-caption nil fontified nil) 224 227 nil 227 240 (org-label nil
> org-attributes nil org-caption nil fontified nil) 240 243 nil 243 245
> (org-protected t) 245 251 (org-label nil org-attributes nil org-caption nil
> fontified nil) 251 252 (org-protected t fontified nil org-caption nil
> org-attributes nil org-label nil) 252 254 (org-protected t) 254 272
> (org-label nil org-attributes nil org-caption nil fontified nil) 272 275
> nil) "\n" t)
> > (setq lines (split-string raw-table "\n" t))
>
> ... and this looks very strange to me: split-string is similar to AWK's or
> Python's
> split() function, which is supposed to split a string using the given
> separator,
> and return a list of substrings. The argument to split-string is correct
> (the raw table
> as a string), as is the separator ("\n"). So where does split-string get
> the ungodly
> mess shown above? Is it possible that you have redefined split-string
> somehow? Or perhaps
> some matching function that split-string uses?
> What happens if you evaluate the following (just press C-x C-e after the
> closing paren or cut-and-paste the expression into the *scratch* buffer
> and press C-j)? What happens if you restart your emacs with -Q and
> evaluate the same expression? In my setup, I can evaluate the following
> with no errors:
>
> (split-string #("| id | Actor | Character
> |\n|+---+---|\n| 1 | Allan Alda
>| ``Hawkeye'' Benjamin Pierce |\n| 2 | Gary Burghoff | ``Radar''
> Walter O'Reilly |\n| 3 | Loretta Switt | ``Hotlips'' Margaret Hoolihan
> |\n" 0 2 nil 2 4 (org-label nil org-attributes nil org-caption nil fontified
> nil) 4 7 nil 7 12 (org-label nil org-attributes nil org-caption nil
> fontified nil) 12 23 nil 23 32 (org-label nil org-attributes nil org-caption
> nil fontified nil) 32 113 nil 113 114 (org-label nil org-attributes nil
> org-caption nil fontified nil) 114 117 nil 117 127 (org-label nil
> org-attributes nil org-caption n
Re: latex exporting strangeness [was: Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error]
Blank at start of file does not do it for me. On Mon, Mar 9, 2009 at 6:42 PM, Nick Dokos wrote: > [replying to my own mail] > > Nick Dokos wrote: > > > > > I said above that the export succeeds and it does, in the sense that I > > get no errors. However, the exported latex looks strange - the table > > comes *before* the "MASH" section. Is this a bug or is it a peculiarity > > of my configuration? Can somebody please try it and let me know? > > > > I seem to recall that this has come up before: basically, an empty line > at the beginning of the org file restores sanity. So even if it is a bug, > there is an easy workaround. > > Sorry for the noise, > Nick > > > > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error
andrew dasys wrote: > Nick, > thank you for looking at this. > > I am running Emacs 21.4.1 Nothing bleeding edge here. > > The help for split-string looks reasonable (compiled Lisp comes from "subr" > ) (complete output attached) > ... > split-string is a compiled Lisp function in `subr'. > (split-string STRING &optional SEPARATORS) > > Splits STRING into substrings where there are matches for SEPARATORS. > Each match for SEPARATORS is a splitting point. > The substrings between the splitting points are made into a list > which is returned. > If SEPARATORS is absent, it defaults to "[ \f\t\n\r\v]+". > > If there is match for SEPARATORS at the beginning of STRING, we do not > include a null substring for that. Likewise, if there is a match > at the end of STRING, we don't include a null substring for that. > > Modifies the match data; use `save-match-data' if necessary. I think that explains it: split-string takes one mandatory and two optional arguments (separator regexp and an omit-nulls boolean) in emacs-22/23; but only *one* optional argument in emacs-21 (the separator arg). The org latex-exporting code calls it with two optional arguments and that makes the emacs-21 implementation of split-string blow up. I just did an experiment: in my emacs-23, I called split-string with one mandatory and *three* more arguments: (split-string "foo bar baz" "\n" t t) and I got Debugger entered--Lisp error: (wrong-number-of-arguments #[(string &optional separators omit-nulls) " ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: latex exporting strangeness [was: Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error]
andrew dasys wrote: > Blank at start of file does not do it for me. > Yes, this is just a workaround for the funny ordering: it does not resolve the error you get (but I hope that the patch that I just posted will). Nick ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error
[I mangled the previous response, so let me try again.] andrew dasys wrote: > Nick, > thank you for looking at this. > > I am running Emacs 21.4.1 Nothing bleeding edge here. > > The help for split-string looks reasonable (compiled Lisp comes from "subr" > ) (complete output attached) > > > split-string is a compiled Lisp function in `subr'. > (split-string STRING &optional SEPARATORS) > > Splits STRING into substrings where there are matches for SEPARATORS. > Each match for SEPARATORS is a splitting point. > The substrings between the splitting points are made into a list > which is returned. > If SEPARATORS is absent, it defaults to "[ \f\t\n\r\v]+". > > If there is match for SEPARATORS at the beginning of STRING, we do not > include a null substring for that. Likewise, if there is a match > at the end of STRING, we don't include a null substring for that. > > Modifies the match data; use `save-match-data' if necessary. I think that explains it: split-string takes one mandatory and two optional arguments (separator regexp and an omit-nulls boolean) in emacs-22/23; but only *one* optional argument in emacs-21 (the separator arg). The org latex-exporting code calls it with two optional arguments and that makes the emacs-21 implementation of split-string blow up. I just did an experiment: in my emacs-23, I called split-string with one mandatory and *three* more arguments: (split-string "foo bar baz" "\n" t t) and I got output which looks very similar to what you are getting. So I think it's an incompatibility with emacs-21. Try the following patch for now and let us know whether it resolves your problem: diff --git a/lisp/org-export-latex.el b/lisp/org-export-latex.el index 0c0c87f..e8ef6d5 100644 --- a/lisp/org-export-latex.el +++ b/lisp/org-export-latex.el @@ -,7 +,10 @@ The conversion is made depending of STRING-BEFORE and STRING-AFTER." (string-match "\\http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Tables and Latex "Wrong-number-of-arguments" error
Fix, thanks, in particular to Nick for sorting this out. Andrew, I strongly suggest you upgrade to Emacs 22. - Carsten On Mar 10, 2009, at 3:12 AM, Nick Dokos wrote: [I mangled the previous response, so let me try again.] andrew dasys wrote: Nick, thank you for looking at this. I am running Emacs 21.4.1 Nothing bleeding edge here. The help for split-string looks reasonable (compiled Lisp comes from "subr" ) (complete output attached) split-string is a compiled Lisp function in `subr'. (split-string STRING &optional SEPARATORS) Splits STRING into substrings where there are matches for SEPARATORS. Each match for SEPARATORS is a splitting point. The substrings between the splitting points are made into a list which is returned. If SEPARATORS is absent, it defaults to "[ \f\t\n\r\v]+". If there is match for SEPARATORS at the beginning of STRING, we do not include a null substring for that. Likewise, if there is a match at the end of STRING, we don't include a null substring for that. Modifies the match data; use `save-match-data' if necessary. I think that explains it: split-string takes one mandatory and two optional arguments (separator regexp and an omit-nulls boolean) in emacs-22/23; but only *one* optional argument in emacs-21 (the separator arg). The org latex-exporting code calls it with two optional arguments and that makes the emacs-21 implementation of split-string blow up. I just did an experiment: in my emacs-23, I called split-string with one mandatory and *three* more arguments: (split-string "foo bar baz" "\n" t t) and I got output which looks very similar to what you are getting. So I think it's an incompatibility with emacs-21. Try the following patch for now and let us know whether it resolves your problem: diff --git a/lisp/org-export-latex.el b/lisp/org-export-latex.el index 0c0c87f..e8ef6d5 100644 --- a/lisp/org-export-latex.el +++ b/lisp/org-export-latex.el @@ -,7 +,10 @@ The conversion is made depending of STRING- BEFORE and STRING-AFTER." (string-match "\\http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
