Re: [Orgmode] org-cycle-item-indentation, org-use-sub-superscripts missed
Am 27.10.2010 20:11, schrieb Bastien: Andreas Röhlerandreas.roeh...@easy-emacs.de writes: BTW, is somewhere documented, how to load the devel-tree from emacs -Q? Assuming your devel-tree is in ~/install/git/org-mode/ you need to do a (require 'org) so that the devel version replaces the one loaded by Emacs. Thanks, loading devel now that way: (add-to-list 'load-path ~/org-mode/lisp/) (load /home/speck/org-mode/lisp/org-install.elc) (require 'org) (define-key org-mode-map [(super S)] 'show-entry) (define-key org-mode-map [(super s)] 'hide-entry)) BTW bug shows up again today at another place. Attach report below Emacs -Q org-table-convert-region: Symbol's value as variable is void: org-use-sub-superscripts release_7.01h-868-gafd23 Org-mode version 7.01trans (release_7.01h.868.gafd23) Emacs : GNU Emacs 23.1.1 (i586-suse-linux-gnu, GTK+ Version 2.20.1) of 2010-07-05 on build17 Package: Org-mode version 7.01trans (release_7.01h.868.gafd23) current state: == (setq org-file-apps '((auto-mode . emacs) (\\.x?html?\\' . default) (\\.pdf\\' . default)) org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars) org-link-frame-setup '((vm . vm-visit-folder-other-frame) (gnus . gnus-other-frame) (file . find-file-other-window)) org-structure-template-alist '((s #+begin_src ?\n\n#+end_src src lang=\?\\n\n/src) (e #+begin_example\n?\n#+end_example example\n?\n/example) (q #+begin_quote\n?\n#+end_quote quote\n?\n/quote) (v #+begin_verse\n?\n#+end_verse verse\n?\n/verse) (l #+begin_latex\n?\n#+end_latex literal style=\latex\\n?\n/literal) (L #+latex: literal style=\latex\?/literal) (h #+begin_html\n?\n#+end_html literal style=\html\\n?\n/literal) (H #+html: literal style=\html\?/literal) (a #+begin_ascii\n?\n#+end_ascii) (A #+ascii: ) (i #+include %file ? include file=%file markup=\?\)) org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-export-table-header-tags '(th . /th) org-export-html-inline-image-extensions '(png jpeg jpg gif) org-metaup-hook '(org-babel-load-in-session-maybe) org-after-todo-state-change-hook '(org-clock-out-if-current) org-export-latex-format-toc-function 'org-export-latex-format-toc-default org-export-table-data-tags '(td . /td) org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe) org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-confirm-shell-link-function 'yes-or-no-p org-export-first-hook '(org-beamer-initialize-open-trackers) org-format-latex-header \\documentclass{article}\n\\usepackage{fullpage} % do not remove\n\\usepackage{amssymb}\n\\usepackage[usenames]{color}\n\\usepackage{amsmath}\n\\usepackage{latexsym}\n\\usepackage[mathscr]{eucal}\n\\pagestyle{empty} % do not remove org-babel-pre-tangle-hook '(save-buffer) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link-modifiers) org-link-to-org-use-id 'create-if-interactive org-mode-hook '(#[nil \300\301\302\303\304$\207 [org-add-hook change-major-mode-hook org-show-block-all append local] 5] #[nil \300\301\302\303\304$\207 [org-add-hook change-major-mode-hook org-babel-show-result-all append local] 5] org-babel-result-hide-spec org-babel-hide-all-hashes) org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) org-emphasis-regexp-components '( ('\ - .,:?;'\) \n,\' . 1) org-confirm-elisp-link-function 'yes-or-no-p org-log-note-headings '((done . CLOSING NOTE %t) (state . State %-12s %t) (note . Note taken on %t) (clock-out . )) org-occur-hook '(org-first-headline-recenter) org-drawers '(PROPERTIES CLOCK) org-export-preprocess-before-selecting-backend-code-hook '(org-beamer-select-beamer-code) org-modules '(org-bbdb org-bibtex org-gnus org-info org-jsinfo org-irc org-mew org-mhe org-rmail org-vm org-w3m org-wl) org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc org-beamer-auto-fragile-frames org-beamer-place-default-actions-for-lists) org-metadown-hook '(org-babel-pop-to-session-maybe) ) Best regards, Andreas -- https://code.launchpad.net/~a-roehler/python-mode/python-mode-components https://code.launchpad.net/s-x-emacs-werkstatt/ ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list.
Re: [Orgmode] Beamer center frametitle and block?
Bruno Tavernier tavernier.br...@gmail.com writes: I search on Worg and in the info file but could not find if there is an option to select the position (left,center,right) of beamer's frametitle and block? I cannot help you with the block problem but I would suggest that the frametitle formatting is the responsibility of the beamer theme you have used and so maybe you simply need to change that theme? -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [PATCH] Alphabetical ordered lists
New patch fixing these issues is attached. Let me know of any other problems. On Tue, Oct 26, 2010 at 1:23 AM, Carsten Dominik carsten.domi...@gmail.com wrote: On Oct 26, 2010, at 10:21 AM, Nicolas Goaziou wrote: Hello, Nathaniel Flath writes: I think I've fixed the issues brought up with this new patch. Please let me know what you think. I've noticed a couple of glitches. First, you are using ( 28 (length struct)) to know when to replace letters by numbers. But (length struct) doesn't always match list length, so it will lead to errors when outdenting items. For example, try outdenting, with its subtree, the item marked with in the list below: a) etsiun b) etsiun c) etsiun d) etisun e) etsiun f) etsiun g) etsiun h) etsiun i) etisun j) etsiun k) etsiun l) etsiun m) etsiun n) etsiun a) Outdent me and my children ! a) tersiu b) etsiru c) estiur d) etsnriu e) etsiun f) etiune g) etuirsnet b) etsiun o) etsiun p) etsiun q) etsiun r) etsiun s) etsiun All the lists will be numbered although they could keep alphabetical bullets. Another (lesser) problem is coming from the regexp chosen for bullets, that is [0-9A-Za-z]+. I would suggest something alike \\(\\(?:[0-9]\\)+\\|[A-Za-z]\\). At the moment, you can set counter to [...@a4] and break you list when applying it. Also, even when the alpha lists are turned off, typing a) and pressing M-RET will show that a) is seen as a list bullet. Thanks for your work, we are getting closer to an acceptable patch. - Carsten Regards, -- Nicolas - Carsten ordered-list.patch Description: Binary data ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: General question on dealing with Latex to word conversion
Marvin Doyley marvin...@gmail.com writes: This is indeed a unique way of looking at the problem. I am not sure converting from word to Org is the way to go, because vast majority of my research notes are already in Org. But having said that a good work around could be to create a crude version in word (ditch the equations, but export as plain text), get everyone comments, and incorporate the changes in Org before exporting to latex This will try this in the initial stage of my next grant proposal. My workflow, when required to collaborate with Word (or OOo) users is to export org to HTML, use OOo to convert to Word and send that out. I ask my collaborators to /track changes/ in the Word document and I then manually incorporate these changes into my original org document. Not ideal but it does the job. However, what would be ideal would be if there were a tool which would take a Word document with /track changes/ and generate a patch file for a text version of that document... that could then provide some mechanism for getting changes back into an org document (modulo problems with line re-arrangements unfortunately). Just a pipe dream... -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: TaskJuggler 3, revisited
Hi Anthony Anthony Lander anthonylan...@yahoo.com writes: Is the unfamiliar idiom the backtick list with the ,variables in it, by chance? No it was more stuff like `return' and `return-from'. Ah, sorry. This I should have documented. The problem is that TJ3 fails to compile the file if there is a leaf node with no computable end date. TJ2 happily ignored the situation, but TJ3 throws an error. OK, I understand. I managed to slowly integrate (some of) your changes. It should now generate milestones for nodes that cannot be scheduled and are leaf nodes. So basically it should export valid code for tj3 if you set org-export-taskjuggler-target-version to 3.0. Of course the report definitions in the defcustom org-export-taskjuggler-default-reports are not compatible with tj3 so you will need to change these. I have (or I guess rather had) some fondness for recursive functions, so I re-implemented your leafiness function recursively. However I ran into problems with max-lisp-eval-depth and it appears that recursion is not encouraged in Emacs lisp (http://www.gnu.org/s/emacs/manual/html_node/elisp/Compilation-Tips.html#Compilation-Tips). So I guess it's back to iterative style. In any event, the TJ drawer is my attempt at a catch-all solution. It at least allows a user to use missing features without waiting for a development change. So for example, I personally will never use the accounting stuff, and would not be very motivated to add it to the exporter, but if someone needed it, they could put the required code in the TJ drawer, and they could still use the TJ exporter for their project instead of having to abandon org-mode entirely for one missing feature. I like the drawer stuff and will integrate it. Interesting thought. I very much like the idea that you can do other things with your org-file than export it to taskjuggler. For example, keep actual notes in the file, and export it to other formats like html or LaTeX, for purposes other than project planning. Absolutely, I agree. Being able to say no, this is not a task in the task tree would be very useful. I don't know how to do it nicely either (yet). Hm, no this is not possible right now. Why would you want to do this? Maybe we could just mark it as a comment and make the exporter honor comments. How about if we set up a git repository on github with the files, and then post the link on the mailing list? I set up a repo and pushed my changes to the code there (http://github.com/egli/org-mode). I think we should put your email, and this reply to the list as well. Yes, I almost forgot. Would you mind doing that? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [WISH] Org Importers
Eric However, what would be ideal would be if there were a tool which would take a Word document with /track changes/ and generate a patch file for a text version of that document... that could then provide some mechanism for getting changes back into an org document (modulo problems with line re-arrangements unfortunately). Just a pipe dream... If you allow me some liberty, the suggestion is in two parts 1. Word/Pdf/Latex-Org converter 2. Change tracking within Org For most of us who write or work with copious amount of text, (1) could really be useful. If it gains sufficient escape velocity it can land us in a far off galaxy. (2) could be useful but a bit far-fetched at the moment. I have suggested or hinted elsewhere (in a babel thread) the need for importing in to Org from other formats. Jambunathan K. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Title page for book latex export
I added a link to the Feedback section and another to ESR How To Ask Questions The Smart Way on the index page of http://orgmode.org Thanks everyone! Thank you for sharing, Bastien. I had never read that essay before. And it's exactly where I would expect to find it. Best, Jeff -- Jeffrey Horn Graduate Lecturer and PhD Student in Economics George Mason University (704) 271-4797 jh...@gmu.edu jrhorn...@gmail.com http://www.failuretorefrain.com/jeff/ ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Meetup/conference
Thanks for giving me an excuse to visit Hawaii! Actually, it would be a tough sell to me wife, if you can believe that! Jeff On Wed, Oct 27, 2010 at 8:08 PM, Thomas S. Dye t...@tsdye.com wrote: Aloha all, This might be wildly impractical for most of you, but I'd be happy to facilitate an Org-mode conference at Keauhou Beach Resort in Kona, Hawaii. I organized a conference there for 150 archaeologists a few years ago and the facilities were perfect for a group that size. I don't remember right now the minimum number needed for the group rate, but something around 50 sticks in my head. In addition to congenial meeting facilities, you will find: 1) Terrific sport fishing, 2) Magnificently restored traditional Hawaiian religious temples on the hotel grounds, 3) An active volcano, with lava flowing into the sea, and 4) Tours of the observatories on Mauna Kea. If we tentatively plan for the northern hemisphere winter a year from now that would be sufficient lead time to set up the conference. And as the days shorten and nights begin to freeze for many of you, the thought of a week in January or February in 27 degree Celsius sunshine might prove appealing. Of course, Hawai`i Island lacks Belgian beer and for many of you it is halfway around the world ... All the best, Tom ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode -- Jeffrey Horn Graduate Lecturer and PhD Student in Economics George Mason University (704) 271-4797 jh...@gmu.edu jrhorn...@gmail.com http://www.failuretorefrain.com/jeff/ ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Meetup/conference
On Oct 28, 2010, at 2:08 AM, Thomas S. Dye wrote: Aloha all, This might be wildly impractical for most of you, but I'd be happy to facilitate an Org-mode conference at Keauhou Beach Resort in Kona, Hawaii. I organized a conference there for 150 archaeologists a few years ago and the facilities were perfect for a group that size. I don't remember right now the minimum number needed for the group rate, but something around 50 sticks in my head. In addition to congenial meeting facilities, you will find: 1) Terrific sport fishing, 2) Magnificently restored traditional Hawaiian religious temples on the hotel grounds, 3) An active volcano, with lava flowing into the sea, and 4) Tours of the observatories on Mauna Kea. What a tempting proposal! Imaging a picture of 50 people with Org-mode T-Shirts in front of glowing Lava! I love Hawaii. I for one don't have the funds for traveling that far - but I do get to Hawaii very occasionally for observations. Will let you know when that happens next time! Cheers - Carsten If we tentatively plan for the northern hemisphere winter a year from now that would be sufficient lead time to set up the conference. And as the days shorten and nights begin to freeze for many of you, the thought of a week in January or February in 27 degree Celsius sunshine might prove appealing. Of course, Hawai`i Island lacks Belgian beer and for many of you it is halfway around the world ... All the best, Tom ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [WISH] Org Importers
Jambunathan, (2) could be useful but a bit far-fetched at the moment. Really? Lots of us track changes with git, sometimes by means of one of the Emacs interfaces for it like Magit. You may be thinking of some interface-level features which aren't available by this method, like the ability to annotate changes in the same place you make them, I suppose. But working this way has a lot of 'features' that track changes doesn't. Scot ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] 20101028_orgtexi_names.patch
diff --git a/doc/org.texi b/doc/org.texi index 54f52e2..7630830 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -1708,8 +1708,7 @@ unpredictable for you, configure the variables @table @kbd @tsubheading{Creation and conversion} -...@kindex C-c | -...@item C-c | +...@orgcmd{c-c |,org-table-create-or-convert-from-region} Convert the active region to table. If every line contains at least one TAB character, the function assumes that the material is tab separated. If every line contains a comma, comma-separated values (CSV) are assumed. @@ -1723,16 +1722,14 @@ table. But it's easier just to start typing, like @kbd{|Name|Phone|Age @key{RET} |- @key{TAB}}. @tsubheading{Re-aligning and field motion} -...@kindex C-c C-c -...@item C-c C-c +...@orgcmd{c-c C-c,org-table-create-or-convert-from-region} Re-align the table without moving the cursor. @c @orgcmd{TAB,org-cycle} Re-align the table, move to the next field. Creates a new row if necessary. @c -...@kindex s...@key{tab} -...@item s...@key{tab} +...@orgcmd{s-@key{TAB},org-shifttab} Re-align, move to previous field. @c @kindex @key{RET} ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] 20101028_orgtexi_names.patch
Am 28.10.2010 11:45, schrieb Andreas Röhler: ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode Sorry, just seeing an error inside. Please don't apply. Correct patch follows. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] 20101028_orgtexi_names.patch - (2)
diff --git a/doc/org.texi b/doc/org.texi index 54f52e2..7630830 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -1708,8 +1708,7 @@ unpredictable for you, configure the variables @table @kbd @tsubheading{Creation and conversion} -...@kindex C-c | -...@item C-c | +...@orgcmd{c-c |,org-table-create-or-convert-from-region} Convert the active region to table. If every line contains at least one TAB character, the function assumes that the material is tab separated. If every line contains a comma, comma-separated values (CSV) are assumed. @@ -1723,16 +1722,14 @@ table. But it's easier just to start typing, like @kbd{|Name|Phone|Age @key{RET} |- @key{TAB}}. @tsubheading{Re-aligning and field motion} -...@kindex C-c C-c -...@item C-c C-c +...@orgcmd{c-c C-c,org-ctrl-c-ctrl-c} Re-align the table without moving the cursor. @c @orgcmd{TAB,org-cycle} Re-align the table, move to the next field. Creates a new row if necessary. @c -...@kindex s...@key{tab} -...@item s...@key{tab} +...@orgcmd{s-@key{TAB},org-shifttab} Re-align, move to previous field. @c @kindex @key{RET} ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [WISH] Org Importers
Jambunathan K kjambunat...@gmail.com writes: Eric However, what would be ideal would be if there were a tool which would take a Word document with /track changes/ and generate a patch file for a text version of that document... that could then provide some mechanism for getting changes back into an org document (modulo problems with line re-arrangements unfortunately). Just a pipe dream... If you allow me some liberty, the suggestion is in two parts 1. Word/Pdf/Latex-Org converter 2. Change tracking within Org For most of us who write or work with copious amount of text, (1) could really be useful. If it gains sufficient escape velocity it can land us in a far off galaxy. (2) could be useful but a bit far-fetched at the moment. I'm not sure I understand. change tracking in org is trivial (git, mercurial, etc); it's extracting Word change tracking information in a form usable by other tools that is not trivial... eric ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [WISH] Org Importers
On 28 Oct 2010, at 11:15, Scot Becker wrote: Jambunathan, (2) could be useful but a bit far-fetched at the moment. Really? Lots of us track changes with git, sometimes by means of one of the Emacs interfaces for it like Magit. You may be thinking of some interface-level features which aren't available by this method, like the ability to annotate changes in the same place you make them, I suppose. But working this way has a lot of 'features' that track changes doesn't. We once thought of having some markup in our LaTeX files to track changes, offering annotations. If I recall correctly, we had a command \changed{old}{new}{comment}. You could leave out the new or old text part: newly added text would be \changed{}{bla bla}{this is new text!}, deleted text would be \changed{completely wrong}{}{what an idiot}. The command would render the old/new text differently (gray, strikethrough, blue, whatever) and add the comment as a margin note. Maybe something like this would be useful/feasible in Org? (not that I have a need for this -- we never implemented that command, either). Cheers, Peter.___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [Babel] Prefix for tangled files
Hello, Wanting to use Babel as much as possible, writing a lot of scripts that I tangle (and eventually share with others), I find that prefixing all tangled files shoud be a good habit in order to directly see which files (in dired) are the results of a tangling process. Of course, I can have this habit, but others (and colleagues) may not have it. Would it make sense to have an Org-Babel variable for such a prefix (defaulting to the empty string, and overridable per block, subtree, file, language, as for the rest)? Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org now fontifies code blocks
Thomas S. Dye t...@tsdye.com writes: On Sep 9, 2010, at 12:35 PM, Dan Davison wrote: Thomas S. Dye t...@tsdye.com writes: Hi Dan, Glad to know that Darlan's slowdown is fixed. No change here that I can tell. Now that I've had org-src-fontify- natively set to t for a while, I can see that the slowdown is proportional to the number and size of code blocks in the Org-mode file. It is most noticeable in a file with about 30 printed pages of a manuscript held in several dozen LaTeX code blocks, quite a bit less so in a file where the several dozen code blocks are short R routines. Hi Tom, I've used fontification in Org code blocks constantly for a couple of months now, and I do not agree that there are any editing or unfolding delays which should deter typical Org users from using fontified src blocks. In typical usage I do not experience any delays whatsoever (my blocks tend to be fewer than 100 lines in length). I have tested a file with 22000 lines containing two subtrees of 59 latex blocks each of length 190 lines. Opening the file takes perhaps 4 seconds as opposed to 1. And unfolding one of the 11,000 line subtrees for the first time sometimes takes 1-2 seconds. However, once the file is open and being used, folding and unfolding of blocks is snappy. Editing and fontification is immediate in the 190 line blocks. When editing in a 2088 line block, there is an almost 1 second delay for a fontified character to appear, which is no good at all -- but I think users of blocks of that size should be happy using C-c '. I do not get any fontification messages in the minibuffer. This is on a slow machine (an Intel atom netbook), with emacs23 and emacs24 running under linux. So even in my 22000 line file containing 190 line blocks, the delays are short and only occur when first opening and unfolding the file. However, users of very large src blocks should definitely use C-c ' for editing. FWIW, I see the org-src-fontification message while unfolding, [...] Could you post that message please (go to *Messages* buffer after unfolding and it should be there). I haven't put any messages in, but I think I know the message you mean and I think it is an Emacs message. [...] Yes, here is a portion of the message buffer: Searching for `makaainana.org' Automatic display of crossref information was turned on Fontifying org-src-fontification:latex-mode... (regexps.) Automatic display of crossref information was turned on [...] I believe the message comes from line 744 of org-src.el No, the message comes from core Emacs fontification code. I'm unsure why you are seeing these messages and I am not. Do you still see the behaviour/problems you reported above? Dan All the best, Tom even when the unfolded result doesn't show a code block. Later when a sub- tree is unfolded, the org-src-fontification message appears again, which makes me wonder if there is unnecessary work going on. All the best, Tom On Sep 9, 2010, at 3:02 AM, Darlan Cavalcante Moreira wrote: Thank you Dan, It is perfect now. No perceivable slowdown At Wed, 08 Sep 2010 13:41:51 -0400, Dan Davison wrote: Darlan Cavalcante Moreira darc...@gmail.com writes: Maybe my problem is not related to slow folding/unfolding behavior that you are getting, but if I set the org-src-tab-acts-natively variable to t the folding/unfolding of headlines becomes very slow for me. Thank you Darlan, I have just pushed a change that should make that better -- does that improve things? I did think there was something else going on (that was why I asked Tom for confirmation), but I didn't have time to investigate properly. The problem seems to be that, on a folded headline containing many blocks, `org-edit-src-find-region-and-lang' is actually quite slow to come up with the answer No, there's nothing for me to edit here. (try issuing M-x org-edit-src-code on a folded headline containing many blocks; I haven't understood this properly yet.) Dan In fact, I was thinking that I had the problem described here, but I just isolated the cause and in my case it was the org-src-tab-acts- natively variable that I had set to t in my .emacs file. -- Darlan At Tue, 7 Sep 2010 06:05:54 -1000, Thomas S. Dye t...@tsdye.com wrote: Hi Dan, Yes, I can confirm that (setq org-src-fontify-natively nil) makes unfolding snappy again. All the best, Tom On Sep 7, 2010, at 3:23 AM, Dan Davison wrote: Thomas S. Dye t...@tsdye.com writes: Aloha Dan, This is really nice. Thanks for shepherding it along. In some of my use cases there is a substantial delay when opening a large file and then unfolding sections with many source code blocks. Hi Tom, I think this is a good point and probably as you say a reason for turning it off by default. Org should be (and was!) lightweight by default. I haven't had time to profile things properly. Before we turn it
[Orgmode] Re: [WISH] Org Importers
Eric S Fraga ucec...@ucl.ac.uk writes: Jambunathan K kjambunat...@gmail.com writes: Eric However, what would be ideal would be if there were a tool which would take a Word document with /track changes/ and generate a patch file for a text version of that document... that could then provide some mechanism for getting changes back into an org document (modulo problems with line re-arrangements unfortunately). Just a pipe dream... If you allow me some liberty, the suggestion is in two parts 1. Word/Pdf/Latex-Org converter 2. Change tracking within Org For most of us who write or work with copious amount of text, (1) could really be useful. If it gains sufficient escape velocity it can land us in a far off galaxy. (2) could be useful but a bit far-fetched at the moment. I'm not sure I understand. change tracking in org is trivial (git, mercurial, etc); it's extracting Word change tracking information in a form usable by other tools that is not trivial... My intention was really to bring attention to the need for importers and how useful they could be. Looks like the thread is veering in another direction ... As for change tracking, I will have insightful things to say once I get to look at the details of how OpenDocument manages the same. Jambunathan K. eric ___ Emacs-orgmode mailing list Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [WISH] Org Importers
Jambunathan K kjambunat...@gmail.com writes: Eric S Fraga ucec...@ucl.ac.uk writes: I'm not sure I understand. change tracking in org is trivial (git, mercurial, etc); it's extracting Word change tracking information in a form usable by other tools that is not trivial... My intention was really to bring attention to the need for importers Ah, okay. Point taken! how useful they could be. Looks like the thread is veering in another direction ... as is often the case ;-) As for change tracking, I will have insightful things to say once I get to look at the details of how OpenDocument manages the same. Excellent. I look forward to it. Thanks. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Org now fontifies code blocks
Hi Tom, I've used fontification in Org code blocks constantly for a couple of months now, and I do not agree that there are any editing or unfolding delays which should deter typical Org users from using fontified src blocks. In typical usage I do not experience any delays whatsoever (my blocks tend to be fewer than 100 lines in length). Is Tom perhaps using OSX? I found absurd fontification delays on OSX for various things (*clock task select* was the worst, IIRC) until somebody advised me to (setq font-lock-verbose nil), and that fixed it completely. I don't think it's the actual fontification that's slow, I think it's the (message) that is telling you what it's doing. Jules ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Using capture to add plain text under a headline
Noorul Islam noorul at noorul.com writes: On Wed, Oct 27, 2010 at 4:13 PM, Axis axis at gmx.ch wrote: Hello, I'm having a struggle capturing a plain text item under a headline; it always gets added to the bottom of the file. List items or org entries can be stowed away properly without a problem, i.e. (e Event entry (file+headline ~/org/agenda.org Events) * %? %^T) works but (b Birthdays plain (file+headline ~/org/agenda.org Birthdays) %\\%(diary-anniversary %? mm dd yy) turns %d) doesn't. Any clues as to what might go wrong here or how else I could add a line of plain text to a headline? I am not able to understand what you are trying to convey. Can you provide some examples? Thanks and Regards Noorul ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode at gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode Hi Noorul, thanks for your quick reply. The lines of init.el code were actually meant to be examples. I have been trying to set up templates for the new org-capture function. I keep an agenda file with different headlines for events, birthdays etc. What I now would like to do is add birthdays using the capture mechanism as sexp-lines under the birthdays-headline of this agenda file. For events I don't use sexp entries but regular org-entries with a timestamp, which are filed away under the correct heading without a hitch. If I try to do the same with my sexp lines, - e.g. %\\%(diary-anniversary 10 2 1869) Mahatma Gandhi would be %d years old - (which apparently cannot be added as org entries in order to be still recognized as sexp expressions but have to be added as plain text), they always end up at the end of the file, rather than at the end of the headline. Hope this made things a little more clear. I'm currently using org-mode 7.01h on a windows machine by the way. Thanks, Toby ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [CONCERN] Orgmode version string
I have every reason to believe that upcoming version of Org would be tagged as 7.02. Earlier I had argued that version strings be version-to-list compatible. I would like to reiterate it. My real concern is that 7.02 would be deemed as equivalent to 7.2 internally by the versioning subsystem and this is likely to clash with user's point of view. A user would *definitely* assume 7.02 as different from 7.2 and in all probability swear that former is inferior to the later. Please confirm what I am saying by evalling this: #+begin_src emacs-lisp (version-list-= (version-to-list 7.02) (version-to-list 7.2)) #+end_src Ignore this mail if it is already taken care of. Needless to say, I have ELPA-tarballs in mind when I say this. Jambunathan K. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org now fontifies code blocks
Jules Bean ju...@jellybean.co.uk writes: Hi Tom, I've used fontification in Org code blocks constantly for a couple of months now, and I do not agree that there are any editing or unfolding delays which should deter typical Org users from using fontified src blocks. In typical usage I do not experience any delays whatsoever (my blocks tend to be fewer than 100 lines in length). Is Tom perhaps using OSX? I found absurd fontification delays on OSX for various things (*clock task select* was the worst, IIRC) until somebody advised me to (setq font-lock-verbose nil), and that fixed it completely. I don't think it's the actual fontification that's slow, I think it's the (message) that is telling you what it's doing. I wonder whether fontification messages are relics of the age long past when they served as modern equivalents of progress bars. ,[ C-h v font-lock-verbose RET ] | font-lock-verbose is a variable defined in `font-lock.el'. | Its value is 0 | | Documentation: | If non-nil, means show status messages for buffer fontification. | If a number, only buffers greater than this size have fontification messages. | | You can customize this variable. | | [back] ` Perhaps Emacs maintainers would be willing to change the default setting of this variable. Jules ___ Emacs-orgmode mailing list Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org now fontifies code blocks
Jambunathan K kjambunat...@gmail.com writes: Jules Bean ju...@jellybean.co.uk writes: Hi Tom, I've used fontification in Org code blocks constantly for a couple of months now, and I do not agree that there are any editing or unfolding delays which should deter typical Org users from using fontified src blocks. In typical usage I do not experience any delays whatsoever (my blocks tend to be fewer than 100 lines in length). Is Tom perhaps using OSX? I found absurd fontification delays on OSX for various things (*clock task select* was the worst, IIRC) until somebody advised me to (setq font-lock-verbose nil), and that fixed it completely. Thanks Jules. I think I must have read the same advice, and now that you mention it, I have that set to nil in my .emacs.org. I do see Tom's messages when I set it to t. Hopefully setting to nil results in a speed-up in OSX? I don't think it's the actual fontification that's slow, I think it's the (message) that is telling you what it's doing. Hi Jambunathan, I wonder whether fontification messages are relics of the age long past when they served as modern equivalents of progress bars. I think you may be right. ,[ C-h v font-lock-verbose RET ] | font-lock-verbose is a variable defined in `font-lock.el'. | Its value is 0 | | Documentation: | If non-nil, means show status messages for buffer fontification. | If a number, only buffers greater than this size have fontification messages. | | You can customize this variable. | | [back] ` Perhaps Emacs maintainers would be willing to change the default setting of this variable. That sounds like a sensible suggestion. Dan Jules ___ Emacs-orgmode mailing list Please 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 Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Accepted] [Orgmode] 20101028_orgtexi_names.patch - (2)
Patch 347 (http://patchwork.newartisans.com/patch/347/) is now Accepted. Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C4CC94AAB.2030908%40easy-emacs.de%3E Here is the original message containing the patch: Content-Type: text/plain; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Orgmode] 20101028_orgtexi_names.patch - (2) Date: Thu, 28 Oct 2010 15:04:27 - From: =?utf-8?q?Andreas_R=C3=B6hler_=3Candreas=2Eroehler=40easy-emacs=2Ede?= =?utf-8?q?=3E?= X-Patchwork-Id: 347 Message-Id: 4cc94aab.2030...@easy-emacs.de To: emacs-orgmode emacs-orgmode@gnu.org diff --git a/doc/org.texi b/doc/org.texi index 54f52e2..7630830 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -1708,8 +1708,7 @@ unpredictable for you, configure the variables @table @kbd @tsubheading{Creation and conversion} -...@kindex C-c | -...@item C-c | +...@orgcmd{c-c |,org-table-create-or-convert-from-region} Convert the active region to table. If every line contains at least one TAB character, the function assumes that the material is tab separated. If every line contains a comma, comma-separated values (CSV) are assumed. @@ -1723,16 +1722,14 @@ table. But it's easier just to start typing, like @kbd{|Name|Phone|Age @key{RET} |- @key{TAB}}. @tsubheading{Re-aligning and field motion} -...@kindex C-c C-c -...@item C-c C-c +...@orgcmd{c-c C-c,org-ctrl-c-ctrl-c} Re-align the table without moving the cursor. @c @orgcmd{TAB,org-cycle} Re-align the table, move to the next field. Creates a new row if necessary. @c -...@kindex s...@key{tab} -...@item s...@key{tab} +...@orgcmd{s-@key{TAB},org-shifttab} Re-align, move to previous field. @c @kindex @key{RET} ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [CONCERN] Orgmode version string
Jambunathan K kjambunat...@gmail.com writes: I have every reason to believe that upcoming version of Org would be tagged as 7.02. Earlier I had argued that version strings be version-to-list compatible. I would like to reiterate it. My real concern is that 7.02 would be deemed as equivalent to 7.2 internally by the versioning subsystem and this is likely to clash with user's point of view. A user would *definitely* assume 7.02 as different from 7.2 and in all probability swear that former is inferior to the later. Please confirm what I am saying by evalling this: #+begin_src emacs-lisp (version-list-= (version-to-list 7.02) (version-to-list 7.2)) #+end_src I confirm. Ignore this mail if it is already taken care of. Needless to say, I have ELPA-tarballs in mind when I say this. Another way is to make Emacs more liberal about version names. Can you suggest a new default for `version-regexp-alist' so that 7.01 is considered older than 7.10? (version-list-= (version-to-list 7.02) (version-to-list 7.2)) being t is not intuitive. -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Worg: link broken
Hello, In page http://orgmode.org/guide/Working-With-Source-Code.html, see further reading: link chapter 14 broken (recursive, BTW?). Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Hi, Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) Best -- Eric ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Eric Schulte schulte.e...@gmail.com writes: Hi, Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) If anyone missed it, there is also emacs-muse-slidy. http://www.flickr.com/photos/arciniegas/5108022392/ That is very impressive. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: blorgit build
Hi Ezequiel, Ezequiel Birman stormwa...@espiga4.com.ar writes: Thanks, it works now though I am not sure about the best way to load emacs. Nowadays I use 'emacsclient -c' and let it handle the process of starting the daemon but 1. Should I let org-interaction.el start the server from now on? (eg. by loading it in my .emacs) That's what I do. 2. Should I start another emacs instance just for blorgit? I tend to run it on a remote server, in which case I run it inside of gnu screen which allows for a persistent graphical session to Emacs even if I'm disconnected from the server. (see http://orgmode.org/worg/blorgit.php#sec-3_5) 3. Would it be convenient to create a new user to run this dedicated emacs instance and blorgit at system startup? Hmm, I could see that working. If you manage to put together a working setup along these lines it would be nice if you could add the instructions to the blorgit page on Worg. Best -- Eric ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [Babel] Installation notes for an app
#+TITLE: Installation Notes for an app #+LANGUAGE: en_US * Global constants ** Development #+tblname: dev-params | serverName | host1| | appBaseDir | /cygdrive/d/dir1 | ** Staging #+tblname: stg-params | serverName | host2| | appBaseDir | /cygdrive/d/dir2 | ** Production #+tblname: prd-params | serverName | host3| | appBaseDir | /cygdrive/d/dir3 | * Show the params :dev: ** Statically assigned #+begin_src sh :rownames no :var data=dev-params :exports both echo $data #+end_src #+results: : serverName host1 appBaseDir /cygdrive/d/dir1 ** Dynamically assigned Trying to be as adaptable as possible, I'll use the tag to refer to the right table: #+begin_src sh :rownames no :var data=(concat (car (org-get-tags-at (point))) -params) :exports both echo $data #+end_src #+results: : dev-params XXX I expected to see here the same results as in the [[*Statically%20assigned][previous version]]. PS- Instead of a tag, I could use as well some other sort of global constant. Right now, I do not see yet the respective gains or problems of both. I guess I'll do in the coming days. * Export the params To export the params to the shell, I can process the above string with AWK or some such. XXX Any advice on doing it better? Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org now fontifies code blocks
On Oct 28, 2010, at 1:10 AM, Dan Davison wrote: Thomas S. Dye t...@tsdye.com writes: On Sep 9, 2010, at 12:35 PM, Dan Davison wrote: Thomas S. Dye t...@tsdye.com writes: Hi Dan, Glad to know that Darlan's slowdown is fixed. No change here that I can tell. Now that I've had org-src-fontify- natively set to t for a while, I can see that the slowdown is proportional to the number and size of code blocks in the Org-mode file. It is most noticeable in a file with about 30 printed pages of a manuscript held in several dozen LaTeX code blocks, quite a bit less so in a file where the several dozen code blocks are short R routines. Hi Tom, I've used fontification in Org code blocks constantly for a couple of months now, and I do not agree that there are any editing or unfolding delays which should deter typical Org users from using fontified src blocks. In typical usage I do not experience any delays whatsoever (my blocks tend to be fewer than 100 lines in length). I have tested a file with 22000 lines containing two subtrees of 59 latex blocks each of length 190 lines. Opening the file takes perhaps 4 seconds as opposed to 1. And unfolding one of the 11,000 line subtrees for the first time sometimes takes 1-2 seconds. However, once the file is open and being used, folding and unfolding of blocks is snappy. Editing and fontification is immediate in the 190 line blocks. When editing in a 2088 line block, there is an almost 1 second delay for a fontified character to appear, which is no good at all -- but I think users of blocks of that size should be happy using C-c '. I do not get any fontification messages in the minibuffer. This is on a slow machine (an Intel atom netbook), with emacs23 and emacs24 running under linux. So even in my 22000 line file containing 190 line blocks, the delays are short and only occur when first opening and unfolding the file. However, users of very large src blocks should definitely use C-c ' for editing. FWIW, I see the org-src-fontification message while unfolding, [...] Could you post that message please (go to *Messages* buffer after unfolding and it should be there). I haven't put any messages in, but I think I know the message you mean and I think it is an Emacs message. [...] Yes, here is a portion of the message buffer: Searching for `makaainana.org' Automatic display of crossref information was turned on Fontifying org-src-fontification:latex-mode... (regexps.) Automatic display of crossref information was turned on [...] I believe the message comes from line 744 of org-src.el No, the message comes from core Emacs fontification code. I'm unsure why you are seeing these messages and I am not. Do you still see the behaviour/problems you reported above? Dan HI Dan, No, the slowness that I had with this on OS X is gone now. I think the key is this, as Jules Bean noted: #+begin_src emacs-lisp :tangle yes (setq font-lock-verbose nil) #+end_src This was set to 0 previously. Thanks for this improvement. It is great to see semantic markup in code blocks in the Org-mode buffer. Tom All the best, Tom even when the unfolded result doesn't show a code block. Later when a sub- tree is unfolded, the org-src-fontification message appears again, which makes me wonder if there is unnecessary work going on. All the best, Tom On Sep 9, 2010, at 3:02 AM, Darlan Cavalcante Moreira wrote: Thank you Dan, It is perfect now. No perceivable slowdown At Wed, 08 Sep 2010 13:41:51 -0400, Dan Davison wrote: Darlan Cavalcante Moreira darc...@gmail.com writes: Maybe my problem is not related to slow folding/unfolding behavior that you are getting, but if I set the org-src-tab-acts-natively variable to t the folding/unfolding of headlines becomes very slow for me. Thank you Darlan, I have just pushed a change that should make that better -- does that improve things? I did think there was something else going on (that was why I asked Tom for confirmation), but I didn't have time to investigate properly. The problem seems to be that, on a folded headline containing many blocks, `org-edit-src-find-region-and-lang' is actually quite slow to come up with the answer No, there's nothing for me to edit here. (try issuing M-x org-edit-src-code on a folded headline containing many blocks; I haven't understood this properly yet.) Dan In fact, I was thinking that I had the problem described here, but I just isolated the cause and in my case it was the org-src-tab-acts- natively variable that I had set to t in my .emacs file. -- Darlan At Tue, 7 Sep 2010 06:05:54 -1000, Thomas S. Dye t...@tsdye.com wrote: Hi Dan, Yes, I can confirm that (setq org-src-fontify-natively nil) makes unfolding snappy again. All the best, Tom On Sep 7, 2010, at 3:23 AM, Dan Davison wrote: Thomas S. Dye t...@tsdye.com writes: Aloha Dan, This is really nice. Thanks for shepherding it
[Orgmode] Re: Meetup/conference
Since we're talking about meet-ups, I'd like to say it would be great to see an informal org-mode meet-up attached to other conferences one might attend. Not as an alternative to the Hawaii proposal, but as an also. cheers, r ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Meetup/conference
On Oct 27, 2010, at 11:12 PM, Carsten Dominik wrote: On Oct 28, 2010, at 2:08 AM, Thomas S. Dye wrote: Aloha all, This might be wildly impractical for most of you, but I'd be happy to facilitate an Org-mode conference at Keauhou Beach Resort in Kona, Hawaii. I organized a conference there for 150 archaeologists a few years ago and the facilities were perfect for a group that size. I don't remember right now the minimum number needed for the group rate, but something around 50 sticks in my head. In addition to congenial meeting facilities, you will find: 1) Terrific sport fishing, 2) Magnificently restored traditional Hawaiian religious temples on the hotel grounds, 3) An active volcano, with lava flowing into the sea, and 4) Tours of the observatories on Mauna Kea. What a tempting proposal! Imaging a picture of 50 people with Org-mode T-Shirts in front of glowing Lava! I love Hawaii. I for one don't have the funds for traveling that far - but I do get to Hawaii very occasionally for observations. Will let you know when that happens next time! Cheers - Carsten If we tentatively plan for the northern hemisphere winter a year from now that would be sufficient lead time to set up the conference. And as the days shorten and nights begin to freeze for many of you, the thought of a week in January or February in 27 degree Celsius sunshine might prove appealing. Of course, Hawai`i Island lacks Belgian beer and for many of you it is halfway around the world ... All the best, Tom ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten Well, an org-mode conference without you wouldn't work at all. Consider my offer an open offer if you should change your mind. Perhaps you could cut and paste this in one of your agenda files? :) TODO Consider Org-mode conference in Hawaii SCHEDULED: 2011-01-03 Mon All the best, Tom ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] organizing =intra-day tasks= with a countdown timer
I wrote this a while back, and now I see that the manual describes a countdown timer. So now might be a good time. === We've discussed something like this before, but it seems there have been changes, so I am starting from scratch. Wondering how much of the functionality exists in Emacs or Org. I describe it in detail below. === Overview: === I'd like to keep =countdown timers= and get reminded at blastoff. This is a completely separate concept from clocking, effort estimates, and that org timer that inserts mm:ss, by the way. Here is a single example -- all 3 timers will run at the same time: 1) You just put the laundry in. You want a reminder to switch it in 30m. 2) You are also making tea right now. You want a reminder in 5m to drink it. 3) You are interviewing somebody at 6PM today. You want a reminder 15m before and at 6PM. Note that 1 and 2 are specified with a number of minutes, while 3 is specified with a time. Note that there is more than one timer at the same time. === Entry: === The interface should be simple, perhaps via capture, and definitely in the minibuffer. It's OK if it creates tasks. This would allow persistence and keep track of your activities. Appt-add can mostly do 3, but without keeping an Org task and without specifying duration (only target). Thus, you have to manually calculate the duration, which is a cognitive burden. For 3 you can add an Org task, set a time, and tell appt to show it. However, I don't know if there is a capture interface for all of that. I know of no mechanism for 1 and 2. === Output: === Ideally, you would be able to show a buffer that shows remaining duration, target time, and name of thing: |--+-+---+---| | status | target | remaining | task | |--+-+---+---| | reminded | 17:17 | -13m | tea | | -| /17:30/ | - | /now/ | | wait | 17:44 | 14m | laundry | | wait | 18:00 | 30m | interview | |--+-+---+---| I don't know if it makes sense to use agenda. And a timer in the modeline that can be switched between the currently clocked task display (whatever you are clocking in org, i.e. the usual count-up display) and the next item (in this case laundry in 14m). === OK, so how much of all this is possible these days? Thanks. Samuel ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [CONCERN] Orgmode version string
Hello Bastien Bastien bastien.gue...@wikimedia.fr writes: Jambunathan K kjambunat...@gmail.com writes: I have every reason to believe that upcoming version of Org would be tagged as 7.02. Earlier I had argued that version strings be version-to-list compatible. I would like to reiterate it. My real concern is that 7.02 would be deemed as equivalent to 7.2 internally by the versioning subsystem and this is likely to clash with user's point of view. A user would *definitely* assume 7.02 as different from 7.2 and in all probability swear that former is inferior to the later. Please confirm what I am saying by evalling this: #+begin_src emacs-lisp (version-list-= (version-to-list 7.02) (version-to-list 7.2)) #+end_src I confirm. Ignore this mail if it is already taken care of. Needless to say, I have ELPA-tarballs in mind when I say this. Another way is to make Emacs more liberal about version names. Can you suggest a new default for `version-regexp-alist' so that 7.01 is considered older than 7.10? I don't think I can sell this to emacs-devel with any success. It's not really worth it. I think I have made a sensible argument (or atleast recorded my opinion). I will leave things at that. (version-list-= (version-to-list 7.02) (version-to-list 7.2)) being t is not intuitive. Jambunathan K. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: organizing =intra-day tasks= with a countdown timer
I should point out that this is more a matter of getting the ideas posted than a feature request. On 2010-10-28, Samuel Wales samolog...@gmail.com wrote: I wrote this a while back, and now I see that the manual describes a countdown timer. So now might be a good time. === We've discussed something like this before, but it seems there have been changes, so I am starting from scratch. Wondering how much of the functionality exists in Emacs or Org. I describe it in detail below. === Overview: === I'd like to keep =countdown timers= and get reminded at blastoff. This is a completely separate concept from clocking, effort estimates, and that org timer that inserts mm:ss, by the way. Here is a single example -- all 3 timers will run at the same time: 1) You just put the laundry in. You want a reminder to switch it in 30m. 2) You are also making tea right now. You want a reminder in 5m to drink it. 3) You are interviewing somebody at 6PM today. You want a reminder 15m before and at 6PM. Note that 1 and 2 are specified with a number of minutes, while 3 is specified with a time. Note that there is more than one timer at the same time. === Entry: === The interface should be simple, perhaps via capture, and definitely in the minibuffer. It's OK if it creates tasks. This would allow persistence and keep track of your activities. Appt-add can mostly do 3, but without keeping an Org task and without specifying duration (only target). Thus, you have to manually calculate the duration, which is a cognitive burden. For 3 you can add an Org task, set a time, and tell appt to show it. However, I don't know if there is a capture interface for all of that. I know of no mechanism for 1 and 2. === Output: === Ideally, you would be able to show a buffer that shows remaining duration, target time, and name of thing: |--+-+---+---| | status | target | remaining | task | |--+-+---+---| | reminded | 17:17 | -13m | tea | | -| /17:30/ | - | /now/ | | wait | 17:44 | 14m | laundry | | wait | 18:00 | 30m | interview | |--+-+---+---| I don't know if it makes sense to use agenda. And a timer in the modeline that can be switched between the currently clocked task display (whatever you are clocking in org, i.e. the usual count-up display) and the next item (in this case laundry in 14m). === OK, so how much of all this is possible these days? Thanks. Samuel -- Q: How many CDC scientists does it take to change a lightbulb? A: You only think it's dark. [CDC has denied a deadly serious disease for 25 years] == Retrovirus: http://www.wpinstitute.org/xmrv/index.html -- PLEASE DONATE === I would like to see the original Lo et al. 2010 NIH/FDA/Harvard XMRV paper. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [PATCH] Fix typo
Signed-off-by: Julien Danjou jul...@danjou.info --- ORGWEBPAGE/Changes.org |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/ORGWEBPAGE/Changes.org b/ORGWEBPAGE/Changes.org index 549aed4..9a6b934 100644 --- a/ORGWEBPAGE/Changes.org +++ b/ORGWEBPAGE/Changes.org @@ -374,7 +374,7 @@ on Worg. *** Timer/clock enhancements -=org-timer-set-timer= displays a countdow timer in the modeline. +=org-timer-set-timer= displays a countdown timer in the modeline. From the agenda, `J' invokes =org-agenda-clock-goto=. * Version 7.01 -- 1.7.2.3 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Eric Schulte schulte.e...@gmail.com writes: Hi, Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) I think (require 'org-exp) is required. Looks like it walks you through the headline one at a time and presents the entry contents as such. When I get to the equations slide what should I expect to see? The equation fully rendered (as in text books) or just the markup (as it is literally typed). Jambunathan K. Best -- Eric ___ Emacs-orgmode mailing list Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [CONCERN] Orgmode version string
Bastien Can you suggest a new default for `version-regexp-alist' so that 7.01 is considered older than 7.10? I assume there is a typo here. Just for the sake of clarification: (version-list-= (version-to-list 7.01) (version-to-list 7.1)) is t (version-list- (version-to-list 7.01) (version-to-list 7.10)) is t Note that the following difference in above expressions 1. '=' and '' 2. 7.1 and 7.10 Jambunathan K ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Clock report (R from the agenda)
Sébastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Hello, Here is a minimal example for comments about the agenda filtering applied on the clock report of logged activities. * Work :work: :PROPERTIES: :CATEGORY: Work :END: ** Client A *** DONE Work on offer :LOGBOOK: CLOCK: [2010-09-30 Thu 09:12]--[2010-09-30 Thu 12:35] = 3:23 :END: ** Client B *** DONE Developed SQL scripts :LOGBOOK: CLOCK: [2010-09-30 Thu 13:20]--[2010-09-30 Thu 18:06] = 4:46 :END: * Personal :home: :PROPERTIES: :CATEGORY: Personal :END: ** DONE Lunch with Mary :LOGBOOK: CLOCK: [2010-09-30 Thu 19:49]--[2010-09-30 Thu 21:55] = 2:06 :END: * Clock report ** Without tag filtering Commands: - C-c a a :: Show the agenda. - v d :: Switch to day view. - b :: Go backward in time to display yesterday. - l :: Toggle Logbook mode. - R :: Toggle Clockreport mode. Results: :8:00-09:00 : Work:9:12-12:35 Clocked: (3:23) DONE Work on offer :work:: : 10:00-11:00 : 12:00-13:00 : Work: 13:20-18:06 Clocked: (4:46) DONE Developed SQL scripts :work:: : 14:00-15:00 : 16:00-17:00 : 18:00-19:00 : Personal: 19:49-21:55 Clocked: (2:06) DONE Lunch with Mary :home:: : 20:00-21:00 : 22:00-23:00 : : | File | L | Headline | Time| | : |--+---+--+-+--| : | | | *Total time* | *10:15* | | : |--+---+--+-+--| : | Clock-Report.org | | *File time* | *10:15* | | : | Clock-Report.org | 1 | Work | 8:09| | : | Clock-Report.org | 2 | Client A | | 3:23 | : | Clock-Report.org | 2 | Client B | | 4:46 | : | Clock-Report.org | 1 | Personal | 2:06| | : | Clock-Report.org | 2 | DONE Lunch with Mary | | 2:06 | ** With tag filtering Command: - / w :: filter on tag work (w). Results: :8:00-09:00 : Work:9:12-12:35 Clocked: (3:23) DONE Work on offer :work:: : 10:00-11:00 : 12:00-13:00 : Work: 13:20-18:06 Clocked: (4:46) DONE Developed SQL scripts :work:: : 14:00-15:00 : 16:00-17:00 : 18:00-19:00 : 20:00-21:00 : 22:00-23:00 : : | File | L | Headline | Time| | : |--+---+--+-+--| : | | | *Total time* | *10:15* | | : |--+---+--+-+--| : | Clock-Report.org | | *File time* | *10:15* | | : | Clock-Report.org | 1 | Work | 8:09| | : | Clock-Report.org | 2 | Client A | | 3:23 | : | Clock-Report.org | 2 | Client B | | 4:46 | : | Clock-Report.org | 1 | Personal | 2:06| | : | Clock-Report.org | 2 | DONE Lunch with Mary | | 2:06 | I don't see anymore the lines that have nothing to do with my job. Though, I still see the associated time in the clock report under... Regenerating it (by disabling it and re-enabling it) does not change anything: still there. For sure, this can _not_ be considered as a bug. Nobody never said this should work like I (now) expect. Though, I guess such a feature would be benefitial for everybody -- as I don't see any reason for having the tag filtering only work with the diary view, and not with the clock report under. Best regards, Seb Hi Sebastien, I personally use the clock report for _today_ often and I want it to include all of the time, even if I am filtering tasks on today's agenda. If this behaviour was to change I would like an option to keep it the way it is now. I can see cases where I would want to filter the clock report by tags as well so I think having an option for both would be useful. Regards, Bernt ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Richard Riley rile...@googlemail.com writes: Eric Schulte schulte.e...@gmail.com writes: Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. [...] http://github.com/eschulte/epresent (instructions in the README) If anyone missed it, there is also emacs-muse-slidy. http://www.flickr.com/photos/arciniegas/5108022392/ That is very impressive. Not bad. But there is org-s5 too. http://github.com/sigma/org-s5 -- Miłego dnia, Łukasz Stelmach ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Hi Eric, Eric Schulte wrote: Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) Just a typo in README: present.org, instead of presentation.org. Quite promising for the rest, really! Thanks once again, for all add-ons you provide us with... On the glitches side: - some titles are truncated because of their size - I did not see any image - Beamer's frame level is not supported (ending up with a couple of really long slides) - having to scroll within a slide seems to edit the Org file somehow - edited Org file is not undo-able because of visibility troubles - error outline-back-to-heading: before first heading But, once again, it gives a lot of hope to get right to the point of loosing a less time as possible, and lets us work on the contents of our file. Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Eric Schulte schulte.e...@gmail.com writes: Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. [...] http://github.com/eschulte/epresent (instructions in the README) I am preparing a talk about org-mode. I've decided to use org-s5 but I'm starting to hesitate :-) -- Miłego dnia, Łukasz Stelmach ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: organizing =intra-day tasks= with a countdown timer
Samuel Wales samolog...@gmail.com writes: 2) You are also making tea right now. You want a reminder in 5m to drink it. So true ;-) ICRBIDWT[*] -- Miłego dnia, Łukasz Stelmach [*] I could refrain but I didn't want to ;-) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [Babel] Bug with org-src-fontify-natively... after running epresent
Hello Eric, After having run epresent, I got this error when trying to publish my theme-test.org file (sent on this list a couple of days ago -- no reaction BTW ;-)). --8---cut here---start-8--- Debugger entered--Lisp error: (void-function -mode) -mode() funcall(-mode) (if (eq major-mode lang-mode) nil (funcall lang-mode)) (unless (eq major-mode lang-mode) (funcall lang-mode)) (save-current-buffer (set-buffer (get-buffer-create ...)) (delete-region (point-min) (point-max)) (insert string) (unless (eq major-mode lang-mode) (funcall lang-mode)) (font-lock-fontify-buffer) (setq pos (point-min)) (while (setq next ...) (put-text-property ... ... ... ... org-buffer) (setq pos next))) (with-current-buffer (get-buffer-create (concat org-src-fontification: ...)) (delete-region (point-min) (point-max)) (insert string) (unless (eq major-mode lang-mode) (funcall lang-mode)) (font-lock-fontify-buffer) (setq pos (point-min)) (while (setq next ...) (put-text-property ... ... ... ... org-buffer) (setq pos next))) (let* ((lang-mode ...) (string ...) (modified ...) (org-buffer ...) pos next) (remove-text-properties start end (quote ...)) (with-current-buffer (get-buffer-create ...) (delete-region ... ...) (insert string) (unless ... ...) (font-lock-fontify-buffer) (setq pos ...) (while ... ... ...)) (add-text-properties start end (quote ...)) (set-buffer-modified-p modified)) org-src-font-lock-fontify-block( 1227 1500) (cond ((and lang org-src-fontify-natively) (org-src-font-lock-fontify-block lang block-start block-end)) (quoting (add-text-properties beg1 ... ...)) ((not org-fontify-quote-and-verse-blocks)) ((string= block-type quote) (add-text-properties beg1 end1 ...)) ((string= block-type verse) (add-text-properties beg1 end1 ...))) (progn (setq end (match-end 0) end1 (1- ...)) (setq block-end (match-beginning 0)) (when quoting (remove-text-properties beg end ...)) (add-text-properties beg end (quote ...)) (add-text-properties beg beg1 (quote ...)) (add-text-properties end1 (+ end 1) (quote ...)) (cond (... ...) (quoting ...) (...) (... ...) (... ...)) t) (if (re-search-forward (concat ^[]*#\\+end ... \\.*) nil t) (progn (setq end ... end1 ...) (setq block-end ...) (when quoting ...) (add-text-properties beg end ...) (add-text-properties beg beg1 ...) (add-text-properties end1 ... ...) (cond ... ... ... ... ...) t)) (when (re-search-forward (concat ^[ ]*#\\+end ... \\.*) nil t) (setq end (match-end 0) end1 (1- ...)) (setq block-end (match-beginning 0)) (when quoting (remove-text-properties beg end ...)) (add-text-properties beg end (quote ...)) (add-text-properties beg beg1 (quote ...)) (add-text-properties end1 (+ end 1) (quote ...)) (cond (... ...) (quoting ...) (...) (... ...) (... ...)) t) (cond ((member dc1 ...) (org-remove-flyspell-overlays-in ... ...) (remove-text-properties ... ... ...) (add-text-properties ... ... ...) (add-text-properties ... ... ...) t) ((and ... ...) (setq block-type ... quoting ...) (when ... ... ... ... ... ... ... ... t)) ((member dc1 ...) (add-text-properties beg ... ...) (add-text-properties ... ... ...)) ((not ...) (add-text-properties beg ... ...) t) ((or ... ...) (add-text-properties beg ... ...) t) ((member dc3 ...) (add-text-properties beg ... ...)) (t nil)) (let ((beg ...) (block-start ...) (block-end nil) (lang ...) (beg1 ...) (dc1 ...) (dc3 ...) end end1 quoting block-type) (cond (... ... ... ... ... t) (... ... ...) (... ... ...) (... ... t) (... ... t) (... ...) (t nil))) (if (re-search-forward ^\\([ ]*#\\+\\(\\([a-zA-Z]+:?\\| \\|$\\)\\(_\\([a-zA-Z]+\\)\\)?\\)[ ]*\\(\\([^ \n]*\\)[ ]*\\(.*\\)\\)\\) limit t) (let (... ... ... ... ... ... ... end end1 quoting block-type) (cond ... ... ... ... ... ... ...))) (let ((case-fold-search t)) (if (re-search-forward ^\\([ ]*#\\+\\(\\([a-zA-Z]+:?\\| \\|$\\)\\(_\\([a-zA-Z]+\\)\\)?\\)[ ]*\\(\\([^ \n]*\\)[]*\\(.*\\)\\)\\) limit t) (let ... ...))) org-fontify-meta-lines-and-blocks(2136) #[(start end optional loudly) ...@\306=\204 \307! \211AA)\310 \311\312 \313\211\211'()*)\203+\...@ \314\315(\316'T\211'\317\#\210)@\2...@,b\210`-W\203\373\f;\203` \320\f-\306#\202d \f-!\203\373`\311\224V\204q \321u\210\203\241 `\212\311\224b\210\321y\210`)Y\203\241 \322`\212\311\224b\210\321y\210`)U\203\232 `S\202\234 \311\224`\323\306$\210 A\211\203K @@\247\203...@\211.@\211/\224,/\225-\324.80,\204\334 \325.8\206x\326\327/.#\202x\330...@!\2111\242\331=\203\332,-1\211AA)#\2101\211A@)11\2040\306=\204\313\202w0\204.\333,-\331\313$\206w\322,-\3311$\202w0\306=\203A\322,-\3311$\202w0\334=\203T\335,-\3311$\202w0\336=\203g\337,-\3311$\202w0\340=\205w\341,-\3311$),\210)\202\364`\313\223\2...@-2\211)@\325)\233\313\311\224\330)a...@!3453\247\203\2603`v\204\267\342
Re: [Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Eric, This is cool and very useful. Thanks. This must be Zeitgeist-y because I was thinking about preparing presentations in Emacs this week. Then I saw slidy, now this and s5. Here's a further idea, to see what people think. Do you think it would be possible to make a temporary org-mode display configuration to display org-mode-written presentations (similar to epresent) without leaving org mode, and leaving the displayed slides editable? I once saw a video of someone doing a live presentation on something Emacs-y and he did the presentation by typing headlines, lists and detail in a clean Emacs buffer as he went along, similar to the way that some teachers might write out subject headings or outlines on the chalkboard or overhead projector as they lecture. I liked this a lot. As I see it, for less formal presentation situations, it lets you annotate and record class discussions discussions. It also lets the talk proceed in a less scripted manner: you can for example re-work the problem on the fly according to the way the group has defined it in the moment, not only according to the way you planned it at home. But doing it on the fly means that you don't have any of the advantages of typical slide-style presentations: an outline to prompt you, important figures, tables and visuals already there, links, detail, and the rest, pre-assembled. I've wondered whether org mode might not be a nice vehicle to combine these things. For example, you create your script (just like in Eric's ' present.org'), but instead of showing in a custom display mode, you actually tweak the display parameters of org-mode itself to look slide-like (no stars, bigger fonts for titles, invisible /markup characters/, etc.), and then display the slides by displaying each top level subtree in a narrowed buffer one at a time. You add key bindings for moving back and forth, even perhaps a temporary minor mode for single key frame navigation that you could go in and out of (vi-like, I suppose). This way you'd be in (a slightly modified) org mode all the time, and could edit as you go, using all the structural features of org mode, and at the end you'd have a neat record of the way the lecture actually went, that you could distribute as you wish. Can anyone think why this might not be doable? Scot 2010/10/28 Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl Eric Schulte schulte.e...@gmail.com writes: Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. [...] http://github.com/eschulte/epresent (instructions in the README) I am preparing a talk about org-mode. I've decided to use org-s5 but I'm starting to hesitate :-) -- Miłego dnia, Łukasz Stelmach ___ Emacs-orgmode mailing list Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [WISH] Org Importers
Peter Frings peter.fri...@agfa.com writes: We once thought of having some markup in our LaTeX files to track changes, offering annotations. If I recall correctly, we had a command \changed{old}{new}{comment}. You could leave out the new or old text part: newly added text would be \changed{}{bla bla}{this is new text!}, deleted text would be \changed{completely wrong}{}{what an idiot}. The command would render the old/new text differently (gray, strikethrough, blue, whatever) and add the comment as a margin note. There is actually a latex implementation of something like this in the =changes= package that comes with texlive (at least)! This package has commands like \added and \deleted as well. There is also the =changebar= package which draws change bars in the margin. I've used both in the past but found them too cumbersome. I prefer simply relying on version control systems (git etc.). -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Internal links in LaTeX export
Hi Thomas, Thomas S. Dye wrote: The manual is silent about what happens to external links on export to LaTeX. I'm finding that internal links export to HTML and work as expected there. In the pdf file via LaTeX the internal links are colored, but aren't active. Is this the expected behavior or am I possibly doing something that disables the links on their way to pdf? Internal links always worked for me in PDF, though they more tend(ed) to go to the page rather than really placing me on the section (like what you have in your browser). Questions: - Which PDF reader do you use? That could influence... - Do you want me to test some example file? If yes, send it here, or privately to me -- attention for delays due to spammotel, though. Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Eric Schulte schulte.e...@gmail.com writes: Hi, Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) Best -- Eric This is brilliant! Sure, it isn't going to replace beamer for me but for quick and dirty presentations, this will be very very useful. It seems to work very well out of the box (for me). I haven't tried an image yet but the latex definitely works well. Thanks, eric PS - I'll be tracking that git repository! -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Internal links in LaTeX export
On Oct 28, 2010, at 10:18 AM, Sébastien Vauban wrote: Hi Thomas, Thomas S. Dye wrote: The manual is silent about what happens to external links on export to LaTeX. I'm finding that internal links export to HTML and work as expected there. In the pdf file via LaTeX the internal links are colored, but aren't active. Is this the expected behavior or am I possibly doing something that disables the links on their way to pdf? Internal links always worked for me in PDF, though they more tend(ed) to go to the page rather than really placing me on the section (like what you have in your browser). Questions: - Which PDF reader do you use? That could influence... - Do you want me to test some example file? If yes, send it here, or privately to me -- attention for delays due to spammotel, though. Best regards, Seb Thanks Seb, It doesn't appear to be a reader problem. The links fail in skim and acrobat. I'm getting this in the LaTeX output: \href{sec-2_5}{package loading part} If I read the hyperref documentation correctly, then I think it should be: \hyperref[sec-2_5]{package loading part} If I'm right about what the link should look like in LaTeX, and there is no obvious reason why I'm not getting it in the LaTeX export, then I'll work on finding a minimal example. All the best, Tom ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Internal links in LaTeX export
Thomas S. Dye t...@tsdye.com writes: On Oct 28, 2010, at 10:18 AM, Sébastien Vauban wrote: Hi Thomas, Thomas S. Dye wrote: The manual is silent about what happens to external links on export to LaTeX. I'm finding that internal links export to HTML and work as expected there. In the pdf file via LaTeX the internal links are colored, but aren't active. Is this the expected behavior or am I possibly doing something that disables the links on their way to pdf? Internal links always worked for me in PDF, though they more tend(ed) to go to the page rather than really placing me on the section (like what you have in your browser). Questions: - Which PDF reader do you use? That could influence... - Do you want me to test some example file? If yes, send it here, or privately to me -- attention for delays due to spammotel, though. Best regards, Seb Thanks Seb, It doesn't appear to be a reader problem. The links fail in skim and acrobat. I'm getting this in the LaTeX output: \href{sec-2_5}{package loading part} If I read the hyperref documentation correctly, then I think it should be: \hyperref[sec-2_5]{package loading part} If I'm right about what the link should look like in LaTeX, and there is no obvious reason why I'm not getting it in the LaTeX export, then I'll work on finding a minimal example. Play with this (for now). ,[ C-h v org-export-latex-hyperref-format RET ] | org-export-latex-hyperref-format is a variable defined in `org-latex.el'. | Its value is \\href{%s}{%s} | | Documentation: | A printf format string to be applied to hyperref links. | The format must contain two %s instances. The first will be filled with | the link, the second with the link description. | | You can customize this variable. ` This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. All the best, Tom ___ Emacs-orgmode mailing list Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Internal links in LaTeX export
On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote: Thomas S. Dye t...@tsdye.com writes: On Oct 28, 2010, at 10:18 AM, Sébastien Vauban wrote: Hi Thomas, Thomas S. Dye wrote: The manual is silent about what happens to external links on export to LaTeX. I'm finding that internal links export to HTML and work as expected there. In the pdf file via LaTeX the internal links are colored, but aren't active. Is this the expected behavior or am I possibly doing something that disables the links on their way to pdf? Internal links always worked for me in PDF, though they more tend(ed) to go to the page rather than really placing me on the section (like what you have in your browser). Questions: - Which PDF reader do you use? That could influence... - Do you want me to test some example file? If yes, send it here, or privately to me -- attention for delays due to spammotel, though. Best regards, Seb Thanks Seb, It doesn't appear to be a reader problem. The links fail in skim and acrobat. I'm getting this in the LaTeX output: \href{sec-2_5}{package loading part} If I read the hyperref documentation correctly, then I think it should be: \hyperref[sec-2_5]{package loading part} If I'm right about what the link should look like in LaTeX, and there is no obvious reason why I'm not getting it in the LaTeX export, then I'll work on finding a minimal example. Play with this (for now). ,[ C-h v org-export-latex-hyperref-format RET ] | org-export-latex-hyperref-format is a variable defined in `org- latex.el'. | Its value is \\href{%s}{%s} | | Documentation: | A printf format string to be applied to hyperref links. | The format must contain two %s instances. The first will be filled with | the link, the second with the link description. | | You can customize this variable. ` This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. Aloha Jambunathan K., Very many thanks for this information. I have Org-mode version 7.01trans (release_7.01h.880.g7531f). I take it the problem I'm having is due to a relatively recent change to Org-mode. If there is anything I can do to help isolate the problem, please let me know. All the best, Tom ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] TikZ to separate file (babel?) possible?
On Tue, Oct 26, 2010 at 6:01 PM, Eric Schulte schulte.e...@gmail.comwrote: Hi, First my previously pasted :exports code will throw errors on interactive evaluation (i.e. when not exporting), this alternative should be more robust. :exports (if (and (boundp 'latexp) latexp) code results) As for placing latex headers in a latex code block, I don't believe that is currently possible. I do agree it would be nice for latex code blocks to inherit latex headers from the containing Org-mode buffer but that would be a non-trivial piece of development, which I just don't have time for at the moment. I've just added a :headers argument which should allow changing things like fonts that need to take place in the headers portion of the latex file. See the following examples, passing both a single header and a list of headers. --8---cut here---start-8--- #+begin_src latex :headers \usepackage{lmodern} :file name1.pdf Eric Schulte #+end_src #+results: [[file:name1.pdf]] #+begin_src latex :headers '(\\usepackage{mathpazo} \\usepackage{fullpage}) :file name2.pdf Eric Schulte #+end_src #+results: [[file:name2.pdf]] --8---cut here---end---8--- Please pull this down and let me know if it works for you. Just pulled, make clean make make doc make install. Tried it and I get the default font for the first and Palatino for the second, but the lmodern is not appearing to change what's going on. I tried what usually works for me: \renewcommand{\rmdefault}{cmss} and this did not work to make it sans serif. Am I doing something wrong? Thanks, John Best -- Eric John Hendy jw.he...@gmail.com writes: Maybe it would just be easier if someone attached a .org file that functions as you think would work well -- with both the document and the babel/TikZ export having the same sans-serif font. Perhaps then I could simply C-e p the document and C-c C-c the babel block myself to examine how it behaves? I was not able to get the conditional :export code provided to work. Thanks, John On Tue, Oct 26, 2010 at 9:34 AM, John Hendy jw.he...@gmail.com wrote: On Tue, Oct 26, 2010 at 3:17 AM, Eric S Fraga ucec...@ucl.ac.uk wrote: On Mon, 25 Oct 2010 13:58:41 -0500, John Hendy jw.he...@gmail.com wrote: [1 text/plain; ISO-8859-1 (7bit)] [2 text/html; ISO-8859-1 (quoted-printable)] On Mon, Oct 25, 2010 at 1:53 PM, Eric Schulte schulte.e...@gmail.com wrote: Hi John, In the case you describe I would export the *code* of the tikz latex block rather than the file resulting from evaluating the block. Code = raw LaTeX/TikZ code? If so, I don't really care about that. i just want the graphic. Yes but the point is that, if I understand the processes involved correctly, the export and babel routes each generate different latex code. Babel does *not* look at the document wide settings whereas export does. This is why Eric is suggesting you export the babel code so that it is interpreted by the latex document that results from exporting the whole org document. Otherwise, make sure the settings you want are within the latex source code block? That makes more sense, though if I export the code into the larger LaTeX document, I'm left where I started, I believe. An 8.5x11 exported PDF with my diagram in the middle of it. If it's just getting the right code into the babel block, that's helpful to know. Perhaps the easiest way to put it is this: what is the best path to obtain the following: - a single pdf output of my TikZ diagram, cropped to fit the diagram - the font used in the TikZ diagram that I desire (preferably from the doc) Again, my use-case is one in which I have daily notes or a paper with a diagram but also would like to preserve the diagram for reuse. With babel, it appears this should be possible -- I can both export normally and have the graphic in the paper or send the TikZ section alone to export and use the graphic in a presentation or elsewhere. I wondered about what you said re. putting the settings in the latex source code block, and I was actually fiddling around with that yesterday. My font is simply set like so (present in the examples I posted earlier): #+latex_header: \usepackage{lmodern} #+latex_header: \renewcommand{\rmdefault}{cmss} But I tried putting variations of this in the babel block (without the #+latex_header part, of course) with no success. These didn't work for me: #+begin_src latex :file flow-chart.pdf :packages '(( tikz)) :border 1em \usepackage{lmodern} \renewcommand{\rmdefault}{cmss} or #+begin_src latex :file flow-chart.pdf :packages '(( tikz lmodern)) :border 1em \renewcommand{\rmdefault}{cmss} or #+begin_src latex :file flow-chart.pdf :packages '(( tikz lmodern)) :border 1em
Re: [Orgmode] TikZ to separate file (babel?) possible?
Eric, Just retried and was able to get it to work. Perhaps someone should add this to the ob-doc-latex page? For reference, I tried each of the following: Works: 1) #+begin_src latex :headers \renewcommand{\rmdefault}{cmss} Doesn't work: 2) #+begin_src latex :headers '(\\renewcommand{\rmdefault}{cmss}) Works: 3) #+begin_src latex :headers '(\\usepackage{mathpazo}) Which was puzzling me about #2 which led me to try: Works: 4) Doesn't work: 2) #+begin_src latex :headers '(\\renewcommand{\\rmdefault}{cmss}) Note the second double backslash before rmdefault. That escape character was necessary there, too. Thanks for the help on this!! It's *perfect*. John ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Scot Becker scot.bec...@gmail.com writes: I once saw a video of someone doing a live presentation on something Emacs-y and he did the presentation by typing headlines, lists and detail in a clean Emacs buffer as he went along, similar to the way that some teachers might write out subject headings or outlines on the chalkboard or overhead projector as they lecture. I liked this a lot. As I see it, for less formal presentation situations, it lets you annotate and record class discussions discussions. It also lets the talk proceed in a less scripted manner: you can for example re-work the problem on the fly according to the way the group has defined it in the moment, not only according to the way you planned it at home. But doing it on the fly means that you don't have any of the advantages of typical slide-style presentations: an outline to prompt you, important figures, tables and visuals already there, links, detail, and the rest, pre-assembled. I usually do something in-between this at my talks: I just have an orgmode file that I typed up a brief outline of my talk that I plan to give inside, along with src code snippets, links, whatever. This often works well for a highly technical audience I find. However, yeah, I've also been interested in a less nerdy presentation route myself... s5? One of these others? There seem to be a lot of good options these days. :) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [CONCERN] Orgmode version string
Hi Jambunathan, On Oct 28, 2010, at 2:40 PM, Jambunathan K wrote: I have every reason to believe that upcoming version of Org would be tagged as 7.02. Earlier I had argued that version strings be version-to-list compatible. I would like to reiterate it. My real concern is that 7.02 would be deemed as equivalent to 7.2 internally by the versioning subsystem and this is likely to clash with user's point of view. A user would *definitely* assume 7.02 as different from 7.2 and in all probability swear that former is inferior to the later. (version-to-list 7.02) - (7 2) (version-to-list 7.20) - (7 20) so it seems to me that if we keep two-digit numbers, there will be no problem at all. #+begin_src emacs-lisp (version-list-= (version-to-list 7.02) (version-to-list 7.20)) #+end_src - Carsten Please confirm what I am saying by evalling this: #+begin_src emacs-lisp (version-list-= (version-to-list 7.02) (version-to-list 7.2)) #+end_src Ignore this mail if it is already taken care of. Needless to say, I have ELPA-tarballs in mind when I say this. Jambunathan K. ___ Emacs-orgmode mailing list Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Internal links in LaTeX export
Thomas S. Dye t...@tsdye.com wrote: On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote: This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. Aloha Jambunathan K., Very many thanks for this information. I have Org-mode version 7.01trans (release_7.01h.880.g7531f). I take it the problem I'm having is due to a relatively recent change to Org-mode. If there is anything I can do to help isolate the problem, please let me know. Tom, If you have the time and the inclination, you might try bisecting your way through. Bisecting org-mode problems is actually a very good way to practice because the turnaround time is very small. Prerequisites: * you have a clone of the org-mode git repository. * you have an org test file. Steps: * [optional, but it makes me feel a little safer] create a test branch and switch to it: git checkout -b test-branch master * I clean out all the compiled files while doing a bisection: it's quicker than regenerating them every time and I don't have to worry (much) about emacs loading a wayward .elc file: make clean * start the bisection and tell git which commit is known good and which is known bad: git bisect start # current version is bad git bisect bad # release_7.01h was good - I got the name with ``git tag'' git bisect good release_7.01h That checks out a revision half-way in between the bad and good commits: since there are about 900 commits in between, you'll be at approx the 450-mark and it should take about 10 bisections to get it down to a single commit. * LOOP Now all you have to do is repeat the following steps: # since you did ``make clean'' you don't have to worry about .elc files # just reload all the .el files. M-x org-reload visit your org test file, export to LaTeX, check for \href/\hyperref (or whatever other telltale sign shows badness/goodness). # tell git about it git bisect good *OR* git bisect bad This last step will check out another revision and in about 10 repetitions of the loop, you are done. * Tell git you are done, so it can clean up: git bisect reset Theoretically, you could do all of this in your master branch without creating a test-branch and this last step will reset everything to the way it was before ``git start''. * Post the offending commit to the list. * Get back to your master branch: git checkout master * If you created a test-branch, clean it out: git branch -d test-branch * [Optional] Recreate your .elc files and reload them: make M-x org-reload And that's it: a half-hour of fun and games. Unless of course, you hit upon a revision that is neither good nor bad (in the above restricted sense): you might get some other problem that prevents you from being able to answer. That might or might not be easy to resolve, so I'll leave that as an advanced topic (truth be told, I came up against this situation a couple of days ago and I didn't know how to proceed: so it's ignorance more than anything else that prevents me from saying anything more). If you want to try, I'd be happy to answer questions - I might try the bisection later on tonight myself in any case. And btw, this is of course archeology of a different (and much easier) kind, so I imagine you'll take to it like a fish in water :-) HTH, Nick ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Christopher Allan Webber cweb...@dustycloud.org writes: However, yeah, I've also been interested in a less nerdy presentation route myself... s5? One of these others? There seem to be a lot of good options these days. :) and here I've been specifically looking for nerdier presentation options :) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Hi Scot, Scot Becker scot.bec...@gmail.com writes: Eric, This is cool and very useful. Thanks. Thanks, it was fun to work on. Also, most of the cool functionality already existed in Tom's original version, I just rebased it against Org-mode. This must be Zeitgeist-y because I was thinking about preparing presentations in Emacs this week. Then I saw slidy, now this and s5. Here's a further idea, to see what people think. Do you think it would be possible to make a temporary org-mode display configuration to display org-mode-written presentations (similar to epresent) without leaving org mode, and leaving the displayed slides editable? I once saw a video of someone doing a live presentation on something Emacs-y and he did the presentation by typing headlines, lists and detail in a clean Emacs buffer as he went along, similar to the way that some teachers might write out subject headings or outlines on the chalkboard or overhead projector as they lecture. I liked this a lot. As I see it, for less formal presentation situations, it lets you annotate and record class discussions discussions. It also lets the talk proceed in a less scripted manner: you can for example re-work the problem on the fly according to the way the group has defined it in the moment, not only according to the way you planned it at home. But doing it on the fly means that you don't have any of the advantages of typical slide-style presentations: an outline to prompt you, important figures, tables and visuals already there, links, detail, and the rest, pre-assembled. There is always the option of just upping the font size of a full screen Emacs buffer. In the past I've recorded macros which 1) widen 2) org-get-next-sibling 3) org-narrow-to-subtree or 1) widen 2) org-get-last-sibling 3) org-narrow-to-subtree and have found those nearly sufficient for giving a live editable presentation in Org-mode. I've wondered whether org mode might not be a nice vehicle to combine these things. For example, you create your script (just like in Eric's ' present.org'), but instead of showing in a custom display mode, you actually tweak the display parameters of org-mode itself to look slide-like (no stars, bigger fonts for titles, invisible /markup characters/, etc.), and then display the slides by displaying each top level subtree in a narrowed buffer one at a time. You add key bindings for moving back and forth, even perhaps a temporary minor mode for single key frame navigation that you could go in and out of (vi-like, I suppose). This way you'd be in (a slightly modified) org mode all the time, and could edit as you go, using all the structural features of org mode, and at the end you'd have a neat record of the way the lecture actually went, that you could distribute as you wish. Can anyone think why this might not be doable? That does seem eminently doable, and I think that epresent could be a good jumping off point, all that should be required is changing epresent from a major to a minor mode (although that may not be required since it inherits from Org-mode) and moving some of the key-bindings behind less invasive key-bindings. That said I definitely do not have the time to build upon or even really support this code, so you'll be on your own in the implementation (although I'll be happy to help in terms of answering questions). Cheers -- Eric Scot ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl writes: Richard Riley rile...@googlemail.com writes: Eric Schulte schulte.e...@gmail.com writes: Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. [...] http://github.com/eschulte/epresent (instructions in the README) If anyone missed it, there is also emacs-muse-slidy. http://www.flickr.com/photos/arciniegas/5108022392/ That is very impressive. Not bad. But there is org-s5 too. http://github.com/sigma/org-s5 Oh cool, this is the first I've seen of S5 or org-S5. I think I'll probably stick with Beamer export for my serious presentations, but I like the idea and simplicity of being to run simple presentations directly from within Emacs. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Jambunathan K kjambunat...@gmail.com writes: Eric Schulte schulte.e...@gmail.com writes: Hi, Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) I think (require 'org-exp) is required. do you know what for? Looks like it walks you through the headline one at a time and presents the entry contents as such. yes When I get to the equations slide what should I expect to see? The equation fully rendered (as in text books) or just the markup (as it is literally typed). I see an image overlay of the latex fragment. Is that not what you see? Jambunathan K. Best -- Eric ___ Emacs-orgmode mailing list Please 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 Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Hi Seb, Sébastien Vauban wxhgmqzgw...@spammotel.com writes: Hi Eric, Eric Schulte wrote: Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) Just a typo in README: present.org, instead of presentation.org. Thanks fixed. Quite promising for the rest, really! Thanks once again, for all add-ons you provide us with... Thanks, all credit goes to Carsten for making Org-mode so much fun to extend. On the glitches side: I'm sure there are still some bugs. I definitely want to introduce this more as something that may be fun rather than supported software. - some titles are truncated because of their size - I did not see any image I'll take a look, I don't think I ever tested with an image (aside from the LaTeX preview image). - Beamer's frame level is not supported (ending up with a couple of really long slides) This is one of those things that I don't think I'll ever really want to implement as it begins to go beyond the complexity of what I consider a simple tool. - having to scroll within a slide seems to edit the Org file somehow My guess is that widening and narrowing the buffer is re-setting the edited state of the buffer, but I can't say for sure. - edited Org file is not undo-able because of visibility troubles Yea, epresent hides the cursor and the echo area, which makes any sort of editing or navigation aside form using the built in functions a pain. Maybe if scroll was bound to space-bar this could be fixed. - error outline-back-to-heading: before first heading When does this happen? But, once again, it gives a lot of hope to get right to the point of loosing a less time as possible, and lets us work on the contents of our file. Here's hoping. Cheers -- Eric Best regards, Seb ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [Babel] Bug with org-src-fontify-natively... after running epresent
Hi Seb, I just pushed up a change to epresent so that it should now restore your original value of org-src-fontify-natively -- assuming that you quit epresent with the epresent-quit command (bound to q). Best -- Eric Sébastien Vauban wxhgmqzgw...@spammotel.com writes: Hello Eric, After having run epresent, I got this error when trying to publish my theme-test.org file (sent on this list a couple of days ago -- no reaction BTW ;-)). Debugger entered--Lisp error: (void-function -mode) -mode() funcall(-mode) (if (eq major-mode lang-mode) nil (funcall lang-mode)) (unless (eq major-mode lang-mode) (funcall lang-mode)) (save-current-buffer (set-buffer (get-buffer-create ...)) (delete-region (point-min) (point-max)) (insert string) (unless (eq major-mode lang-mode) (funcall lang-mode)) (font-lock-fontify-buffer) (setq pos (point-min)) (while (setq next ...) (put-text-property ... ... ... ... org-buffer) (setq pos next))) (with-current-buffer (get-buffer-create (concat org-src-fontification: ...)) (delete-region (point-min) (point-max)) (insert string) (unless (eq major-mode lang-mode) (funcall lang-mode)) (font-lock-fontify-buffer) (setq pos (point-min)) (while (setq next ...) (put-text-property ... ... ... ... org-buffer) (setq pos next))) (let* ((lang-mode ...) (string ...) (modified ...) (org-buffer ...) pos next) (remove-text-properties start end (quote ...)) (with-current-buffer (get-buffer-create ...) (delete-region ... ...) (insert string) (unless ... ...) (font-lock-fontify-buffer) (setq pos ...) (while ... ... ...)) (add-text-properties start end (quote ...)) (set-buffer-modified-p modified)) org-src-font-lock-fontify-block( 1227 1500) (cond ((and lang org-src-fontify-natively) (org-src-font-lock-fontify-block lang block-start block-end)) (quoting (add-text-properties beg1 ... ...)) ((not org-fontify-quote-and-verse-blocks)) ((string= block-type quote) (add-text-properties beg1 end1 ...)) ((string= block-type verse) (add-text-properties beg1 end1 ...))) (progn (setq end (match-end 0) end1 (1- ...)) (setq block-end (match-beginning 0)) (when quoting (remove-text-properties beg end ...)) (add-text-properties beg end (quote ...)) (add-text-properties beg beg1 (quote ...)) (add-text-properties end1 (+ end 1) (quote ...)) (cond (... ...) (quoting ...) (...) (... ...) (... ...)) t) (if (re-search-forward (concat ^[ ]*#\\+end ... \\.*) nil t) (progn (setq end ... end1 ...) (setq block-end ...) (when quoting ...) (add-text-properties beg end ...) (add-text-properties beg beg1 ...) (add-text-properties end1 ... ...) (cond ... ... ... ... ...) t)) (when (re-search-forward (concat ^[]*#\\+end ... \\.*) nil t) (setq end (match-end 0) end1 (1- ...)) (setq block-end (match-beginning 0)) (when quoting (remove-text-properties beg end ...)) (add-text-properties beg end (quote ...)) (add-text-properties beg beg1 (quote ...)) (add-text-properties end1 (+ end 1) (quote ...)) (cond (... ...) (quoting ...) (...) (... ...) (... ...)) t) (cond ((member dc1 ...) (org-remove-flyspell-overlays-in ... ...) (remove-text-properties ... ... ...) (add-text-properties ... ... ...) (add-text-properties ... ... ...) t) ((and ... ...) (setq block-type ... quoting ...) (when ... ... ... ... ... ... ... ... t)) ((member dc1 ...) (add-text-properties beg ... ...) (add-text-properties ... ... ...)) ((not ...) (add-text-properties beg ... ...) t) ((or ... ...) (add-text-properties beg ... ...) t) ((member dc3 ...) (add-text-properties beg ... ...)) (t nil)) (let ((beg ...) (block-start ...) (block-end nil) (lang ...) (beg1 ...) (dc1 ...) (dc3 ...) end end1 quoting block-type) (cond (... ... ... ... ... t) (... ... ...) (... ... ...) (... ... t) (... ... t) (... ...) (t nil))) (if (re-search-forward ^\\([ ]*#\\+\\(\\([a-zA-Z]+:?\\| \\|$\\)\\(_\\([a-zA-Z]+\\)\\)?\\)[ ]*\\(\\([^ \n]*\\)[ ]*\\(.*\\)\\)\\) limit t) (let (... ... ... ... ... ... ... end end1 quoting block-type) (cond ... ... ... ... ... ... ...))) (let ((case-fold-search t)) (if (re-search-forward ^\\([ ]*#\\+\\(\\([a-zA-Z]+:?\\| \\|$\\)\\(_\\([a-zA-Z]+\\)\\)?\\)[ ]*\\(\\([^ \n]*\\)[]*\\(.*\\)\\)\\) limit t) (let ... ...))) org-fontify-meta-lines-and-blocks(2136) #[(start end optional loudly) ...@\306=\204\307! \211AA)\310 \311\312 \313\211\211'()*)\203+\...@\314\315(\316'T\211'\317\#\210)@\...@,b\210`-W\203\373\f;\203`\320\f-\306#\202d\f-!\203\373`\311\224V\204q\321u\210\203\241`\212\311\224b\210\321y\210`)Y\203\241\322`\212\311\224b\210\321y\210`)U\203\232`S\202\234\311\224`\323\306$\210A\211\203K
[Orgmode] Re: [WISH] Org Importers
Jambunathan K kjambunat...@gmail.com writes: However, what would be ideal would be if there were a tool which would take a Word document with /track changes/ and generate a patch file for a text version of that document... that could then provide some mechanism for getting changes back into an org document (modulo problems with line re-arrangements unfortunately). Just a pipe dream... If you allow me some liberty, the suggestion is in two parts 1. Word/Pdf/Latex-Org converter I have suggested or hinted elsewhere (in a babel thread) the need for importing in to Org from other formats. FWIW, I have a home-brewed perl script that converts latex documents to org-mode files. Loosely based on latex2doc[1], it uses a latex style file (generated by the perl script) to markup the pdf output (e.g. asterisks for section headings, etc.). The org-formatted pdf is then converted to plain text with pdftotext. It's a crude and by no means comprehensive hack designed to meet my own peculiar needs. But I'd be happy to share it on Worg (with ample disclaimers) if anyone is interested. Best, Matt Footnotes: [1] http://www.dur.ac.uk/p.j.heslin/Software/Latex/latex2doc.php ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: General question on dealing with Latex to word conversion
Marvin Doyley marvin...@gmail.com writes: Org mode is now a part of my daily work-flow, not only do I use it for teaching, scheduling my time, but I also use it to store my research notes. The only snag is several of my collaborators is tied to microsoft word, and thus my only work around is to export my notes and draft from Org to plain text and then reformat everything in word, which real time sync., especially when I have to retype equations in Mathtype. I know there are bunch of commercial software that claim to be able to convert latex files to word, but most are far from perfect. Is there a more efficient way of tacking this problem ? Is there is any plans of developing a org-export-rtf or org-export-docx function ? There is now an FAQ on converting to odt/rtf/doc, since there have been several threads on this question recently: http://orgmode.org/worg/org-faq.php#convert-to-open-office The FAQ is based largely on the helpful discussion of this issue late last month: http://comments.gmane.org/gmane.emacs.orgmode/31168 Please feel free to suggest other methods you'd like to see in the FAQ. Marvin: I'm not sure whether the methods in the FAQ address the problem of math equations. I believe that some exporters (such as latex2rtf) convert equations to images, while others (such as ttf) try to render them in html, etc. Might I ask which converters[1] you have tried? I might be helpful for the org community to know what does *not* work. I've had great success with tex4ht and latex2rtf, but my documents don't include math equations. :) Best, Matt Footnotes: [1] http://www.tug.org/applications/tex4ht/mn.html#QQ1-1-83 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Internal links in LaTeX export
On Oct 28, 2010, at 12:35 PM, Nick Dokos wrote: Thomas S. Dye t...@tsdye.com wrote: On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote: This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. Aloha Jambunathan K., Very many thanks for this information. I have Org-mode version 7.01trans (release_7.01h.880.g7531f). I take it the problem I'm having is due to a relatively recent change to Org-mode. If there is anything I can do to help isolate the problem, please let me know. Tom, If you have the time and the inclination, you might try bisecting your way through. Bisecting org-mode problems is actually a very good way to practice because the turnaround time is very small. Prerequisites: * you have a clone of the org-mode git repository. * you have an org test file. Steps: * [optional, but it makes me feel a little safer] create a test branch and switch to it: git checkout -b test-branch master * I clean out all the compiled files while doing a bisection: it's quicker than regenerating them every time and I don't have to worry (much) about emacs loading a wayward .elc file: make clean * start the bisection and tell git which commit is known good and which is known bad: git bisect start # current version is bad git bisect bad # release_7.01h was good - I got the name with ``git tag'' git bisect good release_7.01h That checks out a revision half-way in between the bad and good commits: since there are about 900 commits in between, you'll be at approx the 450- mark and it should take about 10 bisections to get it down to a single commit. * LOOP Now all you have to do is repeat the following steps: # since you did ``make clean'' you don't have to worry about .elc files # just reload all the .el files. M-x org-reload visit your org test file, export to LaTeX, check for \href/ \hyperref (or whatever other telltale sign shows badness/goodness). # tell git about it git bisect good *OR* git bisect bad This last step will check out another revision and in about 10 repetitions of the loop, you are done. * Tell git you are done, so it can clean up: git bisect reset Theoretically, you could do all of this in your master branch without creating a test-branch and this last step will reset everything to the way it was before ``git start''. * Post the offending commit to the list. * Get back to your master branch: git checkout master * If you created a test-branch, clean it out: git branch -d test-branch * [Optional] Recreate your .elc files and reload them: make M-x org-reload And that's it: a half-hour of fun and games. Unless of course, you hit upon a revision that is neither good nor bad (in the above restricted sense): you might get some other problem that prevents you from being able to answer. That might or might not be easy to resolve, so I'll leave that as an advanced topic (truth be told, I came up against this situation a couple of days ago and I didn't know how to proceed: so it's ignorance more than anything else that prevents me from saying anything more). If you want to try, I'd be happy to answer questions - I might try the bisection later on tonight myself in any case. And btw, this is of course archeology of a different (and much easier) kind, so I imagine you'll take to it like a fish in water :-) HTH, Nick Hi Nick, Irresistible hook at the end there. I wish this stuff were as easy as archaeology is for me. Your instructions are terrific, though. I did hit on a revision that was neither good nor bad: commit 8562273b272024a630a582b0e1b94c481d8abeec Author: Eric Schulte schulte.e...@gmail.com Date: Sat Oct 16 13:21:47 2010 -0600 ob-ref: don't forget arguments to referenced code blocks * lisp/ob-ref.el (org-babel-ref-resolve): bringing the referent arguments back to their params before evaluation This one puts these lines in *Messages* when I export to LaTeX executing Org code block... if: Symbol's value as variable is void: result-type I tried using different commits for the initial git bisect good, hoping that would skip by the problem, but this one appears to have stuck around a while. My other two tries both ended with this same error, but with different commits. I'm not sure what to do next. This problem isn't yielding to my archaeo-logic. :) All the best, Tom ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Internal links in LaTeX export
Thomas There was a hint at possible solution (or atleast a partial solution) in my original post. Did you try it before jumping in to rough waters or digging deeper? Do , | M-x customize-variable RET org-export-latex-hyperref-format' ` so that your .emacs has an entry like this , [.emacs] | | (custom-set-variables | '(org-export-latex-hyperref-format \\hyperref[%s]{%s})) | ` The above setting solves the problem for me with the following simple Org file. * Heading1 Make this section as large as possible so that it fills atleast a page. * Heading2 Links to [[Heading1]] Jambunathan K. Thomas S. Dye t...@tsdye.com writes: On Oct 28, 2010, at 12:35 PM, Nick Dokos wrote: Thomas S. Dye t...@tsdye.com wrote: On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote: This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. Aloha Jambunathan K., Very many thanks for this information. I have Org-mode version 7.01trans (release_7.01h.880.g7531f). I take it the problem I'm having is due to a relatively recent change to Org-mode. If there is anything I can do to help isolate the problem, please let me know. Tom, If you have the time and the inclination, you might try bisecting your way through. Bisecting org-mode problems is actually a very good way to practice because the turnaround time is very small. Prerequisites: * you have a clone of the org-mode git repository. * you have an org test file. Steps: * [optional, but it makes me feel a little safer] create a test branch and switch to it: git checkout -b test-branch master * I clean out all the compiled files while doing a bisection: it's quicker than regenerating them every time and I don't have to worry (much) about emacs loading a wayward .elc file: make clean * start the bisection and tell git which commit is known good and which is known bad: git bisect start # current version is bad git bisect bad # release_7.01h was good - I got the name with ``git tag'' git bisect good release_7.01h That checks out a revision half-way in between the bad and good commits: since there are about 900 commits in between, you'll be at approx the 450- mark and it should take about 10 bisections to get it down to a single commit. * LOOP Now all you have to do is repeat the following steps: # since you did ``make clean'' you don't have to worry about .elc files # just reload all the .el files. M-x org-reload visit your org test file, export to LaTeX, check for \href/ \hyperref (or whatever other telltale sign shows badness/goodness). # tell git about it git bisect good *OR* git bisect bad This last step will check out another revision and in about 10 repetitions of the loop, you are done. * Tell git you are done, so it can clean up: git bisect reset Theoretically, you could do all of this in your master branch without creating a test-branch and this last step will reset everything to the way it was before ``git start''. * Post the offending commit to the list. * Get back to your master branch: git checkout master * If you created a test-branch, clean it out: git branch -d test-branch * [Optional] Recreate your .elc files and reload them: make M-x org-reload And that's it: a half-hour of fun and games. Unless of course, you hit upon a revision that is neither good nor bad (in the above restricted sense): you might get some other problem that prevents you from being able to answer. That might or might not be easy to resolve, so I'll leave that as an advanced topic (truth be told, I came up against this situation a couple of days ago and I didn't know how to proceed: so it's ignorance more than anything else that prevents me from saying anything more). If you want to try, I'd be happy to answer questions - I might try the bisection later on tonight myself in any case. And btw, this is of course archeology of a different (and much easier) kind, so I imagine you'll take to it like a fish in water :-) HTH, Nick Hi Nick, Irresistible hook at the end there. I wish this stuff were as easy as archaeology is for me. Your instructions are terrific, though. I did hit on a revision that was neither good nor bad: commit 8562273b272024a630a582b0e1b94c481d8abeec Author: Eric Schulte schulte.e...@gmail.com Date: Sat Oct 16 13:21:47 2010 -0600 ob-ref: don't forget arguments to referenced code blocks * lisp/ob-ref.el (org-babel-ref-resolve): bringing the referent arguments back to their params before evaluation This one puts these lines in *Messages* when I export to LaTeX executing Org code block... if: Symbol's value as variable is void: result-type I tried using different commits for the initial git bisect good, hoping that would skip by the problem, but this one
Re: [Orgmode] [CONCERN] Orgmode version string
Carsten (version-to-list 7.02) - (7 2) (version-to-list 7.20) - (7 20) so it seems to me that if we keep two-digit numbers, there will be no problem at all. #+begin_src emacs-lisp (version-list-= (version-to-list 7.02) (version-to-list 7.20)) #+end_src Yes, I agree. Jambunathan K. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Eric Schulte schulte.e...@gmail.com writes: Jambunathan K kjambunat...@gmail.com writes: Eric Schulte schulte.e...@gmail.com writes: Hi, Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) I think (require 'org-exp) is required. do you know what for? This is the trace I got otherwise. (See the trace at the end of the mail) Looks like it walks you through the headline one at a time and presents the entry contents as such. yes And it fontifies the headlines in bold fonts just as in slides (actually too big for my NetBook). Yesterday when I did a quick run the presentation was insipid and I didn't get to see the big slide-like fonts. Honestly, I was a bit surprised at why others were wowing. I ran the presentation today right after also doing a C-c C-e d (for verifying Thomas' bug report on LaTeX internal links) and I see the altered behaviour. I do think it is pretty impressive. I think loading the org-latex.el makes this difference. When I get to the equations slide what should I expect to see? The equation fully rendered (as in text books) or just the markup (as it is literally typed). I see an image overlay of the latex fragment. Is that not what you see? No I don't see any overlays. I will investigate the problem sometime later. Possible that it has something to do with ltxpng or missing image libraries. Jambunathan K. Trace: Debugger entered--Lisp error: (void-function org-infile-export-plist) (org-infile-export-plist) (plist-get (org-infile-export-plist) :latex-header-extra) (let* ((prefixnodir ...) (absprefix ...) (todir ...) (opt org-format-latex-options) (matchers ...) (re-list org-latex-regexps) (org-format-latex-header-extra ...) (cnt 0) txt hash link beg end re e checkdir executables-checked string m n block linkfile movefile ov) (while (setq e ...) (setq m ... re ... n ... block ...) (when ... ... ...))) org-format-latex(ltxpng/present c:/Documents and Settings/kjambunathan/My Documents/My Data/elisp/eschulte-epresent-016f027/ overlays Creating images for entry...%s nil forbuffer dvipng) (let (beg end at msg) (cond (... ...) (... ... ...) (t ... ...)) (message msg ) (narrow-to-region beg end) (goto-char beg) (org-format-latex (concat ltxpng/ ...) default-directory (quote overlays) msg at (quote forbuffer) (quote dvipng)) (message msg done. Use `C-c C-c' to remove images.)) (save-restriction (let (beg end at msg) (cond ... ... ...) (message msg ) (narrow-to-region beg end) (goto-char beg) (org-format-latex ... default-directory ... msg at ... ...) (message msg done. Use `C-c C-c' to remove images.))) (save-excursion (save-restriction (let ... ... ... ... ... ... ...))) org-preview-latex-fragment(16) (let ((org-format-latex-options ...)) (org-preview-latex-fragment 16)) (let ((delay-mode-hooks t)) (org-mode) (setq major-mode (quote epresent-mode)) (setq mode-name EPresent) (progn (if ... ...) (unless ... ...) (let ... ...)) (use-local-map epresent-mode-map) (set-syntax-table epresent-mode-syntax-table) (setq local-abbrev-table epresent-mode-abbrev-table) (text-scale-adjust 0) (text-scale-adjust epresent-text-scale) (setq org-inline-image-overlays t) (setq org-src-fontify-natively t) (let (...) (org-preview-latex-fragment 16)) (add-to-invisibility-spec (quote ...)) (org-remove-flyspell-overlays-in (point-min) (point-max)) (epresent-fontify)) (progn (make-local-variable (quote delay-mode-hooks)) (let (...) (org-mode) (setq major-mode ...) (setq mode-name EPresent) (progn ... ... ...) (use-local-map epresent-mode-map) (set-syntax-table epresent-mode-syntax-table) (setq local-abbrev-table epresent-mode-abbrev-table) (text-scale-adjust 0) (text-scale-adjust epresent-text-scale) (setq org-inline-image-overlays t) (setq org-src-fontify-natively t) (let ... ...) (add-to-invisibility-spec ...) (org-remove-flyspell-overlays-in ... ...) (epresent-fontify))) (delay-mode-hooks (org-mode) (setq major-mode (quote epresent-mode)) (setq mode-name EPresent) (progn (if ... ...) (unless ... ...) (let ... ...)) (use-local-map epresent-mode-map) (set-syntax-table epresent-mode-syntax-table) (setq local-abbrev-table epresent-mode-abbrev-table)
Re: [Orgmode] Re: Internal links in LaTeX export
Aloha Jambunathan K., Yes, thanks for that suggestion. It should work on your example, but it breaks external links, like this: \hyperref[http://www.ctan.org/tex-archive/macros/latex/contrib/koma-script/ ]{KOMA-script} External links require the \href{}{} command. It appears the LaTeX export process no longer distinguishes internal and external links, as I believe it used to do. All the best, Tom On Oct 28, 2010, at 3:30 PM, Jambunathan K wrote: Thomas There was a hint at possible solution (or atleast a partial solution) in my original post. Did you try it before jumping in to rough waters or digging deeper? Do , | M-x customize-variable RET org-export-latex-hyperref-format' ` so that your .emacs has an entry like this , [.emacs] | | (custom-set-variables | '(org-export-latex-hyperref-format \\hyperref[%s]{%s})) | ` The above setting solves the problem for me with the following simple Org file. * Heading1 Make this section as large as possible so that it fills atleast a page. * Heading2 Links to [[Heading1]] Jambunathan K. Thomas S. Dye t...@tsdye.com writes: On Oct 28, 2010, at 12:35 PM, Nick Dokos wrote: Thomas S. Dye t...@tsdye.com wrote: On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote: This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. Aloha Jambunathan K., Very many thanks for this information. I have Org-mode version 7.01trans (release_7.01h.880.g7531f). I take it the problem I'm having is due to a relatively recent change to Org-mode. If there is anything I can do to help isolate the problem, please let me know. Tom, If you have the time and the inclination, you might try bisecting your way through. Bisecting org-mode problems is actually a very good way to practice because the turnaround time is very small. Prerequisites: * you have a clone of the org-mode git repository. * you have an org test file. Steps: * [optional, but it makes me feel a little safer] create a test branch and switch to it: git checkout -b test-branch master * I clean out all the compiled files while doing a bisection: it's quicker than regenerating them every time and I don't have to worry (much) about emacs loading a wayward .elc file: make clean * start the bisection and tell git which commit is known good and which is known bad: git bisect start # current version is bad git bisect bad # release_7.01h was good - I got the name with ``git tag'' git bisect good release_7.01h That checks out a revision half-way in between the bad and good commits: since there are about 900 commits in between, you'll be at approx the 450- mark and it should take about 10 bisections to get it down to a single commit. * LOOP Now all you have to do is repeat the following steps: # since you did ``make clean'' you don't have to worry about .elc files # just reload all the .el files. M-x org-reload visit your org test file, export to LaTeX, check for \href/ \hyperref (or whatever other telltale sign shows badness/goodness). # tell git about it git bisect good *OR* git bisect bad This last step will check out another revision and in about 10 repetitions of the loop, you are done. * Tell git you are done, so it can clean up: git bisect reset Theoretically, you could do all of this in your master branch without creating a test-branch and this last step will reset everything to the way it was before ``git start''. * Post the offending commit to the list. * Get back to your master branch: git checkout master * If you created a test-branch, clean it out: git branch -d test-branch * [Optional] Recreate your .elc files and reload them: make M-x org-reload And that's it: a half-hour of fun and games. Unless of course, you hit upon a revision that is neither good nor bad (in the above restricted sense): you might get some other problem that prevents you from being able to answer. That might or might not be easy to resolve, so I'll leave that as an advanced topic (truth be told, I came up against this situation a couple of days ago and I didn't know how to proceed: so it's ignorance more than anything else that prevents me from saying anything more). If you want to try, I'd be happy to answer questions - I might try the bisection later on tonight myself in any case. And btw, this is of course archeology of a different (and much easier) kind, so I imagine you'll take to it like a fish in water :-) HTH, Nick Hi Nick, Irresistible hook at the end there. I wish this stuff were as easy as archaeology is for me. Your instructions are terrific, though. I did hit on a revision that was neither good nor bad: commit 8562273b272024a630a582b0e1b94c481d8abeec Author: Eric Schulte schulte.e...@gmail.com Date: Sat Oct 16 13:21:47 2010 -0600 ob-ref: don't forget arguments to referenced code blocks * lisp/ob-ref.el
Re: [Orgmode] Re: [WISH] Org Importers
FWIW, I have a home-brewed perl script that converts latex documents to org-mode files. Loosely based on latex2doc[1], it uses a latex style file (generated by the perl script) to markup the pdf output (e.g. asterisks for section headings, etc.). The org-formatted pdf is then converted to plain text with pdftotext. It's a crude and by no means comprehensive hack designed to meet my own peculiar needs. But I'd be happy to share it on Worg (with ample disclaimers) if anyone is interested. I for one, would be interested in this, though it is likely to be a few months before I can get around to using it for an actual project. Jeff -- Jeffrey Horn Graduate Lecturer and PhD Student in Economics George Mason University (704) 271-4797 jh...@gmu.edu jrhorn...@gmail.com http://www.failuretorefrain.com/jeff/ ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Internal links in LaTeX export
Thomas S. Dye t...@tsdye.com wrote: ... I did hit on a revision that was neither good nor bad: commit 8562273b272024a630a582b0e1b94c481d8abeec Author: Eric Schulte schulte.e...@gmail.com Date: Sat Oct 16 13:21:47 2010 -0600 ob-ref: don't forget arguments to referenced code blocks * lisp/ob-ref.el (org-babel-ref-resolve): bringing the referent arguments back to their params before evaluation This one puts these lines in *Messages* when I export to LaTeX executing Org code block... if: Symbol's value as variable is void: result-type Yeah, that was the error that stopped me cold as well, although I hit it on a different commit (I think) - there must be a way to get around the problem but it certainly makes things more difficult. I imagine the way to go is to find a commit before this error was introduced and a commit after it was fixed and try those with your problem: it might allow you to bypass the problematic range (in which case, you might be able to continue bisecting all the way to the end), or it might limit the bad commit to this range - the latter is still valuable to know but certainly not as definitive as this is the bad commit. And in any case, all of this would fall into the advanced appendix in the git bisection book. Sorry it didn't pan out but I hope that you had fun digging, Nick ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [SOLVED] Re: Internal links in LaTeX export
Thomas S. Dye t...@tsdye.com writes: Aloha Jambunathan K., Yes, thanks for that suggestion. It should work on your example, but it breaks external links, like this: \hyperref[http://www.ctan.org/tex-archive/macros/latex/contrib/koma-script/ ]{KOMA-script} External links require the \href{}{} command. It appears the LaTeX export process no longer distinguishes internal and external links, as I believe it used to do. This is the problematic commit: commit f5918bdcc05d7924dc204b57307023eb1ef011f0 parent df5894cdcb10819560f003c5b94b8f5f2b7d33cf Date: Sun Oct 17 08:29:51 2010 + LaTeX export: use org-export-latex-hyperref-format * lisp/org-latex.el (org-export-latex-links) : Replaced hard coded hyperref format with custom variable `org-export-latex-hyperref-format' Note that href is not same as hyperref. Jambunthan K. All the best, Tom On Oct 28, 2010, at 3:30 PM, Jambunathan K wrote: Thomas There was a hint at possible solution (or atleast a partial solution) in my original post. Did you try it before jumping in to rough waters or digging deeper? Do , | M-x customize-variable RET org-export-latex-hyperref-format' ` so that your .emacs has an entry like this , [.emacs] | | (custom-set-variables | '(org-export-latex-hyperref-format \\hyperref[%s]{%s})) | ` The above setting solves the problem for me with the following simple Org file. * Heading1 Make this section as large as possible so that it fills atleast a page. * Heading2 Links to [[Heading1]] Jambunathan K. Thomas S. Dye t...@tsdye.com writes: On Oct 28, 2010, at 12:35 PM, Nick Dokos wrote: Thomas S. Dye t...@tsdye.com wrote: On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote: This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. Aloha Jambunathan K., Very many thanks for this information. I have Org-mode version 7.01trans (release_7.01h.880.g7531f). I take it the problem I'm having is due to a relatively recent change to Org-mode. If there is anything I can do to help isolate the problem, please let me know. Tom, If you have the time and the inclination, you might try bisecting your way through. Bisecting org-mode problems is actually a very good way to practice because the turnaround time is very small. Prerequisites: * you have a clone of the org-mode git repository. * you have an org test file. Steps: * [optional, but it makes me feel a little safer] create a test branch and switch to it: git checkout -b test-branch master * I clean out all the compiled files while doing a bisection: it's quicker than regenerating them every time and I don't have to worry (much) about emacs loading a wayward .elc file: make clean * start the bisection and tell git which commit is known good and which is known bad: git bisect start # current version is bad git bisect bad # release_7.01h was good - I got the name with ``git tag'' git bisect good release_7.01h That checks out a revision half-way in between the bad and good commits: since there are about 900 commits in between, you'll be at approx the 450- mark and it should take about 10 bisections to get it down to a single commit. * LOOP Now all you have to do is repeat the following steps: # since you did ``make clean'' you don't have to worry about .elc files # just reload all the .el files. M-x org-reload visit your org test file, export to LaTeX, check for \href/ \hyperref (or whatever other telltale sign shows badness/goodness). # tell git about it git bisect good *OR* git bisect bad This last step will check out another revision and in about 10 repetitions of the loop, you are done. * Tell git you are done, so it can clean up: git bisect reset Theoretically, you could do all of this in your master branch without creating a test-branch and this last step will reset everything to the way it was before ``git start''. * Post the offending commit to the list. * Get back to your master branch: git checkout master * If you created a test-branch, clean it out: git branch -d test-branch * [Optional] Recreate your .elc files and reload them: make M-x org-reload And that's it: a half-hour of fun and games. Unless of course, you hit upon a revision that is neither good nor bad (in the above restricted sense): you might get some other problem that prevents you from being able to answer. That might or might not be easy to resolve, so I'll leave that as an advanced topic (truth be told, I came up against this situation a couple of days ago and I didn't know how to proceed: so it's ignorance more than anything else that prevents me from saying anything more). If you want to try, I'd be happy to answer questions - I might try the bisection later on tonight myself in any case. And
Re: [Orgmode] [SOLVED] Re: Internal links in LaTeX export
On Oct 29, 2010, at 5:22 AM, Jambunathan K wrote: Thomas S. Dye t...@tsdye.com writes: Aloha Jambunathan K., Yes, thanks for that suggestion. It should work on your example, but it breaks external links, like this: \hyperref[http://www.ctan.org/tex-archive/macros/latex/contrib/koma-script/ ]{KOMA-script} External links require the \href{}{} command. It appears the LaTeX export process no longer distinguishes internal and external links, as I believe it used to do. This is the problematic commit: commit f5918bdcc05d7924dc204b57307023eb1ef011f0 parent df5894cdcb10819560f003c5b94b8f5f2b7d33cf Date: Sun Oct 17 08:29:51 2010 + LaTeX export: use org-export-latex-hyperref-format I have just reverted this commit. - Carsten * lisp/org-latex.el (org-export-latex-links) : Replaced hard coded hyperref format with custom variable `org-export-latex-hyperref-format' Note that href is not same as hyperref. Jambunthan K. All the best, Tom On Oct 28, 2010, at 3:30 PM, Jambunathan K wrote: Thomas There was a hint at possible solution (or atleast a partial solution) in my original post. Did you try it before jumping in to rough waters or digging deeper? Do , | M-x customize-variable RET org-export-latex-hyperref-format' ` so that your .emacs has an entry like this , [.emacs] | | (custom-set-variables | '(org-export-latex-hyperref-format \\hyperref[%s]{%s})) | ` The above setting solves the problem for me with the following simple Org file. * Heading1 Make this section as large as possible so that it fills atleast a page. * Heading2 Links to [[Heading1]] Jambunathan K. Thomas S. Dye t...@tsdye.com writes: On Oct 28, 2010, at 12:35 PM, Nick Dokos wrote: Thomas S. Dye t...@tsdye.com wrote: On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote: This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. Aloha Jambunathan K., Very many thanks for this information. I have Org-mode version 7.01trans (release_7.01h.880.g7531f). I take it the problem I'm having is due to a relatively recent change to Org-mode. If there is anything I can do to help isolate the problem, please let me know. Tom, If you have the time and the inclination, you might try bisecting your way through. Bisecting org-mode problems is actually a very good way to practice because the turnaround time is very small. Prerequisites: * you have a clone of the org-mode git repository. * you have an org test file. Steps: * [optional, but it makes me feel a little safer] create a test branch and switch to it: git checkout -b test-branch master * I clean out all the compiled files while doing a bisection: it's quicker than regenerating them every time and I don't have to worry (much) about emacs loading a wayward .elc file: make clean * start the bisection and tell git which commit is known good and which is known bad: git bisect start # current version is bad git bisect bad # release_7.01h was good - I got the name with ``git tag'' git bisect good release_7.01h That checks out a revision half-way in between the bad and good commits: since there are about 900 commits in between, you'll be at approx the 450- mark and it should take about 10 bisections to get it down to a single commit. * LOOP Now all you have to do is repeat the following steps: # since you did ``make clean'' you don't have to worry about .elc files # just reload all the .el files. M-x org-reload visit your org test file, export to LaTeX, check for \href/ \hyperref (or whatever other telltale sign shows badness/goodness). # tell git about it git bisect good *OR* git bisect bad This last step will check out another revision and in about 10 repetitions of the loop, you are done. * Tell git you are done, so it can clean up: git bisect reset Theoretically, you could do all of this in your master branch without creating a test-branch and this last step will reset everything to the way it was before ``git start''. * Post the offending commit to the list. * Get back to your master branch: git checkout master * If you created a test-branch, clean it out: git branch -d test-branch * [Optional] Recreate your .elc files and reload them: make M-x org-reload And that's it: a half-hour of fun and games. Unless of course, you hit upon a revision that is neither good nor bad (in the above restricted sense): you might get some other problem that prevents you from being able to answer. That might or might not be easy to resolve, so I'll leave that as an advanced topic (truth be told, I came up against this situation a couple of days ago and I didn't know how to proceed: so it's ignorance more than anything else that prevents me from saying anything more). If you want to try, I'd be happy to answer questions - I might try the bisection later on tonight myself in any case. And btw,
[Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Jambunathan K kjambunat...@gmail.com writes: Eric Schulte schulte.e...@gmail.com writes: Jambunathan K kjambunat...@gmail.com writes: Eric Schulte schulte.e...@gmail.com writes: Hi, Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a very nice little utility for giving presentations using Emacs as the display engine. Obviously I was aghast to learn that epresent didn't work with Org-mode documents. I took the liberty of reworking it so that it runs off of Org-mode documents and uses Org-mode both to structure the presentation and to handle most of the fancy display elements. This re-working was mainly a series of quick hacks, and is certainly not mature in any way. But I think it is usable in it's current state for running simple presentations, and thought it may be interesting or of use to people here. If you're interested check out the example presentation included in the source code repository. http://github.com/eschulte/epresent (instructions in the README) I think (require 'org-exp) is required. do you know what for? This is the trace I got otherwise. (See the trace at the end of the mail) Thanks, It's now requiring org-exp and org-latex. Looks like it walks you through the headline one at a time and presents the entry contents as such. yes And it fontifies the headlines in bold fonts just as in slides (actually too big for my NetBook). in newer Emacs C-- and C-+ should be usable to adjust the font sizes. Yesterday when I did a quick run the presentation was insipid and I didn't get to see the big slide-like fonts. Honestly, I was a bit surprised at why others were wowing. I ran the presentation today right after also doing a C-c C-e d (for verifying Thomas' bug report on LaTeX internal links) and I see the altered behaviour. I do think it is pretty impressive. I think loading the org-latex.el makes this difference. When I get to the equations slide what should I expect to see? The equation fully rendered (as in text books) or just the markup (as it is literally typed). I see an image overlay of the latex fragment. Is that not what you see? No I don't see any overlays. I will investigate the problem sometime later. Possible that it has something to do with ltxpng or missing image libraries. hmm, this uses the same machinery used to display latex previews in regular Org-mode buffers (callable with C-c C-x C-l), so if that works this should work, and vice versa, but I believe this does require some special commands be available on your system (e.g. dvipng). Best -- Eric Jambunathan K. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: epresent and Org-mode: using Emacs to run presentations of Org-mode docs
Sébastien Vauban wxhgmqzgw...@spammotel.com writes: - I did not see any image I think inline images should be working with the latest version ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Internal links in LaTeX export
Carsten Dominik carsten.domi...@gmail.com writes: On Oct 29, 2010, at 5:22 AM, Jambunathan K wrote: Thomas S. Dye t...@tsdye.com writes: Aloha Jambunathan K., Yes, thanks for that suggestion. It should work on your example, but it breaks external links, like this: \hyperref[http://www.ctan.org/tex-archive/macros/latex/contrib/koma-script/ ]{KOMA-script} External links require the \href{}{} command. It appears the LaTeX export process no longer distinguishes internal and external links, as I believe it used to do. This is the problematic commit: commit f5918bdcc05d7924dc204b57307023eb1ef011f0 parent df5894cdcb10819560f003c5b94b8f5f2b7d33cf Date: Sun Oct 17 08:29:51 2010 + LaTeX export: use org-export-latex-hyperref-format I have just reverted this commit. - Carsten Looks like time to change the variable name which is actually confusing. Since href and hyperref are two different things, I renamed the existing `org-export-latex-hyperref-format' variable as `org-export-latex-href-format' and introduced a new one `org-export-latex-hyperref-format'. * org-latex.el (org-export-latex-hyperref-format): New option. (org-export-latex-href-format): Renamed the existing variable `org-export-latex-hyperref-format' as `org-export-latex-href-format' (org-export-latex-links): Use `org-export-latex-hyperref-format' and `org-export-latex-href-format' Thanks and Regards Noorul diff --git a/lisp/org-latex.el b/lisp/org-latex.el index cdc240c..8f0e0ea 100644 --- a/lisp/org-latex.el +++ b/lisp/org-latex.el @@ -295,7 +295,14 @@ markup defined, the first one in the association list will be used. :group 'org-export-latex :type 'string) -(defcustom org-export-latex-hyperref-format \\href{%s}{%s} +(defcustom org-export-latex-href-format \\href{%s}{%s} + A printf format string to be applied to href links. +The format must contain two %s instances. The first will be filled with +the link, the second with the link description. + :group 'org-export-latex + :type 'string) + +(defcustom org-export-latex-hyperref-format \\hyperref[%s]{%s} A printf format string to be applied to hyperref links. The format must contain two %s instances. The first will be filled with the link, the second with the link description. @@ -2016,10 +2023,10 @@ The conversion is made depending of STRING-BEFORE and STRING-AFTER. (insert (format (org-export-get-coderef-format path desc) (cdr (assoc path org-export-code-refs) -(radiop (insert (format \\hyperref[%s]{%s} +(radiop (insert (format org-export-latex-hyperref-format (org-solidify-link-text raw-path) desc))) ((not type) - (insert (format \\hyperref[%s]{%s} + (insert (format org-export-latex-hyperref-format (org-remove-initial-hash (org-solidify-link-text raw-path)) desc))) @@ -2030,7 +2037,7 @@ The conversion is made depending of STRING-BEFORE and STRING-AFTER. ;; a LaTeX issue, but we here implement a work-around anyway. (setq path (org-export-latex-protect-amp path) desc (org-export-latex-protect-amp desc))) - (insert (format org-export-latex-hyperref-format path desc))) + (insert (format org-export-latex-href-format path desc))) ((functionp (setq fnc (nth 2 (assoc type org-link-protocols ;; The link protocol has a function for formatting the link * lisp/org-latex.el (org-export-latex-links) : Replaced hard coded hyperref format with custom variable `org-export-latex-hyperref-format' Note that href is not same as hyperref. Jambunthan K. All the best, Tom On Oct 28, 2010, at 3:30 PM, Jambunathan K wrote: Thomas There was a hint at possible solution (or atleast a partial solution) in my original post. Did you try it before jumping in to rough waters or digging deeper? Do , | M-x customize-variable RET org-export-latex-hyperref-format' ` so that your .emacs has an entry like this , [.emacs] | | (custom-set-variables | '(org-export-latex-hyperref-format \\hyperref[%s]{%s})) | ` The above setting solves the problem for me with the following simple Org file. * Heading1 Make this section as large as possible so that it fills atleast a page. * Heading2 Links to [[Heading1]] Jambunathan K. Thomas S. Dye t...@tsdye.com writes: On Oct 28, 2010, at 12:35 PM, Nick Dokos wrote: Thomas S. Dye t...@tsdye.com wrote: On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote: This is a regression. release-7.01h is good. HEAD is bad. I get the following line with release-7.01h. Links to \hyperref[sec-1]{Heading1} Jambunathan K. Aloha Jambunathan K., Very many thanks for this information. I have
Re: [Orgmode] Re: Internal links in LaTeX export
Nick Dokos nicholas.do...@hp.com wrote: Thomas S. Dye t...@tsdye.com wrote: ... I did hit on a revision that was neither good nor bad: commit 8562273b272024a630a582b0e1b94c481d8abeec Author: Eric Schulte schulte.e...@gmail.com Date: Sat Oct 16 13:21:47 2010 -0600 ob-ref: don't forget arguments to referenced code blocks * lisp/ob-ref.el (org-babel-ref-resolve): bringing the referent arguments back to their params before evaluation This one puts these lines in *Messages* when I export to LaTeX executing Org code block... if: Symbol's value as variable is void: result-type Yeah, that was the error that stopped me cold as well, although I hit it In case it wasn't clear, that was a couple of days ago on a different bisection, while chasing another problem. on a different commit (I think) - there must be a way to get around the problem but it certainly makes things more difficult. I imagine the way to go is to find a commit before this error was introduced and a commit after it was fixed and try those with your problem: it might allow you to bypass the problematic range (in which case, you might be able to continue bisecting all the way to the end), or it might limit the bad commit to this range - the latter is still valuable to know but certainly not as definitive as this is the bad commit. And in any case, all of this would fall into the advanced appendix in the git bisection book. Sorry it didn't pan out but I hope that you had fun digging, In this instance, I actually bisected it down to the bad commit that Jambunathan K. identified (and Carsten reverted). I guess I was lucky in the sense that I pulled a couple of days ago, so HEAD was 851 commits ahead of 7.01h and the bisection proceeded as follows: release_7.01h-851-gfd9e933 - bad release_7.01h - good release_7.01h-425-gfea9072 - good release_7.01h-638-gd9e4469 - good release_7.01h-744-g3d2aec3 - bad release_7.01h-691-g6b9782d - good release_7.01h-717-gc9bb51e - bad release_7.01h-704-g935c310 - good release_7.01h-710-gc9b0176 - good release_7.01h-713-g8820a25 - good release_7.01h-715-gf5918bd - bad release_7.01h-714-gdf5894c - good and it identified release_7.01h-715-gf5918bd as the first bad commit. From the previous investigation, I know that the result-type error that you ran into, was introduced after commit 750 and resolved before commit 800 (using release_7.01h as the origin), so once I got to the point above, I was safe: I couldn't possibly end up in the problematic range. OTOH, if you start from say 810, the sequence would be 405, 608, 709, 759 (or so) and you end up in the problematic range, which is probably what happened to you. BTW, I got the bisection sequence (after the fact) with git bisect log and then translated the (40-hex digit SHA1 form) commits to the more readable form above using git describe commit This is all 20/20 hindsight of course, but I hope interesting enough as a curiosity. Nick ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode