Re: [O] [BUG] Inconsistency in src block hiding
Again, drawers are in-line with standard hiding methods. Though, their behaviour with regards to export needs to be changed (i.e. by default simply export contents of the drawer instead of ignoring it). I think we should drop any #+result: or #+name: hiding and take another route. It's not their job anyway. Fair enough, I like this idea. So let's work towards drawers rehabilitation. The attached patch entirely removes the #+name and #+results based hiding. Note that the existing wrap argument to the :results header argument will wrap results in a block which allows easy tab-based result hiding. As this is a relatively large change I hesitate to apply it outright, although I do agree that it leads to simpler more consistent behavior. If general consensus seems to support the application of this patch then I will be happy to apply it. Best, From 8eec0e67d0e9ea703f0449310ca4db8c600e880f Mon Sep 17 00:00:00 2001 From: Eric Schulte schulte.e...@gmail.com Date: Mon, 28 Nov 2011 00:43:35 -0700 Subject: [PATCH] remove #+name and #+result hiding Given that arbitrary regions may already be hidden using a drawer the ability to hide any named entity is redundant. In addition the name based hiding does not mix well with other keywords. Thanks to Nicolas Goaziou for raising this issue and suggesting the removal of #+name based hiding. --- lisp/ob.el | 83 1 files changed, 0 insertions(+), 83 deletions(-) diff --git a/lisp/ob.el b/lisp/ob.el index dab40f4..5815fe6 100644 --- a/lisp/ob.el +++ b/lisp/ob.el @@ -975,89 +975,6 @@ This can be called with C-c C-c. (when hash (kill-new hash) (message hash (add-hook 'org-ctrl-c-ctrl-c-hook 'org-babel-hash-at-point) -(defun org-babel-result-hide-spec () - Hide portions of results lines. -Add `org-babel-hide-result' as an invisibility spec for hiding -portions of results lines. - (add-to-invisibility-spec '(org-babel-hide-result . t))) -(add-hook 'org-mode-hook 'org-babel-result-hide-spec) - -(defvar org-babel-hide-result-overlays nil - Overlays hiding results.) - -(defun org-babel-result-hide-all () - Fold all results in the current buffer. - (interactive) - (org-babel-show-result-all) - (save-excursion -(while (re-search-forward org-babel-result-regexp nil t) - (save-excursion (goto-char (match-beginning 0)) - (org-babel-hide-result-toggle-maybe) - -(defun org-babel-show-result-all () - Unfold all results in the current buffer. - (mapc 'delete-overlay org-babel-hide-result-overlays) - (setq org-babel-hide-result-overlays nil)) - -;;;###autoload -(defun org-babel-hide-result-toggle-maybe () - Toggle visibility of result at point. - (interactive) - (let ((case-fold-search t)) -(if (save-excursion - (beginning-of-line 1) - (looking-at org-babel-result-regexp)) -(progn (org-babel-hide-result-toggle) - t) ;; to signal that we took action - nil))) ;; to signal that we did not - -(defun org-babel-hide-result-toggle (optional force) - Toggle the visibility of the current result. - (interactive) - (save-excursion -(beginning-of-line) -(if (re-search-forward org-babel-result-regexp nil t) -(let ((start (progn (beginning-of-line 2) (- (point) 1))) - (end (progn - (while (looking-at org-babel-multi-line-header-regexp) - (forward-line 1)) - (goto-char (- (org-babel-result-end) 1)) (point))) - ov) - (if (memq t (mapcar (lambda (overlay) -(eq (overlay-get overlay 'invisible) -'org-babel-hide-result)) - (overlays-at start))) - (if (or (not force) (eq force 'off)) - (mapc (lambda (ov) - (when (member ov org-babel-hide-result-overlays) -(setq org-babel-hide-result-overlays - (delq ov org-babel-hide-result-overlays))) - (when (eq (overlay-get ov 'invisible) -'org-babel-hide-result) -(delete-overlay ov))) -(overlays-at start))) -(setq ov (make-overlay start end)) -(overlay-put ov 'invisible 'org-babel-hide-result) -;; make the block accessible to isearch -(overlay-put - ov 'isearch-open-invisible - (lambda (ov) - (when (member ov org-babel-hide-result-overlays) - (setq org-babel-hide-result-overlays - (delq ov org-babel-hide-result-overlays))) - (when (eq (overlay-get ov 'invisible) - 'org-babel-hide-result) - (delete-overlay ov -(push ov org-babel-hide-result-overlays))) - (error Not looking at a result line - -;; org-tab-after-check-for-cycling-hook
Re: [O] [org-babel] switching off (re-)evaluation of code blocks during Org export
Dear Eric, Sorry for the noise, it works fine. see the manual for valid values for the eval header argument. I actually did, but only the online version so far. Of course, for such changes I had to check the doc sources... Anyway, thanks a lot!! Best wishes, Torsten On 28 Nov 2011, at 07:13, Eric Schulte wrote: Hi Torsten, Change non-export to no-export, see the manual for valid values for the eval header argument. Best -- Eric Torsten Anders torsten.and...@beds.ac.uk writes: Dear Eric, Apologies for my late response (too much teaching and admin in this new job :-P). Thanks a lot again for kingly adding the eval header argument non-export. From what I understand in your message this would be exactly what I was looking for (allow interactive evaluation, but inhibit code block evaluation during export). I just pulled the latest org sources and tested your addition. Unfortunately, even when using this header argument value, code blocks in both Lilypond and Fomus are still executed when the buffer is exported to either PDF (via Latex) or HTML. Below is a test that I understood should not execute during export. Am I missing something? #+begin_src fomus :eval non-export :results silent :file fomus-test.ly time 1 dur 1 pitch 60; #+end_src [[file:fomus-test.pdf]] Thanks a lot again! Best wishes, Torsten On 22 Nov 2011, at 01:23, Eric Schulte wrote: Hi Torsten, Torsten Anders torsten.and...@beds.ac.uk writes: Dear Sebastien and Eric, Thanks a lot for your kind replies. However, this is not yet quite what I am after. I want to be able to manually execute each code block, but not automatically whenever the whole document is rendered. So, I would always switch on/off eval never. Hm... I've just pushed up a patch which adds a new option to the eval header argument. Setting eval to non-export will now allow interactive evaluation, but will inhibit code block evaluation during export. This should address your need as I understand it. I will try out the :cache header argument. However, again this does not work so well, because for the languages I am using the :file argument does not work very well (I have to manually change extensions, so I include the resulting file links by hand anyway and set :results to silent. So, I it sounds like few org-babel users is really running larger applications in their code blocks which can delay the export of the whole document considerably. I would not jump to that conclusion. I have used babel code blocks to cache the results of very long running results, however between the :cache header argument and the ability to manually disassociate generated results from code blocks I have not had any problems inhibiting execution during export. Best -- Eric Anyway, thanks a lot for your feedback. Best wishes, Torsten -- Eric Schulte http://cs.unm.edu/~eschulte/ -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [ANN] Org Export in contrib
On Nov 27, 2011, at 8:54 PM, Nicolas Goaziou wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
2. The document title cannot be obtained anymore from the first line of
text. It's either explicitely defined with the =TITLE= keyword, or
derived from buffer's name.
This is actually good, I think. Much of the stuff like initial text,
title from text etc are leftovers from early time. It might mean that
we will have to keep the old exporters around somewhere, if someone
needs compatibility.
We're not there yet. But I hope there will be no backward compatibility.
We really should remove from all export unrelated code the export
related text-properties.
Yes, I agree.
4. [TABLE OF CONTENTS] as a placeholder for the table of contents has
been removed. Though, a new keyword, =TOC=, achieves the same
effect, and can even take more values, like contents, tables,
figures and listings. Tools are provided to make them available
to any exporter to come.
What do you mean by keyword? Can you provide an example of how
to place the TOC?
Just put #+toc: headlines, #+toc: tables, #+toc: listings, #+toc:
figures anywhere in the document (at least with the LaTeX back-end).
OK, thanks.
6. Macros have been under powered a little. They cannot live anymore in
comments, example blocks, or even src blocks. In fact, one cannot
find a macro where the text isn't parsed. Macros are Org syntax.
Using such syntax where there is, by definition, none is just
nonsensical.
I know that Stefan Vollmar is using macros in complicated and
extensive ways. I also know that he is using the index facilities,
which so far have depended heavily on the preprocessor. I am curious
how indexing will work with org-elements. Have you put any thought
into this?
I don't think that macros will be a source of problems since comments
and example blocks were weird locations for them anyway.
In the LaTeX exporter, #+index: something will be transcoded into
\index{something}. That's about it.
Should the generic export build a list of all #+index: values and
store it in a `:index' property (accessible through the communication
channel)?
Yes, I think so!
9. Table.el tables will always use their own export back-end. In other
words, no Org syntax will be recognized in such table anymore.
A table.el is an extraneous element while the parser is meant to
parse Org syntax.
Maybe we should see if there is a hook in table.el which could
be called to format text in a backend specific way. If it is not
there, maybe we can simply introduce it ourselves, or add some
advice for this purpose
Ok. If anyone can look at it and determine the right thing to do, I will
merge it into the exporter code.
I will try to look at this possibility.
Cheers
- Carsten
11. =org-export-with-TeX-macros= has been replaced with the more
appropriate =org-export-with-entities=, and the associated =OPTIONS=
keyword's symbol changed from =TeX:nil= to =e:nil=.
I do like the change, but maybe it would be good to support TeX
for backward compatibility... Then, maybe, we are breaking a few
things anyway.
TeX is still supported as a latex-fragment. In the long run, though,
I think TeX commands that are not meant for dvipng/mathjax should be
called through an export snippet (that is @l{...} temporary syntax).
12. About variables changes, =org-export-author-info=,
=org-export-creator-info= and =org-export-email-info= have been
replaced with, respectively, =org-export-with-author=,
=org-export-with-creator= ad =org-export-with-email=, for the sake
of consistency with other opt-in variables.
Are you adding defvaralias for compatibility, or are you arguing for
a clean break here?
There is no defvaralias. Though, I don't mind adding them.
Regards,
--
Nicolas Goaziou
- Carsten
Re: [O] How to estimate effort by week?
Hi Bernt, thanks a lot for your advice. Sorry, but it took some time until I found the time for trying it. I think I understood how it works. Below I just have some minor questions. 2011-11-19 16:32 Bernt Hansen: Is this to help limit you to that time per week or for estimating? Indeed I was interested in limiting the time that I spend on some task. For limiting you can set up something like this: --8---cut here---start-8--- * STARTED Some task ^^^ OK, so this example uses another TOOD keyword, which I haven't had before. I understand that your example also works without introducing a new state, but I'm not yet sure what TODO states I need to use this feature most efficiently. See below for a more specific question about that. SCHEDULED:2011-11-21 Mon +1w :LOGBOOK: - State DONE from STARTED[2011-11-19 Sat 10:27] If I understand correctly, this mainly follows the habit tracking documented on the info page Tracking your habits – right? CLOCK: [2011-11-19 Sat 10:25]--[2011-11-19 Sat 10:27] = 0:02 CLOCK: [2011-11-19 Sat 09:28]--[2011-11-19 Sat 10:27] = 0:59 :END: :PROPERTIES: :Effort: 1:00 :LAST_REPEAT: [2011-11-19 Sat 10:27] :END: Limit work to 60 minutes per week Let it repeat for next week --8---cut here---end---8--- where the task repeats at some interval (weekly since you want to work up to 1 hour per week on this task). When you clock in the task the modeline shows your current clocked minutes on the task _since your last repeat_. OK, that's basically what I wanted to achieve, and it's very nice that the clocked minutes are also shown in a warning face here when I exceed the limit. Set your Effort property to the limit you want for the task for the interval and set your repeat to the size of your interval (1 hour per week in this case) So when you reach the limit of 1 hour (in this case) you mark the task DONE which stops the clock and rescheduled the task to the next repeat date. More realistically I won't do that after one hour, but continue working on that task (with a guilty conscience), and then mark it DONE around the end of the week ;-) OK, I see that marking such a task as DONE does not actually leave it in the DONE state but takes it back to the first TODO state. So far I had the TODO sequence TODO DELEGATED | DONE CANCELLED and tried to extend it to TODO DELEGATED STARTED | DONE CANCELLED, but that would take my repeating task back to TODO instead of STARTED after marking it DONE. I think a separate sequence of states would make more sense; maybe STARTED | RESTARTED? When you clock the task in again the modeline shows 0:00 and counts up to the effort limit again. Cheers, Christoph -- Christoph Lange, http://www.facebook.com/ch.lange, Skype duke4701
Re: [O] Open Drawer using keys or even better automatically
Dear Suvayu, at first: sorry for the late response. My last response is lost in space. I know how to export my thesis. This was just about having the ability to see nothing else but the headings and the synopsis itself, where the synopsis should be something like * The Heading :SYNOPSIS: Here we have the synopsis text :END: Here comes some very lengthy and boring text. What I'd wish to see is something like. * The Heading Here we have the synopsis text Like e.g. within the Scrivener Cardboard. Best Markus
Re: [O] Bug in latex export
Nobody out there able to reproduce? I still have trouble with this on org-mode 7.7 and ubuntu 11.10. Best Markus
[O] org-refile returns 'invalid target location' when refiling to file root
org-version 7.7 If I `C-c w` and attempt to refile a tree to the root of a file, the minibuffer displays invalid target location and org-mode fails to refile the tree. This works as expected when refiling to a heading within the same file, or if I have org-refile-use-outline-path set to `file` rather than `full-file-path`. (I have idential filenames in different paths, so I need to use full-file-path.) I expect this to work because of the documentation for org-refile-use-outline-path. Admittedly, this is under the heading of the `file` value, but I see no reason why it shouldn't be consistent across the two settings. In this case, you can also stop the completion after the file name, to get entries inserted as top level in the file. Do let me know if there's more useful information I can provide. ~jonathon Applicable `.emacs`: (setq org-refile-targets '( (nil :todo . PROJECT) (nil :maxlevel . 1) (org-files :maxlevel . 1) )) (setq org-refile-allow-creating-parent-nodes t) (setq org-refile-use-outline-path 'full-file-path)
[O] org table spreadsheet problem
hi,all. I have a orgtbl like the following, | # | 2 | a | | # | -2 | abc | | # | 5 | abc | | # | -3 | a | |---++-| | || | | ^ | x | | and i want to sum the second column which the corresponding third column's values=abc to variable x. (in this example $x = -2+5 = 3). what Formula syntax for Calc/Lisp can achieve this,please. thanks.
Re: [O] org table spreadsheet problem
Hi, Please check the following thread on a similar problem: http://thread.gmane.org/gmane.emacs.orgmode/29877/focus=29920 There is a definition for 'vsumif' function you can use to add conditionally. Regards, .j. On Mon, Nov 28, 2011 at 03:32:05PM +0800, qkbey...@gmail.com wrote: hi,all. I have a orgtbl like the following, | # | 2 | a | | # | -2 | abc | | # | 5 | abc | | # | -3 | a | |---++-| | || | | ^ | x | | and i want to sum the second column which the corresponding third column's values=abc to variable x. (in this example $x = -2+5 = 3). what Formula syntax for Calc/Lisp can achieve this,please. thanks.
Re: [O] org-refile returns 'invalid target location' when refiling to file root
Hi Jonathon, I have this in my .emacs file, maybe it helps. (setq org-refile-allow-creating-parent-nodes (quote confirm)) Cheers, Viktor Jonathon Anderson wrote: org-version 7.7 If I `C-c w` and attempt to refile a tree to the root of a file, the minibuffer displays invalid target location and org-mode fails to refile the tree. This works as expected when refiling to a heading within the same file, or if I have org-refile-use-outline-path set to `file` rather than `full-file-path`. (I have idential filenames in different paths, so I need to use full-file-path.) I expect this to work because of the documentation for org-refile-use-outline-path. Admittedly, this is under the heading of the `file` value, but I see no reason why it shouldn't be consistent across the two settings. In this case, you can also stop the completion after the file name, to get entries inserted as top level in the file. Do let me know if there's more useful information I can provide. ~jonathon Applicable `.emacs`: (setq org-refile-targets '( (nil :todo . PROJECT) (nil :maxlevel . 1) (org-files :maxlevel . 1) )) (setq org-refile-allow-creating-parent-nodes t) (setq org-refile-use-outline-path 'full-file-path)
Re: [O] How to estimate effort by week?
Christoph LANGE ch.la...@jacobs-university.de writes: Hi Bernt, thanks a lot for your advice. Sorry, but it took some time until I found the time for trying it. I think I understood how it works. Below I just have some minor questions. Hi Christoph, The delay is not a problem at all. 2011-11-19 16:32 Bernt Hansen: Is this to help limit you to that time per week or for estimating? Indeed I was interested in limiting the time that I spend on some task. For limiting you can set up something like this: --8---cut here---start-8--- * STARTED Some task ^^^ OK, so this example uses another TOOD keyword, which I haven't had before. I understand that your example also works without introducing a new state, but I'm not yet sure what TODO states I need to use this feature most efficiently. See below for a more specific question about that. Yes, I use STARTED as a todo keyword and it gets automatically set when I clock in the task. My setup details are at http://doc.norang.ca/org-mode.html in case you want all the gory details. SCHEDULED:2011-11-21 Mon +1w :LOGBOOK: - State DONE from STARTED[2011-11-19 Sat 10:27] If I understand correctly, this mainly follows the habit tracking documented on the info page Tracking your habits – right? No this isn't a habit because it doesn't have a STYLE property. It's just a regular repeating todo task. A habit needs a repeater and a STYLE property with a value of 'habit'. CLOCK: [2011-11-19 Sat 10:25]--[2011-11-19 Sat 10:27] = 0:02 CLOCK: [2011-11-19 Sat 09:28]--[2011-11-19 Sat 10:27] = 0:59 :END: :PROPERTIES: :Effort: 1:00 :LAST_REPEAT: [2011-11-19 Sat 10:27] :END: Limit work to 60 minutes per week Let it repeat for next week --8---cut here---end---8--- where the task repeats at some interval (weekly since you want to work up to 1 hour per week on this task). When you clock in the task the modeline shows your current clocked minutes on the task _since your last repeat_. OK, that's basically what I wanted to achieve, and it's very nice that the clocked minutes are also shown in a warning face here when I exceed the limit. It works for me :) Set your Effort property to the limit you want for the task for the interval and set your repeat to the size of your interval (1 hour per week in this case) So when you reach the limit of 1 hour (in this case) you mark the task DONE which stops the clock and rescheduled the task to the next repeat date. More realistically I won't do that after one hour, but continue working on that task (with a guilty conscience), and then mark it DONE around the end of the week ;-) I don't always stop when I go over either - but my clocked time is shown with a bright red background I can't miss on the modeline and everytime I clock in the task (ie capture something clocks in the capture task and returns to this overrun task) my siren sound is played so it's very obvious. OK, I see that marking such a task as DONE does not actually leave it in the DONE state but takes it back to the first TODO state. When you mark a TODO task DONE (or CANCELLED or any other done-state keyword it cycles back to TODO or to a specific state you specify in a property REPEAT_TO_STATE) So far I had the TODO sequence TODO DELEGATED | DONE CANCELLED and tried to extend it to TODO DELEGATED STARTED | DONE CANCELLED, but that would take my repeating task back to TODO instead of STARTED after marking it DONE. I think a separate sequence of states would make more sense; maybe STARTED | RESTARTED? If you want to force the state to STARTED then add a property like this :PROPERTY: :REPEAT_TO_STATE: STARTED :END: Regards, Bernt
Re: [O] [ANN] Org Export in contrib
Carsten Dominik carsten.domi...@gmail.com writes: 9. Table.el tables will always use their own export back-end. In other words, no Org syntax will be recognized in such table anymore. A table.el is an extraneous element while the parser is meant to parse Org syntax. Maybe we should see if there is a hook in table.el which could be called to format text in a backend specific way. If it is not there, maybe we can simply introduce it ourselves, or add some advice for this purpose Ok. If anyone can look at it and determine the right thing to do, I will merge it into the exporter code. I will try to look at this possibility. Also, note that tables come with the `:type' property, which tells whether it is a table-el or not (it is either `org' or `table.el'). Thus, back-ends can already implement special actions when type is `table.el'. Isn't is sufficient? Regards, -- Nicolas Goaziou
[O] noweb problem
Dear Org babel developers, In the simple test below I would expect that the second cope block expands to ls ~, but seemingly it instead expands to ls only. What am I missing? #+srcname: sh-test-noweb #+begin_src sh ~ #+end_src #+begin_src sh :noweb yes ls sh-test-noweb #+end_src Did anything perhaps change in the literate programming interface? Apologies if I missed something obvious or if I am victim of some stupid typo. Thanks a lot! Best wishes, Torsten
[O] index.org; am I doing something wrong??
I created an index.org file and have been using that to organize all of my org files and create an Outline of my Notes etc... Is this the correct way to do it? because when i sync with MobileOrg then MobileOrg cannot open any of my files on my mobile device. What am I doing wrong? -- Cameron
Re: [O] org-refile returns 'invalid target location' when refiling to file root
On Mon, Nov 28, 2011 at 8:44 PM, Viktor Rosenfeld listuse...@googlemail.com wrote: I have this in my .emacs file, maybe it helps. (setq org-refile-allow-creating-parent-nodes (quote confirm)) Yeah, I have that too. Or, similar. (setq org-refile-allow-creating-parent-nodes t) ~jonathon
[O] Push files and views for MobileOrg
Whenever I push file and views for MobileOrg it does not setup the agendas.org file. Why?? How can I fix this? TIA, -- Cameron
Re: [O] noweb problem
Ah, thanks a lot! I should develop the habit of reading the documentation of the development version when using that version... Best wishes, Torsten On 28 Nov 2011, at 20:14, Eric Schulte wrote: Hi Torsten, The change here is in the naming conventions, srcname is no longer a valid method of naming a code block, try name instead. e.g., #+name: sh-test-noweb #+begin_src sh ~ #+end_src #+begin_src sh :noweb yes ls sh-test-noweb #+end_src Best, Torsten Anders torsten.and...@beds.ac.uk writes: Dear Org babel developers, In the simple test below I would expect that the second cope block expands to ls ~, but seemingly it instead expands to ls only. What am I missing? #+srcname: sh-test-noweb #+begin_src sh ~ #+end_src #+begin_src sh :noweb yes ls sh-test-noweb #+end_src Did anything perhaps change in the literate programming interface? Apologies if I missed something obvious or if I am victim of some stupid typo. Thanks a lot! Best wishes, Torsten -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] noweb problem
Hi Torsten, The change here is in the naming conventions, srcname is no longer a valid method of naming a code block, try name instead. e.g., #+name: sh-test-noweb #+begin_src sh ~ #+end_src #+begin_src sh :noweb yes ls sh-test-noweb #+end_src Best, Torsten Anders torsten.and...@beds.ac.uk writes: Dear Org babel developers, In the simple test below I would expect that the second cope block expands to ls ~, but seemingly it instead expands to ls only. What am I missing? #+srcname: sh-test-noweb #+begin_src sh ~ #+end_src #+begin_src sh :noweb yes ls sh-test-noweb #+end_src Did anything perhaps change in the literate programming interface? Apologies if I missed something obvious or if I am victim of some stupid typo. Thanks a lot! Best wishes, Torsten -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] [PATCH] Lilypond: added PDF output
Dear all, The current implementation how org-babel calls Lilypond hard-wires the supported output file formats to EPS and PNG. Attached is a very simple patch that adds support for PDF as well, so that resulting PDF files can be directly integrated in the PDF files generated by Latex and Latex Beamer support. Thanks! Best wishes, Torsten ob-lilypond.el.diff Description: Binary data
[O] org-bibtex does not work
Hi all,
I finally converted all my BibTex references into a org file.
Now I face the problem that I can't generate a BibTeX file.
org-bibtex ask me for the filename and then it seems to be stuck in a
infinite loop.
Only way to get out of this is using C-g.
The BibTeX file never appeared.
setting the debugger to start on quit (setq debug-on-quit) results in
Debugger entered--Lisp error: (quit)
bibtex-realign()
bibtex-reformat()
(progn (insert entry) (when tags (bibtex-beginning-of-entry) (if
(re-search-forward keywords.*=.*{\\(.*\\)} nil t) (progn (goto-char
(match-end 1)) (insert , )) (bibtex-make-field keywords t t))
(insert (mapconcat (function identity) tags , ))) (bibtex-reformat)
(buffer-string))
(unwind-protect (progn (insert entry) (when tags
(bibtex-beginning-of-entry) (if (re-search-forward
keywords.*=.*{\\(.*\\)} nil t) (progn (goto-char (match-end 1))
(insert , )) (bibtex-make-field keywords t t)) (insert (mapconcat
(function identity) tags , ))) (bibtex-reformat) (buffer-string))
(and (buffer-name temp-buffer) (kill-buffer temp-buffer)))
(save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
(insert entry) (when tags (bibtex-beginning-of-entry) (if
(re-search-forward keywords.*=.*{\\(.*\\)} nil t) (progn (goto-char
(match-end 1)) (insert , )) (bibtex-make-field keywords t t))
(insert (mapconcat (function identity) tags , ))) (bibtex-reformat)
(buffer-string)) (and (buffer-name temp-buffer) (kill-buffer
temp-buffer
followed by many many more lines.
I tried to export a single entry in a own buffer as well without
success. I skipped my entire emacs settings and used a bare-bone emacs
with exactly the same result.
As from the debugger it seems to be a problem of the internal bibtex
mode. However, I hope someone here is capable to help. I updated both
emacs and org-mode without luck
org-mode 7.7 (git build from today)
emacs GNU Emacs 24.0.91.1 (bzr build from today)
Would be helpfull already if someone could confirm whether it works at
the moment or whether it seems broken
Thanks
Torsten
Re: [O] [ANN] Org Export in contrib
On 11/25/2011 06:32 PM, Nicolas Goaziou wrote: Hello, I've pushed org-export.el to contrib. It's a general export engine, built on top of org-elements aiming at simplifying life of both developers and maintainers (and, therefore, of end-users). Hi Nicolas, I'd like to make same remarks regarding the Wikipedia exporter included in the generic exporter: Is the exporter supposed to export a whole wiki or a sub-wiki from a org-file or a single wiki page? If it is to be only a single wiki page, could you change the variables :body-section-header-prefix and :body-section-header-suffix to begin with == instead of =? The level 1 headings are supposed to be only used for the page title (cf. http://www.mediawiki.org/wiki/Help:Formatting and the note on the talks page http://www.mediawiki.org/wiki/Help_talk:Formatting#Level_1). Second, when I format my org file like this: * heading some text. some text. some text. the text currently gets exported with the leading blanks. This causes the Mediawiki to render the text as preformatted. Is there a way around this? Thanks you very much. Best regards Robert
Re: [O] [ANN] Org Export in contrib
Umm, sorry, I just found out, I was talking about the other generic exporter :( Robert On 11/29/2011 07:15 AM, Robert Klein wrote: On 11/25/2011 06:32 PM, Nicolas Goaziou wrote: Hello, I've pushed org-export.el to contrib. It's a general export engine, built on top of org-elements aiming at simplifying life of both developers and maintainers (and, therefore, of end-users). Hi Nicolas, I'd like to make same remarks regarding the Wikipedia exporter included in the generic exporter: Is the exporter supposed to export a whole wiki or a sub-wiki from a org-file or a single wiki page? If it is to be only a single wiki page, could you change the variables :body-section-header-prefix and :body-section-header-suffix to begin with == instead of =? The level 1 headings are supposed to be only used for the page title (cf. http://www.mediawiki.org/wiki/Help:Formatting and the note on the talks page http://www.mediawiki.org/wiki/Help_talk:Formatting#Level_1). Second, when I format my org file like this: * heading some text. some text. some text. the text currently gets exported with the leading blanks. This causes the Mediawiki to render the text as preformatted. Is there a way around this? Thanks you very much. Best regards Robert
Re: [O] org-refile returns 'invalid target location' when refiling to file root
Jonathon Anderson wrote: On Mon, Nov 28, 2011 at 8:44 PM, Viktor Rosenfeld listuse...@googlemail.com wrote: I have this in my .emacs file, maybe it helps. (setq org-refile-allow-creating-parent-nodes (quote confirm)) Yeah, I have that too. Or, similar. Sorry, don't know how I missed that in your last mail. Cheers, Viktor
