[Orgmode] text-mode-abbrev-table default?
Hi, with abbrev-mode, org-mode made his own (org-mode-abbrev-table) - empty, which was unconvenient, as I declared a lot of abbrevs in text-mode already. Solved it by (add-hook 'org-mode-hook '(lambda () (setq local-abbrev-table text-mode-abbrev-table))) However, as org-mode is a text-mode, why not use `text-mode-abbrev-table' by default? Thanks Andreas -- https://code.launchpad.net/s-x-emacs-werkstatt/ http://bazaar.launchpad.net/~a-roehler/python-mode/python-mode.el/ ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bugs when converting to LaTeX
Hi Sebastien, On Oct 27, 2009, at 9:47 AM, Sébastien Vauban wrote: Unfortunately, this is a weakness of the list parser in the LaTeX exporter. It cannot handle this kind of post-subitem text in an item list. This really must be fixed, and it is on my list, but it is hard. Hopefully, this will be fixed soon, because this is quite scary. Though, that does not imply it is easy to do... Be my guest to give it a try. Here a couple of other conversion bugs that I found: --8<---cut here---start->8--- - /S'il faut remodéliser ce qui est dans le code COBOL, comment faire ? Discussions avec le business, relire le COBOL ? Chez nous, la tarification n'est pas modélisée. Pourtant, c'est là qu'il faut aller vite vis-à-vis du marché./ You need to configure `org-emphasis-regexp-components' and increase the number of newlines allowed in these expressions. The above "question" (in a FAQ) should be in italics. But, to do so, we have to split it in multiple chunks in italics: - /S'il faut remodéliser ce qui est dans le code COBOL, comment faire ?/ /Discussions avec le business, relire le COBOL ?/ /Chez nous, la tarification n'est pas modélisée./ /Pourtant, c'est là qu'il faut aller vite vis-à-vis du marché./ - Le /challenge/ : efficacité et rapidité... Here, the word challenge is not in italics because the following character is an unbreakable space (*not* a normal space). Note -- I'm forced to use such characters in order to get my LaTeX PDF correctly outputted. I don't understand that. Could you please elaborate? Maybe you can fix this by adding your unbreakable space in org- emphasis-regexp-components to the end of the second string of characters, these are the characters allowed after an emphasis string. HTH - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] text-mode-abbrev-table default?
On Oct 27, 2009, at 10:45 PM, Andreas Roehler wrote: Hi, with abbrev-mode, org-mode made his own (org-mode-abbrev-table) - empty, which was unconvenient, as I declared a lot of abbrevs in text-mode already. Solved it by (add-hook 'org-mode-hook '(lambda () (setq local-abbrev-table text- mode-abbrev-table))) However, as org-mode is a text-mode, why not use `text-mode-abbrev-table' by default? Because if I do tis by default, someone if going to want to have a separate table :-) You solution is good - a nice snippet for a FAQ, maybe? - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Quotation marks in links in LaTeX export
Hi Brenton,
thanks for your report, this bug is fixed now.
- Carsten
On Oct 27, 2009, at 4:42 AM, Brenton Kenkel wrote:
Dear all,
I found an apparent minor bug with links containing quotation marks
in LaTeX export. If the first character in the name of a link is a
quotation mark, it is converted to a closing mark rather than an
opening mark. For example:
,
| * test
|
| [[http://www.google.com]["hello";]]
| [[http://www.google.com]["two"; "quotes"]]
`
This produces:
,
| \href{http://www.google.com}{''hello''}
| \href{http://www.google.com}{''two'' ``quotes''}
`
I am using org-mode 6.32 with Emacs 23.1 on Mac OS X.
Thank you,
Brenton Kenkel
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Separate function for config listing from org-submit-bug-report
Hi Jeff, I don't know why you are being prompted for you IMAP password, but regardless of this the email should not be send automatically. So I think you can go through the process and then copy the text and just not send the message! I cannot easily isolate this, because my code only produces the list of interesting variables. Some code in reporter.el does the quoting and insertion. - Carsten On Oct 26, 2009, at 8:50 PM, Jeff Kowalczyk wrote: The code to list a user's Org configuration which differs from the defaults is very useful. However, I've never run the M-x org-submit-bug-report command to completion, since I'm prompted for my GMail IMAP password before the config output is shown. I wouldn't want to spam the list with test data. I'd like to make a feature request that the configuration-dump code be refactored to a separate command which can be inserted at point or to a new buffer. org-submit-bug-report would call this function to build it's message. I couldn't get the form inside of (org.el): (when (yes-or-no-p "Include your Org-mode configuration ") ) to execute in the scratch buffer. Thanks, Jeff ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: text-mode-abbrev-table default?
On 2009-10-28 09:19 +, Carsten Dominik wrote: > Because if I do tis by default, someone if going to want > to have a separate table :-) > > You solution is good - a nice snippet for a FAQ, maybe? It seems natural to `define-abbrev-table' org-mode-abbrev-table with text-mode-abbrev-table being its parent ;) Leo -- Emacs uptime: 36 days, 1 hour, 45 minutes, 0 seconds ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: text-mode-abbrev-table default?
On Oct 28, 2009, at 11:32 AM, Leo wrote: On 2009-10-28 09:19 +, Carsten Dominik wrote: Because if I do tis by default, someone if going to want to have a separate table :-) You solution is good - a nice snippet for a FAQ, maybe? It seems natural to `define-abbrev-table' org-mode-abbrev-table with text-mode-abbrev-table being its parent ;) Org-mode is defined using define-derived-mode, so maybe that should already do this? - Carsten Leo -- Emacs uptime: 36 days, 1 hour, 45 minutes, 0 seconds ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [Announce:] org-git-link
[also replying to the list] Fixed on github, thanks. -- Dr. Reimar Finken(fin...@theo2.physik.uni-stuttgart.de) II. Institut für Theoretische Physik, Universität Stuttgart Pfaffenwaldring 57 Tel: 0711-68564924 70550 Stuttgart, Germany Fax: 0711-68564902 ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Exporting blocks without removing indentation
Fairly late in the export process, org-exp removes the common indentation from lines inside blocks (line 2288 of org-exp.el): (setq rtn (org-remove-indentation code)) However, what do we do if 1. A user has a block that she wishes to export with the indentation intact? 2. An org-exp-blocks plugin has a block that it wishes to export with the indentation intact? I propose that we make (1) and (2) possible. An example where (1) arises is if, when documenting a moderately complex program, different parts of a class or function are contained in separate blocks. Q1. Is that aim approved of? (2) is a bit trickier than (1). To solve (1), we could introduce a fix in org-exp.el like - (setq rtn (org-remove-indentation code)) + (setq rtn (if org-src-preserve-indentation code + (org-remove-indentation code))) However in solving (2) the plugin cannot assume that the variable org-src-preserve-indentation is in effect (in fact it very likely isn't). So we need to come up with a way in which the block resulting from an org-exp-blocks plugin can have its indentation survive through to the export product, even if org-src-preserve-indentation is globally nil. Two possibilities are 1. We adopt a convention whereby if all lines start with some character (say ,) then that character is removed (but the remaining indentation is left intact.) 2. We transplant the indentation-removing work from org-exp.el into org-exp-blocks.el, and arrange that it is only performed if the block is *not* handled by an org-exp-blocks plugin. Q2. Has this made sense? What solution do you suggest? Q3. Should we use org-src-preserve-indentation in this way to affect export? (It currently has effect when switching between the org buffer and the code edit buffer.) Dan ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Differences html/pdf
I normally prefer to export to pdf but I see that there are some differences. I added #+OPTIONS: toc:nil \n:nil todo:nil and toc is not exported in both, todo are anyway always exported and newline are kept only in html. In the latex version they're not exported for some reasons... Should I set some nice secret variable? ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: text-mode-abbrev-table default?
On 2009-10-28 10:37 +, Carsten Dominik wrote: >> It seems natural to `define-abbrev-table' org-mode-abbrev-table with >> text-mode-abbrev-table being its parent ;) > > Org-mode is defined using define-derived-mode, so maybe that should > already do this? > > - Carsten I tested it in GNU Emacs 23.1.50.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54) of 2009-09-22 and it seems abbrevs in text-mode is not inherited. Leo ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Problem with icalendar export: all items with active timestamps are being exported
Hi! I'm trying to get a sane export to my google calendar from org mode and so I'm playing with org-export-icalendar-combine-agenda-files Here the (hopefully relevant) subset of my settings: '(org-combined-agenda-icalendar-file "~/git/Org/home/org.ics") '(org-icalendar-categories (quote (all-tags category todo-state))) '(org-icalendar-include-body 1000) '(org-icalendar-include-sexps nil) '(org-icalendar-include-todo nil) '(org-icalendar-store-UID t) '(org-icalendar-timezone "Europe/Berlin") '(org-icalendar-use-deadline (quote (event-if-not-todo event-if-todo))) '(org-icalendar-use-scheduled (quote (event-if-not-todo event-if-todo))) Thing is, I'd like to get *only* scheduled or deadlined TODO items in my ics file, and I'd expect that setting (org-icalendar-include-todo nil) would export no other todo items. Unfortunately *every* item that has an active timestamp will be exported this way, even if it's not SCHEDULED: or DEADLINE:. Maybe I misunderstand the docs, but it looks like the check for (when org-icalendar-include-todo ...) in org-icalendar.le won't ever be relvant at all. (And the indentation of the when block is wrong, at least in my git checkout from today (I just refreshed it, to make sure).) Any idea? -- Friedrich Delgado Friedrichs TauPan on Ircnet and Freenode ;) ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] text-mode-abbrev-table default?
Carsten Dominik wrote: > > On Oct 27, 2009, at 10:45 PM, Andreas Roehler wrote: > >> >> Hi, >> >> with abbrev-mode, org-mode made his own >> (org-mode-abbrev-table) - empty, which was >> unconvenient, as I declared a lot of abbrevs in >> text-mode already. >> >> Solved it by >> >> (add-hook 'org-mode-hook '(lambda () (setq local-abbrev-table >> text-mode-abbrev-table))) >> >> However, as org-mode is a text-mode, why not use >> `text-mode-abbrev-table' by default? > > Because if I do tis by default, someone if going to want > to have a separate table :-) > > You solution is good - a nice snippet for a FAQ, maybe? > > - Carsten > > > Don't know. Just one remark still in this matter: Some modes as text-mode, org-mode are useful for non-programmers too. However, emacs' didactic already is somehow backward bothering people with keys instead mentioning mnemonic function-names. It's important to reflect how much a newbie/non-programmer may learn. IMHO the use of `customize' with its different types - string, regexp, boolean - its enough already. Requiring knowledge and use of things like `add-hook' is simply too much - emacs will lose this people. So what about introducing a customizable var saying `use-text-mode-abbrev-table'? If set to `t', use it. As said - suggest it as default. Cheers Andreas ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
"Thomas S. Dye" writes: > On Oct 27, 2009, at 12:55 PM, Eric Schulte wrote: >> Although I still don't fully understand the need to embed latex >> *inside* >> of source-code blocks, perhaps the attached org-babel-latex.el file >> [1] >> will represent a simpler solution for embedding the results of >> source-code blocks in latex source-code blocks. It makes use of >> the :var org-babel header argument as shown in the attached example >> file >> [2]. To reproduce first load org-babel-latex.el and then evaluate the >> latex block (note the results are already in the file from my test >> evaluation). >> >> Hope this helps -- Eric >> >> Footnotes: >> [1] >> [2] > > Thanks for this, Eric. It looks neat. I was happy with all the > little .tex files, but agree with Torsten that this path is > potentially cleaner. > Please let me know if you do find this useful or have any suggestions. If it proves useful I will add it to the org-mode repository. > > In response to the implicit question in your comment, perhaps there > isn't a need to embed LaTeX inside source blocks and the uses to which > I put them could be accomplished in org-mode without them. My > programming skills are pretty crude and I'm aware that I'm a long way > from understanding org-mode and its vast potential. With that caveat, > here is my $0.02. > I'm also very far from taking full advantage of Org-mode export > > First, practical reasons: > > 1) I'm comfortable writing LaTeX and am particular about the results; > it is hard for me to map the inverse transformation through the org- > mode LaTeX exporter to express in org the particular LaTeX result I'm > after. > > 2) Someone on the list (Carsten?) mentioned a couple of days ago that > it wasn't reasonable to expect the org LaTeX exporter to capture the > full complexity of LaTeX (I'm paraphrasing, but I think that was the > gist); I ran up against an example of this (or so I think) when trying > to configure export to beamer code, where beamer's use of columns > tripped me up. > I fully understand your point. I guess that given my personal paucity of latex knowledge and abilities the same need has never occurred to me. In my case the Org-mode exported generally knows more about latex than I do. > > Second, conceptual reasons: > > 1) I consider writing LaTeX to be programming (here I mean no > disrespect to real programmers) and appreciate being able to do > literate LaTeX programming; the LaTeX source blocks let me write my > beamer presentation a slide or two at a time, just as I want them, > along with an adjacent source block for my print document, just as i > want it, that covers the same conceptual space, while I use the > surrounding org entries to document why I am doing things a particular > way, etc. > I see, you are using the org-mode file "a level above" the direct export. Maybe another option here would be to tag headlines based on which export target they are included within, and then base your exports on the headline tags (using #+EXPORT_INCLUDE_TAGS:), although I agree this also seems like an appropriate place to use the tangle functionality. > > 2) I think this workflow, with an org-mode meta-document that > encapsulates the print document and presentation materials, along with > the SQL, R, and Python code used to create the datasets and analyze > them, takes org-babel a step closer to realizing its potential as a > tool for reproducible research. Here, I am thinking of an org > document that captures the ways in which a piece of research is one > logical path among many possibilities, implemented and expressed in > one particular way (or two, if you want to distinguish print from > presentation) among many possibilities. > > The LaTeX source blocks in org-babel give me an easy and natural way > to accomplish these things. In the short time I've used them, they've > yielded results that impress me. I'm confident they hold much more > potential than I've been able to tap. > I didn't mean to imply that because I didn't understand the need for direct inclusion of latex code there *wasn't* a need for direct inclusion of latex code :) Thanks for the explanation. > > It is a real pleasure leveraging your good work. > It is a pleasure to be able to participate in such a nice open-source community. -- Eric > > Tom ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Problem with icalendar export: all items with active timestamps are being exported
Hi Friedrich, you don't want normal time stamps in your agenda as events??? Well, this is an unusual idea. Well, pull from git and the say (setq org-icalendar-use-plain-timestamp nil) HTH - Carsten On Oct 28, 2009, at 3:49 PM, Friedrich Delgado Friedrichs wrote: Hi! I'm trying to get a sane export to my google calendar from org mode and so I'm playing with org-export-icalendar-combine-agenda-files Here the (hopefully relevant) subset of my settings: '(org-combined-agenda-icalendar-file "~/git/Org/home/org.ics") '(org-icalendar-categories (quote (all-tags category todo-state))) '(org-icalendar-include-body 1000) '(org-icalendar-include-sexps nil) '(org-icalendar-include-todo nil) '(org-icalendar-store-UID t) '(org-icalendar-timezone "Europe/Berlin") '(org-icalendar-use-deadline (quote (event-if-not-todo event-if-todo))) '(org-icalendar-use-scheduled (quote (event-if-not-todo event-if-todo))) Thing is, I'd like to get *only* scheduled or deadlined TODO items in my ics file, and I'd expect that setting (org-icalendar-include-todo nil) would export no other todo items. Unfortunately *every* item that has an active timestamp will be exported this way, even if it's not SCHEDULED: or DEADLINE:. Maybe I misunderstand the docs, but it looks like the check for (when org-icalendar-include-todo ...) in org-icalendar.le won't ever be relvant at all. (And the indentation of the when block is wrong, at least in my git checkout from today (I just refreshed it, to make sure).) Any idea? -- Friedrich Delgado Friedrichs TauPan on Ircnet and Freenode ;) ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: text-mode-abbrev-table default?
On Oct 28, 2009, at 11:32 AM, Leo wrote: On 2009-10-28 09:19 +, Carsten Dominik wrote: Because if I do tis by default, someone if going to want to have a separate table :-) You solution is good - a nice snippet for a FAQ, maybe? It seems natural to `define-abbrev-table' org-mode-abbrev-table with text-mode-abbrev-table being its parent ;) Hmm, after reconsidering, I think you are right. How exactly would that look like? Should that be a top-level form in org.el? And should I then define org-mode with :abbrev-table org-mode-abbrev- table ? Just make me a patch, and I will apply it. Thanks. - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Differences html/pdf
On Oct 28, 2009, at 3:16 PM, andrea Crotti wrote: I normally prefer to export to pdf but I see that there are some differences. I added #+OPTIONS: toc:nil \n:nil todo:nil and toc is not exported in both, todo are anyway always exported This is about the TODO keywords, and they are stripped in both and newline are kept only in html. In the latex version they're not exported for some reasons... That is correct, we have not implemented keeping all line breaks in LaTeX. Too hard, unfortunately. - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Exporting blocks without removing indentation
Hi Dan, maybe the easiest way to implement this would be a -i (or whatever) switch a the src block. Switches are being processed already, so it will be simple to add one, I think. - Carsten On Oct 28, 2009, at 2:29 PM, Dan Davison wrote: Fairly late in the export process, org-exp removes the common indentation from lines inside blocks (line 2288 of org-exp.el): (setq rtn (org-remove-indentation code)) However, what do we do if 1. A user has a block that she wishes to export with the indentation intact? 2. An org-exp-blocks plugin has a block that it wishes to export with the indentation intact? I propose that we make (1) and (2) possible. An example where (1) arises is if, when documenting a moderately complex program, different parts of a class or function are contained in separate blocks. Q1. Is that aim approved of? (2) is a bit trickier than (1). To solve (1), we could introduce a fix in org-exp.el like - (setq rtn (org-remove-indentation code)) + (setq rtn (if org-src-preserve-indentation code + (org-remove-indentation code))) However in solving (2) the plugin cannot assume that the variable org-src-preserve-indentation is in effect (in fact it very likely isn't). So we need to come up with a way in which the block resulting from an org-exp-blocks plugin can have its indentation survive through to the export product, even if org-src-preserve-indentation is globally nil. Two possibilities are 1. We adopt a convention whereby if all lines start with some character (say ,) then that character is removed (but the remaining indentation is left intact.) 2. We transplant the indentation-removing work from org-exp.el into org-exp-blocks.el, and arrange that it is only performed if the block is *not* handled by an org-exp-blocks plugin. Q2. Has this made sense? What solution do you suggest? Q3. Should we use org-src-preserve-indentation in this way to affect export? (It currently has effect when switching between the org buffer and the code edit buffer.) Dan ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[babel] Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
Dear thread participants, please note that we were breaking the rule of prepending the subject line with the string [babel]! One question inline below. "Eric Schulte" writes: > "Thomas S. Dye" writes: > >> On Oct 27, 2009, at 12:55 PM, Eric Schulte wrote: > >>> Although I still don't fully understand the need to embed latex >>> *inside* >>> of source-code blocks, perhaps the attached org-babel-latex.el file >>> [1] >>> will represent a simpler solution for embedding the results of >>> source-code blocks in latex source-code blocks. It makes use of >>> the :var org-babel header argument as shown in the attached example >>> file >>> [2]. To reproduce first load org-babel-latex.el and then evaluate the >>> latex block (note the results are already in the file from my test >>> evaluation). >>> >>> Hope this helps -- Eric >>> >>> Footnotes: >>> [1] >>> [2] >> >> Thanks for this, Eric. It looks neat. I was happy with all the >> little .tex files, but agree with Torsten that this path is >> potentially cleaner. >> > > Please let me know if you do find this useful or have any suggestions. > If it proves useful I will add it to the org-mode repository. Am I right in thinking that one issue remaining in this thread is that we currently have no means of tangling the output of org-babel-latex? Thus the 'begin_src latex' blocks that we can tangle have unevaluated variables, and the resulting 'begin_latex' blocks have evaluated variables but can't be tangled? (We could extend tangling to cover such blocks, or perhaps preferably use ':results code' to generate 'begin_src latex' blocks?) Dan > >> >> In response to the implicit question in your comment, perhaps there >> isn't a need to embed LaTeX inside source blocks and the uses to which >> I put them could be accomplished in org-mode without them. My >> programming skills are pretty crude and I'm aware that I'm a long way >> from understanding org-mode and its vast potential. With that caveat, >> here is my $0.02. >> > > I'm also very far from taking full advantage of Org-mode export > >> >> First, practical reasons: >> >> 1) I'm comfortable writing LaTeX and am particular about the results; >> it is hard for me to map the inverse transformation through the org- >> mode LaTeX exporter to express in org the particular LaTeX result I'm >> after. >> >> 2) Someone on the list (Carsten?) mentioned a couple of days ago that >> it wasn't reasonable to expect the org LaTeX exporter to capture the >> full complexity of LaTeX (I'm paraphrasing, but I think that was the >> gist); I ran up against an example of this (or so I think) when trying >> to configure export to beamer code, where beamer's use of columns >> tripped me up. >> > > I fully understand your point. I guess that given my personal paucity > of latex knowledge and abilities the same need has never occurred to > me. In my case the Org-mode exported generally knows more about latex > than I do. > >> >> Second, conceptual reasons: >> >> 1) I consider writing LaTeX to be programming (here I mean no >> disrespect to real programmers) and appreciate being able to do >> literate LaTeX programming; the LaTeX source blocks let me write my >> beamer presentation a slide or two at a time, just as I want them, >> along with an adjacent source block for my print document, just as i >> want it, that covers the same conceptual space, while I use the >> surrounding org entries to document why I am doing things a particular >> way, etc. >> > > I see, you are using the org-mode file "a level above" the direct > export. Maybe another option here would be to tag headlines based on > which export target they are included within, and then base your exports > on the headline tags (using #+EXPORT_INCLUDE_TAGS:), although I agree > this also seems like an appropriate place to use the tangle > functionality. > >> >> 2) I think this workflow, with an org-mode meta-document that >> encapsulates the print document and presentation materials, along with >> the SQL, R, and Python code used to create the datasets and analyze >> them, takes org-babel a step closer to realizing its potential as a >> tool for reproducible research. Here, I am thinking of an org >> document that captures the ways in which a piece of research is one >> logical path among many possibilities, implemented and expressed in >> one particular way (or two, if you want to distinguish print from >> presentation) among many possibilities. >> >> The LaTeX source blocks in org-babel give me an easy and natural way >> to accomplish these things. In the short time I've used them, they've >> yielded results that impress me. I'm confident they hold much more >> potential than I've been able to tap. >> > > I didn't mean to imply that because I didn't understand the need for > direct inclusion of latex code there *wasn't* a need for direct > inclusion of latex code :) Thanks for the explanation. > >> >> It is a real pleasure leveraging your good work. >> > > It
Re: [Orgmode] Re: text-mode-abbrev-table default?
Carsten Dominik wrote: > > On Oct 28, 2009, at 11:32 AM, Leo wrote: > >> On 2009-10-28 09:19 +, Carsten Dominik wrote: >>> Because if I do tis by default, someone if going to want >>> to have a separate table :-) >>> >>> You solution is good - a nice snippet for a FAQ, maybe? >> >> It seems natural to `define-abbrev-table' org-mode-abbrev-table with >> text-mode-abbrev-table being its parent ;) > > Hmm, after reconsidering, I think you are right. > > How exactly would that look like? Should that be a top-level form in > org.el? > And should I then define org-mode with :abbrev-table > org-mode-abbrev-table ? > > Just make me a patch, and I will apply it. > > Thanks. > > - Carsten > > > It would be great, if user could choose the appropriate abbrev-table via customize too. For example my text-mode-abbrev-table contains german abbrevs, while writing this text an (english-mode-abbrev-table) is present. It might be useful being able to keep several org-mode projects witch different language abbrev tables. Thanks, Grüße Andreas ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
On Oct 28, 2009, at 5:19 AM, Eric Schulte wrote: I see, you are using the org-mode file "a level above" the direct export. Maybe another option here would be to tag headlines based on which export target they are included within, and then base your exports on the headline tags (using #+EXPORT_INCLUDE_TAGS:), although I agree this also seems like an appropriate place to use the tangle functionality. Eric, Thanks for pointing this out. I'll look into this option. All the best, Tom ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Differences html/pdf
Carsten Dominik writes: >> In the latex version they're not exported for some reasons... > > That is correct, we have not implemented keeping all line breaks in > LaTeX. I've searched around a bit, and to my big surprise, I cannot find a LaTeX package preserving line breaks. I understand such a function doesn't come along nicely with the general LaTeX philosophy, but it should be possible after all... Did anyone already tried to find such a package ? -- Bastien ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Problem with icalendar export: all items with active timestamps are being exported
Hey, that was quick! Thanks! ;) Carsten Dominik schrieb: > you don't want normal time stamps in your agenda as events??? Well, > this is an unusual idea. The reason I want this, is that I use SCHEDULED timestamps as my calendar items (i.e. the "hard landscape" for my day) and normal active timestamps as tickler items which can also be done on a different day. And I then export the iCal file to google calendar and view those entries on my phone, so I only want to see the hard landscape there, in order to decide appointments. I hear some people use exactly the opposite semantics for SCHEDULED and plain timestamps, but I find this more logical. -- Friedrich Delgado Friedrichs TauPan on Ircnet and Freenode ;) ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [babel] Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
Dan Davison writes: > Am I right in thinking that one issue remaining in this thread is that > we currently have no means of tangling the output of org-babel-latex? > Thus the 'begin_src latex' blocks that we can tangle have unevaluated > variables, and the resulting 'begin_latex' blocks have evaluated > variables but can't be tangled? (We could extend tangling to cover such > blocks, or perhaps preferably use ':results code' to generate 'begin_src > latex' blocks?) Sorry, I see. 'begin_latex' is inserted directly into latex export and omitted from other export targets. Still, it might sometimes be useful to use the tangling machinery in which case ':results code' is what is needed. Dan > > Dan > > > >> >>> >>> In response to the implicit question in your comment, perhaps there >>> isn't a need to embed LaTeX inside source blocks and the uses to which >>> I put them could be accomplished in org-mode without them. My >>> programming skills are pretty crude and I'm aware that I'm a long way >>> from understanding org-mode and its vast potential. With that caveat, >>> here is my $0.02. >>> >> >> I'm also very far from taking full advantage of Org-mode export >> >>> >>> First, practical reasons: >>> >>> 1) I'm comfortable writing LaTeX and am particular about the results; >>> it is hard for me to map the inverse transformation through the org- >>> mode LaTeX exporter to express in org the particular LaTeX result I'm >>> after. >>> >>> 2) Someone on the list (Carsten?) mentioned a couple of days ago that >>> it wasn't reasonable to expect the org LaTeX exporter to capture the >>> full complexity of LaTeX (I'm paraphrasing, but I think that was the >>> gist); I ran up against an example of this (or so I think) when trying >>> to configure export to beamer code, where beamer's use of columns >>> tripped me up. >>> >> >> I fully understand your point. I guess that given my personal paucity >> of latex knowledge and abilities the same need has never occurred to >> me. In my case the Org-mode exported generally knows more about latex >> than I do. >> >>> >>> Second, conceptual reasons: >>> >>> 1) I consider writing LaTeX to be programming (here I mean no >>> disrespect to real programmers) and appreciate being able to do >>> literate LaTeX programming; the LaTeX source blocks let me write my >>> beamer presentation a slide or two at a time, just as I want them, >>> along with an adjacent source block for my print document, just as i >>> want it, that covers the same conceptual space, while I use the >>> surrounding org entries to document why I am doing things a particular >>> way, etc. >>> >> >> I see, you are using the org-mode file "a level above" the direct >> export. Maybe another option here would be to tag headlines based on >> which export target they are included within, and then base your exports >> on the headline tags (using #+EXPORT_INCLUDE_TAGS:), although I agree >> this also seems like an appropriate place to use the tangle >> functionality. >> >>> >>> 2) I think this workflow, with an org-mode meta-document that >>> encapsulates the print document and presentation materials, along with >>> the SQL, R, and Python code used to create the datasets and analyze >>> them, takes org-babel a step closer to realizing its potential as a >>> tool for reproducible research. Here, I am thinking of an org >>> document that captures the ways in which a piece of research is one >>> logical path among many possibilities, implemented and expressed in >>> one particular way (or two, if you want to distinguish print from >>> presentation) among many possibilities. >>> >>> The LaTeX source blocks in org-babel give me an easy and natural way >>> to accomplish these things. In the short time I've used them, they've >>> yielded results that impress me. I'm confident they hold much more >>> potential than I've been able to tap. >>> >> >> I didn't mean to imply that because I didn't understand the need for >> direct inclusion of latex code there *wasn't* a need for direct >> inclusion of latex code :) Thanks for the explanation. >> >>> >>> It is a real pleasure leveraging your good work. >>> >> >> It is a pleasure to be able to participate in such a nice open-source >> community. -- Eric >> >>> >>> Tom >> >> >> ___ >> Emacs-orgmode mailing list >> Remember: use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Separate function for config listing from org-submit-bug-report
Carsten Dominik gmail.com> writes: > Hi Jeff, > > I don't know why you are being prompted for you IMAP password, > but regardless of this the email should not be send automatically. > So I think you can go through the process and then copy the text and > just not send the message! The email client is is wanderlust, and it must be trying to initialize a draft message on Google Mail when creating a send message buffer. You are correct, it did give the opportunity to cancel the message before sending. Thanks, > I cannot easily isolate this, because my code only produces the list > of interesting variables. Some code in reporter.el does the quoting > and insertion. Do you have any ideas how to get the following function to work? It is intended to insert the configuration at point: (defun org-dump-configuration () "Call reporter-dump-state (pkgname varlist pre-hooks post-hooks)" (interactive) (require 'reporter) (reporter-dump-state (org-version) (let (mylist) (mapatoms (lambda (v) (and (boundp v) (string-match "\\`\\(org-\\|outline-\\)" (symbol-name v)) (or (and (symbol-value v) (string-match "\\(-hook\\|-function\\)\\'" (symbol-name v))) (and (get v 'custom-type) (get v 'standard-value) (not (equal (symbol-value v) (eval (car (get v 'standard-value))) (push v mylist mylist) (insert "") (insert "") ) ) The error message seems to indicate that parameter 'varlist' is not populated correctly. Emacs : GNU Emacs 23.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0) of 2009-09-28 on thinkpad Package: Org-mode version 6.32trans (release_6.32b.8.g089b) current state: == State could not be dumped due to the following error: (wrong-type-argument integer-or-marker-p nil) You should still send this bug report. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[babel] Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
On Oct 28, 2009, at 6:10 AM, Dan Davison wrote: Dear thread participants, please note that we were breaking the rule of prepending the subject line with the string [babel]! One question inline below. "Eric Schulte" writes: "Thomas S. Dye" writes: On Oct 27, 2009, at 12:55 PM, Eric Schulte wrote: Although I still don't fully understand the need to embed latex *inside* of source-code blocks, perhaps the attached org-babel-latex.el file [1] will represent a simpler solution for embedding the results of source-code blocks in latex source-code blocks. It makes use of the :var org-babel header argument as shown in the attached example file [2]. To reproduce first load org-babel-latex.el and then evaluate the latex block (note the results are already in the file from my test evaluation). Hope this helps -- Eric Footnotes: [1] [2] Thanks for this, Eric. It looks neat. I was happy with all the little .tex files, but agree with Torsten that this path is potentially cleaner. Please let me know if you do find this useful or have any suggestions. If it proves useful I will add it to the org-mode repository. Am I right in thinking that one issue remaining in this thread is that we currently have no means of tangling the output of org-babel-latex? Thus the 'begin_src latex' blocks that we can tangle have unevaluated variables, and the resulting 'begin_latex' blocks have evaluated variables but can't be tangled? (We could extend tangling to cover such blocks, or perhaps preferably use ':results code' to generate 'begin_src latex' blocks?) Dan Hi Dan, I haven't found time to evaluate org-babel-latex, but, yes, the example provided with the code raised a concern that the 'begin_latex' blocks are divorced from the literate programming structure built up by the named 'begin_src latex' blocks. Ideally, I think, the 'begin_latex' blocks would replace <> references to their source 'begin_src latex' blocks, or would employ some other mechanism that doesn't break the literate programming structure I create. Tom ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode version 6.32; org-replace-disputed-keys t - breaks time shifts with S-up/down/left/right
Hi Kai,
On Oct 27, 2009, at 8:03 AM, Kai Tetzlaff wrote:
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report?
See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Some days ago i noticed that time shifting in CLOCK lines stopped
working.
I've now toggled some org config variables and found that this
happens when
org-replace-disputed-keys is set to t. This was not the case with
earlier
org-mode versions.
What exactly did work, and what does now no longer work?
- Carsten
Emacs : GNU Emacs 23.1.50.1 (i386-mingw-nt5.1.2600)
of 2009-10-14 on LENNART-69DE564 (patched)
Package: Org-mode version 6.32
current state:
==
(setq
org-empty-line-terminates-plain-lists t
org-log-done 'time
org-file-apps '((auto-mode . emacs) ("\\.x?html?\\'" . default) ("\
\.pdf\\'" . default)
(directory dired-other-frame file))
org-link-frame-setup '((vm . vm-visit-folder-other-frame) (gnus .
gnus-other-frame)
(file . find-file-other-frame))
org-special-ctrl-a/e 'reversed
org-agenda-clockreport-parameter-plist '(:link nil :maxlevel 4)
org-agenda-files '("~/.emacs.d/org/agenda")
org-clock-persist-query-resume nil
org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
org-publish-timestamp-directory "~/.emacs.d/tmp/org-timestamps/"
org-export-with-sub-superscripts '{}
org-hide-leading-stars t
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-clock-out-when-done nil
org-clock-history-length 25
org-odd-levels-only t
outline-minor-mode-prefix ""
org-special-ctrl-k t
org-publish-use-timestamps-flag nil
org-support-shift-select t
org-clock-in-resume t
org-export-preprocess-hook '(org-export-blocks-preprocess)
org-tags-exclude-from-inheritance '("cmm" "cmn" "cmr")
org-tab-first-hook '(org-hide-block-toggle-maybe)
outline-regexp "\\*+ "
org-src-mode-hook '(org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function 'yes-or-no-p
org-clock-persist t
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-M-RET-may-split-line '((default . t) (headline))
org-default-notes-file "~/.emacs.d/org/notes.org"
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-
drawers org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-publish-project-alist '(("NasTCs-org" :base-directory
"~/.emacs.d/org/agenda/STF160" :base-extension
"org" :exclude "\\(org\\|html\\|css\
\)" :include
("index.org"
"NasTestcases.org") :publishing-directory "~/NasTcOverview"
:publishing-function (kt:publish-html
org-publish-org-to-org) :plain-source t
:htmlized-source t :link-validation-
function kt:copy-and-validate-link :title
"NAS Testcase Overview" :style
"\"\n href=\"css/nas.css
\"\n type=\"text/css\">"
:table-of-contents t :section-numbers
nil :headline-levels 3 :sub-superscript
nil :todo-keywords t :drawers t :tags
not-in-toc :timestamps t :auto-index nil
:exclude-tags ("mdesc" "limpl"))
("NasTCs-other" :base-directory
"~/.emacs.d/org/agenda/STF160" :recursive t
:no-timestamps t :base-extension "css\\|
js" :include (".htaccess")
:publishing-directory "~/
NasTcOverview" :publishing-function
org-publish-attachment)
("NasTCs" :components ("NasTCs-other"
"NasTCs-org"))
("CMerge" :base-directory "~/.emacs.d/
org/agenda/STF160" :exclude ".*" :include
("NasTestcases.org") :publishing-
directory "~/NasTcMerge" :publishing-function
(kt:publish-html org-publish-org-to-
org) :link-validation-function
kt:copy-and-validate-link :title "Merge/
Align EPS-only/Combined NAS TCs"
:table-of-contents nil :section-numbers
nil :headline-levels 3
:sub-superscript nil :todo-keywords
t :drawers ("PROPERTIES") :tags nil
:timestamps nil :auto-index nil :select-
tags ("cmm" "cmn" "cmr") :exclude-tags
("limpl" "tci"))
)
org-mode-hook '(org-clock-load
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-show-
block-all append local] 5]
)
org-clock-out-remove-zero-time-clocks t
org-refile-targets '((org-agenda-file
Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
[cc'ing list who were accidentally omitted]
Torsten Wagner writes:
> Hi Dan,
>
>
>
> > 1. Hiding of the source code blocks for export
> > I like to export the results of the source code block to LaTeX only.
> However,
>
> Using ':exports results' specifies that only the results should appear
> in the exported document. This
>
> #+begin_src python :exports results
> 6 + 6
> #+end_src
>
>
Hi Torsten
> I tried this but the result is first the source code block followed by the
> result:
If it's not working, could you provide the exact example and tell us
your operating system, git version etc?
> Furthermore, I tried to create some LaTeX code as result of the code block
You need to use the ':results latex' header if you want the result to be
output as latex.
<...>
> In general I could try to use org-mode as much as possible. However, in that
> special case I like to merge three (or more) documents together.
> 1. The source code (e.g. python)
> 2. A laboratory journal (this would use org-mode magic)
> 3. An official report e.g. a manuscript to be submitted to a journal (this
> would be a LaTeX file)
>
> The idea is to be able to merge all this together to make sure data
> manipulation and calculus (source code) are as close as possible to the
> specific journal entry, which may supply additional important information and
> the final manuscript snippets which presents officially the particular result.
> A short example would be (without real headers)
>
> --8<-->8---
> * 23.10.09
> Measurement this morning was performed as usual but this time without warm up
> of device foo.
> Measurement file is saved under _link_.
> TODO: Don't forget to prepare for meeting tomorrow
>
> <>
> for foo import *
> a = load("data.csv")
> b = apply_filter(a,lp)
> plot(b)
> saveplot(bar.pdf)
> <>
OK, currently, the way to do that is something like
#+srcname: pyplot(file="bar.pdf")
#+begin_src python :results file
plot(outfile=file)
file
#+end_src
#+resname: pyplot
[[file:bar.pdf]]
Note that for a generalist language like python (which does not always
create output to file) you currently need to
1. specify that it outputs a file with ':results file'
2. explicitly send output to the file in your python code
3. explicitly return the filepath as a string at the end of the
block. it will get inserted as a link.
You have the option of not hard-wiring the filepath in the python code
by using a variable as I did there.
[We may want to change this so that (3) happens automatically when
':file filepath' or ':results file' is provided]
>
> First low pass filter was applied then a plot is generated
> This plot will be used in publication for journal foo
> DEADLINE: <2009-12-14 Mo>
> <>
> \begin{figure}
> \includegraphics{bar.pdf}
> \end{figure}
> <>
To avoid hard-wiring the filename into the latex block you could use the
org-babel-latex.el that Eric has posted.
> --8<-->8---
>
> Text outside should be org-mode text.
> Now I like to export with three scenarios
> 1. Only the LaTeX part (e.g. by using tangle) resulting in a pure native
> LaTeX-file ready for submission
See emails in the concurrent main thread on this topic.
> Above example will result in
>
> \begin{figure}
> \includegraphics{bar.pdf}
> \end{figure}
>
> 2. The LaTeX part and the org-mode parts whereas the LaTeX blocks should be
> somehow verbatim
> or in a some way marked inline. Above example should result in a LaTeX export
> like
'begin_src latex' blocks are exported as code blocks with appropriate
fontification under org-mode.
I hope this is getting clearer now :)
Dan
>
> \section{23.10.09}
> Measurement this morning was performed as usual but this time without warm up
> time.
> Measurement file is saved under \footnote[/home/foo/data.csv]{link}.
> First low pass filter was applied then a plot is generated
> This plot will be used in publication for journal foo
> \begin{minipage}
> \begin{figure}
> \includegraphics{bar.pdf}
> \end{figure}
> \end{minipage}
>
> 3. Export of all which will include the python blocks in a inline form as
> well.
>
> First of all I would be happy if I could avoid to have the source code blocks
> in the export file.
> I simply like to generate LaTeX-snipplets in python and export a LaTeX file
> finally.
>
> Thus,
>
> #+srcname: LaTeX
> #+begin_src python :session :exports results
> plot([1,2,3,4,5],[2,4,6,8,10])
> savefig(file,f-acecolor='w', edgecolor='w',format=None)
> param1 = 19.7
> perf = 77
> #+end_src
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Problem with icalendar export: all items with active timestamps are being exported
On Oct 28, 2009, at 5:35 PM, Friedrich Delgado Friedrichs wrote: Hey, that was quick! Thanks! ;) So it works? Carsten Dominik schrieb: you don't want normal time stamps in your agenda as events??? Well, this is an unusual idea. The reason I want this, is that I use SCHEDULED timestamps as my calendar items (i.e. the "hard landscape" for my day) and normal active timestamps as tickler items which can also be done on a different day. And I then export the iCal file to google calendar and view those entries on my phone, so I only want to see the hard landscape there, in order to decide appointments. I hear some people use exactly the opposite semantics for SCHEDULED and plain timestamps, but I find this more logical. Well, I can see both sides. - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [PATCH] Add min/max/mean age operators to column view.
Hi James, hi everyone,
this is a reasonably complex patch - could we get some volunteers
putting this to the test?
Thanks.
- Carsten
On Oct 26, 2009, at 1:04 AM, James TD Smith wrote:
I posted a patch to the list in July which added two new special
properties
intended for displaying the age of an entry in column view. After some
discussion with Bastien (who was maintainer at the time) we decided
I would
reimplement this functionality using column summary operators. It
took me a
while bit I've finally got a working version.
The patch is also available in the misc-new-features branch at
git://yog-sothoth.mohorovi.cc/org-mode.git.
---
lisp/ChangeLog | 38 +++---
lisp/org-colview.el | 198 +++
+---
lisp/org.el |4 +-
3 files changed, 156 insertions(+), 84 deletions(-)
diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 1b5848e..5677058 100755
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,27 @@
+2009-10-25 James TD Smith
+
+ * org-colview.el (org-format-time-period): Function to format
+ times in fractional days for display.
+ (org-columns-display-here): Add support for showing a calculated
+ value in place of the property.
+ (org-columns): Set `org-columns-time' to the current time so time
+ difference calculations will work.
+ (org-columns-time): Use to store the current time when column view
+ is displayed, so all time differences will use the same reference
+ point.
+ (org-columns-compile-map): There is now an extra position in each
+ entry specifying the function to use to calculate the displayed
+ value for the non-calculated properties in the column,
+ (org-columns-compute-all): Set `org-columns-time' to the current
+ time so time difference calculations will work.
+ (org-columns-compute): Handle column operators where the values
+ used are calculated from the underlying property.
+ (org-columns-number-to-string): Handle the 'age' column format
+ (org-columns-string-to-number): Correct the function name (was
+ org-column...). Add support for the 'age' column format.
+ (org-columns-compile-format): Support the additional parameter in
+ org-columns-compile-map.
+
2009-10-25 Carsten Dominik
* org-clock.el (org-clock-has-been-used): New variable.
@@ -1543,20 +1567,14 @@
* org-exp.el (org-export-format-source-code-or-example): Fix
bad line numbering when exporting examples in HTML.
-2009-07-12 James TD Smith
-
* org-colview.el (org-format-time-period): Formats a time in
fractional days as days, hours, mins, seconds.
(org-columns-display-here): Add special handling for SINCE and
SINCE_IA to format for display.
- * org.el (org-time-since): Add a function to get the time since an
- org timestamp.
- (org-entry-properties): Add two new special properties: SINCE and
- SINCE_IA. These give the time since any active or inactive
- timestamp in an entry.
- (org-special-properties): Add SINCE, SINCE_IA.
- (org-tags-sort-function): Add custom declaration for tags
+2009-07-12 James TD Smith
+
+ * org.el (org-tags-sort-function): Add custom declaration for tags
sorting function.
(org-set-tags): Sort tags if org-tags-sort-function is set
@@ -4423,7 +4441,7 @@
(org-agenda-change-all-lines, org-tags-sparse-tree)
(org-time-string-to-absolute, org-small-year-to-year)
(org-link-escape): Re-apply changes accidentially overwritten
- by last commit to Emacs.
+ by last commit to Emacs
2008-11-23 Carsten Dominik
diff --git a/lisp/org-colview.el b/lisp/org-colview.el
index 374d22a..87c1412 100644
--- a/lisp/org-colview.el
+++ b/lisp/org-colview.el
@@ -111,8 +111,8 @@ This is the compiled version of the format.")
(org-defkey org-columns-map [(shift meta left)] 'org-columns-delete)
(dotimes (i 10)
(org-defkey org-columns-map (number-to-string i)
- `(lambda () (interactive)
- (org-columns-next-allowed-value nil ,i
+ `(lambda () (interactive)
+(org-columns-next-allowed-value nil ,i
(easy-menu-define org-columns-menu org-columns-map "Org Column Menu"
'("Column"
@@ -165,7 +165,7 @@ This is the compiled version of the format.")
(face1 (list color 'org-agenda-column-dateline ref-face))
(pl (or (get-text-property (point-at-bol) 'prefix-length) 0))
(cphr (get-text-property (point-at-bol) 'org-complex-heading-
regexp))
-pom property ass width f string ov column val modval s2 title)
+pom property ass width f string ov column val modval s2 title calc)
;; Check if the entry is in another buffer.
(unless props
(if (eq major-mode 'org-agenda-mode)
@@ -189,19 +189,25 @@ This is the compiled version of the format.")
(nth 2 co
[Orgmode] Re: Differences html/pdf
Carsten Dominik gmail.com> writes: > > > On Oct 28, 2009, at 3:16 PM, andrea Crotti wrote: > > > This is about the TODO keywords, and they are stripped in both Mm I don't understand... How should I disable "todo" exporting then? How I wrote it doesn't work, but from the manual it should be correct... > > > and newline are kept only in html. > > > > > In the latex version they're not exported for some reasons... > > That is correct, we have not implemented keeping all line breaks in > LaTeX. > Too hard, unfortunately. I see.. But would not be enough to do a simple replace \n -> \newline from the org file to the latex source file? ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [babel] Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
"Thomas S. Dye" writes:
> On Oct 28, 2009, at 6:10 AM, Dan Davison wrote:
>> Am I right in thinking that one issue remaining in this thread is that
>> we currently have no means of tangling the output of org-babel-latex?
>> Thus the 'begin_src latex' blocks that we can tangle have unevaluated
>> variables, and the resulting 'begin_latex' blocks have evaluated
>> variables but can't be tangled? (We could extend tangling to cover
>> such
>> blocks, or perhaps preferably use ':results code' to generate
>> begin_src
>> latex' blocks?)
>>
>> Dan
>
> Hi Dan,
>
> I haven't found time to evaluate org-babel-latex, but, yes, the
> example provided with the code raised a concern that the 'begin_latex'
> blocks are divorced from the literate programming structure built up
> by the named 'begin_src latex' blocks. Ideally, I think, the
> begin_latex' blocks would replace <> references to their
> source 'begin_src latex' blocks, or would employ some other mechanism
> that doesn't break the literate programming structure I create.
>
I just started a new branch [1] in the org-mode/babel [2] repository
where we should be able to implement a solution without too much
trouble. If we expand the noweb syntax such that if a source-code block
name has parenthesis "()" appended to the end of it's name, then the
block will be evaluated during noweb reference expansion and it's
results will be placed in the source-code block. That structure should
even allow simple literal arguments to be passed to the referenced
block.
So for example what I'm proposing is that in the following case this
--8<---cut here---start->8---
#+srcname: noweb-example
#+begin_src python :var a=0
a+10
#+end_src
#+begin_src latex :tangle somewhere
\begin{itemize}
\item <>
\item <>
\item <>
\end{itemize}
#+end_src
--8<---cut here---end--->8---
would tangle to somewhere.tex as
--8<---cut here---start->8---
\begin{itemize}
\item a+10
\item 10
\item 18
\end{itemize}
--8<---cut here---end--->8---
Does that sound appropriate? -- Eric
Footnotes:
[1]
http://repo.or.cz/w/org-mode/babel.git?a=shortlog;h=refs/heads/noweb-evaluate
[2] http://repo.or.cz/w/org-mode/babel.git
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Separate function for config listing from org-submit-bug-report
On Oct 28, 2009, at 5:50 PM, Jeff Kowalczyk wrote: Carsten Dominik gmail.com> writes: Hi Jeff, I don't know why you are being prompted for you IMAP password, but regardless of this the email should not be send automatically. So I think you can go through the process and then copy the text and just not send the message! The email client is is wanderlust, and it must be trying to initialize a draft message on Google Mail when creating a send message buffer. You are correct, it did give the opportunity to cancel the message before sending. Thanks, I cannot easily isolate this, because my code only produces the list of interesting variables. Some code in reporter.el does the quoting and insertion. Do you have any ideas how to get the following function to work? It is intended to insert the configuration at point: I believe there is some environment like reporter-status-count or reporter-status-message that needs to be scoped in with let, maybe other variables too... - Carsten (defun org-dump-configuration () "Call reporter-dump-state (pkgname varlist pre-hooks post-hooks)" (interactive) (require 'reporter) (reporter-dump-state (org-version) (let (mylist) (mapatoms (lambda (v) (and (boundp v) (string-match "\\`\\(org-\\|outline-\\)" (symbol-name v)) (or (and (symbol-value v) (string-match "\\(-hook\\|-function\\)\\'" (symbol-name v))) (and (get v 'custom-type) (get v 'standard-value) (not (equal (symbol-value v) (eval (car (get v 'standard-value))) (push v mylist mylist) (insert "") (insert "") ) ) The error message seems to indicate that parameter 'varlist' is not populated correctly. Emacs : GNU Emacs 23.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0) of 2009-09-28 on thinkpad Package: Org-mode version 6.32trans (release_6.32b.8.g089b) current state: == State could not be dumped due to the following error: (wrong-type-argument integer-or-marker-p nil) You should still send this bug report. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Exporting blocks without removing indentation
It's probably too late to suggest this, but it might be that long options are more easy to remember for users than short options? Also, they might be easier to look up in the manual if you use a non-Emacs browser. On 2009-10-28, Carsten Dominik wrote: > Hi Dan, > > maybe the easiest way to implement this would be a -i (or whatever) > switch a the src block. > > Switches are being processed already, so it will be simple to add one, > I think. > > - Carsten > > On Oct 28, 2009, at 2:29 PM, Dan Davison wrote: > >> Fairly late in the export process, org-exp removes the common >> indentation from lines inside blocks (line 2288 of org-exp.el): >> >> (setq rtn (org-remove-indentation code)) >> >> However, what do we do if >> >> 1. A user has a block that she wishes to export with the indentation >> intact? >> >> 2. An org-exp-blocks plugin has a block that it wishes to export with >> the indentation intact? >> >> I propose that we make (1) and (2) possible. An example where (1) >> arises >> is if, when documenting a moderately complex program, different >> parts of >> a class or function are contained in separate blocks. >> >> Q1. Is that aim approved of? >> >> (2) is a bit trickier than (1). To solve (1), we could introduce a fix >> in org-exp.el like >> >> - (setq rtn (org-remove-indentation code)) >> + (setq rtn (if org-src-preserve-indentation code >> + (org-remove-indentation code))) >> >> However in solving (2) the plugin cannot assume that the variable >> org-src-preserve-indentation is in effect (in fact it very likely >> isn't). So we need to come up with a way in which the block resulting >> from an org-exp-blocks plugin can have its indentation survive through >> to the export product, even if org-src-preserve-indentation is >> globally >> nil. Two possibilities are >> >> 1. We adopt a convention whereby if all lines start with some >> character >> (say ,) then that character is removed (but the remaining >> indentation >> is left intact.) >> >> 2. We transplant the indentation-removing work from org-exp.el into >> org-exp-blocks.el, and arrange that it is only performed if the >> block >> is *not* handled by an org-exp-blocks plugin. >> >> Q2. Has this made sense? What solution do you suggest? >> >> Q3. Should we use org-src-preserve-indentation in this way to affect >> export? (It currently has effect when switching between the org buffer >> and the code edit buffer.) >> >> Dan >> >> >> ___ >> Emacs-orgmode mailing list >> Remember: use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode > > - Carsten > > > > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > -- Q: How many CDC "scientists" does it take to change a lightbulb? A: "You only think it's dark." [CDC has denied ME/"CFS" for 25 years] = Retrovirus: http://www.wpinstitute.org/xmrv/xmrv_qa.html ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Differences html/pdf
On Oct 28, 2009, at 6:26 AM, Bastien wrote: Carsten Dominik writes: In the latex version they're not exported for some reasons... That is correct, we have not implemented keeping all line breaks in LaTeX. I've searched around a bit, and to my big surprise, I cannot find a LaTeX package preserving line breaks. I understand such a function doesn't come along nicely with the general LaTeX philosophy, but it should be possible after all... Did anyone already tried to find such a package ? -- Bastien Aloha Bastien, Plain LaTeX has \linebreak and \nolinebreak, that might be appropriate. Tom ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [babel] Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
On Oct 28, 2009, at 7:15 AM, Eric Schulte wrote:
"Thomas S. Dye" writes:
On Oct 28, 2009, at 6:10 AM, Dan Davison wrote:
Am I right in thinking that one issue remaining in this thread is
that
we currently have no means of tangling the output of org-babel-
latex?
Thus the 'begin_src latex' blocks that we can tangle have
unevaluated
variables, and the resulting 'begin_latex' blocks have evaluated
variables but can't be tangled? (We could extend tangling to cover
such
blocks, or perhaps preferably use ':results code' to generate
begin_src
latex' blocks?)
Dan
Hi Dan,
I haven't found time to evaluate org-babel-latex, but, yes, the
example provided with the code raised a concern that the
'begin_latex'
blocks are divorced from the literate programming structure built up
by the named 'begin_src latex' blocks. Ideally, I think, the
begin_latex' blocks would replace <> references to their
source 'begin_src latex' blocks, or would employ some other mechanism
that doesn't break the literate programming structure I create.
I just started a new branch [1] in the org-mode/babel [2] repository
where we should be able to implement a solution without too much
trouble. If we expand the noweb syntax such that if a source-code
block
name has parenthesis "()" appended to the end of it's name, then the
block will be evaluated during noweb reference expansion and it's
results will be placed in the source-code block. That structure
should
even allow simple literal arguments to be passed to the referenced
block.
So for example what I'm proposing is that in the following case this
--8<---cut here---start->8---
#+srcname: noweb-example
#+begin_src python :var a=0
a+10
#+end_src
#+begin_src latex :tangle somewhere
\begin{itemize}
\item <>
\item <>
\item <>
\end{itemize}
#+end_src
--8<---cut here---end--->8---
would tangle to somewhere.tex as
--8<---cut here---start->8---
\begin{itemize}
\item a+10
\item 10
\item 18
\end{itemize}
--8<---cut here---end--->8---
Does that sound appropriate? -- Eric
Footnotes:
[1]
http://repo.or.cz/w/org-mode/babel.git?a=shortlog;h=refs/heads/noweb-evaluate
[2] http://repo.or.cz/w/org-mode/babel.git
Eric,
I think Torsten has a clearer idea than I do about what kinds of
programming structures might be appropriate here, but your suggestion
looks to me like an elegant replacement for the file based technique
I'm using to pass information into 'begin_src latex' blocks now.
Expanding the noweb syntax in the way you propose looks extremely
useful. I think it introduces an exciting range of possibilities into
the workflow I'm developing with org-babel. So, yes, your proposal
sounds appropriate to me.
Tom
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Differences html/pdf
andrea Crotti wrote: > Carsten Dominik gmail.com> writes: > > On Oct 28, 2009, at 3:16 PM, andrea Crotti wrote: > > ... > > > In the latex version they're not exported for some reasons... > > > > That is correct, we have not implemented keeping all line breaks in > > LaTeX. > > Too hard, unfortunately. > > I see.. > But would not be enough to do a simple replace > \n -> \newline from the org file to the latex source file? > No - it's much more complicated than that, partly because bare newlines in LaTeX are completely ignored (except that two newlines in a row signal end of paragraph - assuming of course that you are in paragraph mode...), partly because the constructs that try to emulate newline behavior (\\, \linebreak, \newline) are very context-dependent. For a flavor of some of the complications, see this thread: http://thread.gmane.org/gmane.emacs.orgmode/17333 particularly Bastien's summary of a reply that Sebastien Vauban got in the fr.comp.text.tex newsgroup. Even that, complicated as it is, is not complete. Nick ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [PATCH] Add min/max/mean age operators to column view.
Hi Carsten, On 2009-10-28 18:01:44(+0100), Carsten Dominik wrote: > this is a reasonably complex patch - could we get some volunteers > putting this to the test? If anyone wants to test this, please pull from my git repo; there's a couple of missing brackets in this patch. James -- |---| ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] agenda actions unexpectedly open files
Hi -- This is so odd. Most of the time, but not always, when I mark an item as DONE in the agenda, it pops open the file containing the item. I'm just now noticing that it's doing the same thing when I clock in. This obviously really messes with my workflow. This started someplace along my upgrade process, but I can't put my finger on when. I'm running Aquamacs Distribution 2.0preview3 (GNU Emacs 23.0.94.1) with org-mode 6.32, but this has been happening for a few weeks now. Any advice? -- Michael ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] How to write verbatim [0] ?
Hello Experts, Are there any way to write just a plain [0], instead of interpreting it as a footnote when publishing in to HTML? I've tried the ~[0]~, and ~[~0~]~, but not luck. Thanks! Xin ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Problem with icalendar export: all items with active timestamps are being exported
Carsten Dominik schrieb: > On Oct 28, 2009, at 5:35 PM, Friedrich Delgado Friedrichs wrote: > >Hey, that was quick! Thanks! ;) > So it works? Yes works nicely! > >I hear some people use exactly the opposite semantics for SCHEDULED > >and plain timestamps, but I find this more logical. > Well, I can see both sides. ---Zitatende--- My mobile calendar view is very lean now. -- Friedrich Delgado Friedrichs TauPan on Ircnet and Freenode ;) pgpncohkHEuMW.pgp Description: PGP signature ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] How to write verbatim [0] ?
Xin Shi wrote: > Hello Experts, > > Are there any way to write just a plain [0], instead of interpreting it as a > footnote when > publishing in to HTML? > > I've tried the ~[0]~, and ~[~0~]~, but not luck. > I don't know how to do it on an instance-by-instance basis, but on a per-file basis, there is #+OPTIONS: f:nil to turn off footnotes. HTH, Nick ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] How to write verbatim [0] ?
It works. Though it seems a pity to turn off the footnote mode in the whole file. I used the [ 0 ] for a temporary fix just now. Thanks! Xin On Wed, Oct 28, 2009 at 4:32 PM, Nick Dokos wrote: > Xin Shi wrote: > > > Hello Experts, > > > > Are there any way to write just a plain [0], instead of interpreting it > as a footnote when > > publishing in to HTML? > > > > I've tried the ~[0]~, and ~[~0~]~, but not luck. > > > > I don't know how to do it on an instance-by-instance basis, but > on a per-file basis, there is > > #+OPTIONS: f:nil > > to turn off footnotes. > > HTH, > Nick > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [babel] Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
"Thomas S. Dye" writes: [...] > Eric, > > I think Torsten has a clearer idea than I do about what kinds of > programming structures might be appropriate here, but your suggestion > looks to me like an elegant replacement for the file based technique > I'm using to pass information into 'begin_src latex' blocks now. > Expanding the noweb syntax in the way you propose looks extremely > useful. I think it introduces an exciting range of possibilities into > the workflow I'm developing with org-babel. So, yes, your proposal > sounds appropriate to me. > > Tom This has now been implemented. To try it out grab the most recent version of Org-mode. Changes include - the ability to insert the *results* of source-code blocks through the use of noweb references in which the source-name is followed by ()s, and - the addition of the org-babel-latex.el file which should make it easier to add latex to the languages known to org-babel To try this out please run org-babel-tangle on the attached org-mode file. noweb-eval.org Description: Binary data which should result in the attached .tex file somewhere.tex Description: TeX document Let me know if I should make any changes to this new setup. Thanks for the ideas. -- Eric ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Differences html/pdf
Bastien wrote:
> Carsten Dominik writes:
>
> >> In the latex version they're not exported for some reasons...
> >
> > That is correct, we have not implemented keeping all line breaks in
> > LaTeX.
>
> I've searched around a bit, and to my big surprise, I cannot find a
> LaTeX package preserving line breaks. I understand such a function
> doesn't come along nicely with the general LaTeX philosophy, but it
> should be possible after all...
>
> Did anyone already tried to find such a package ?
>
Not a package, but there is \obeylines (plain TeX) that will
preserve line breaks - e.g. Knuth[1] suggests that it be used for
typesetting poetry:
{\obeylines\smallskip
Roses are red,
\quad Violets are blue;
Rhymes can be typeset
\quad with boxes and glue.
\smallskip}
It apparently works by pretending that the newline is a \par token.
Nick
[1] Knuth, "The TeXbook", p. 94
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Toggle 'closed' in org-agenda-log-mode-items
Hi Nathan, I wanted to do the same thing. Here's a snippet of elisp that does the job -- it's a bit simpleminded but gets the job done: (defun org-toggle-agenda-show-closed-logs () ;; pseudo code -- ;if org-agenda-log-mode-items contains 'closed' then ;remove 'closed' from org-agenda-log-mode-items ;else ; add 'closed' to org-agenda-log-mode-items ;(refresh the agenda view) (interactive) (if (equal (car org-agenda-log-mode-items) 'closed) (setq org-agenda-log-mode-items '(clock)) (setq org-agenda-log-mode-items '(closed clock))) (org-agenda-redo) ) Cheers, Steve "Nathan Neff" wrote in message news:211769420907310652j5b378f4fi4c0be8d7910dd...@mail.gmail.com... On Thu, Jul 30, 2009 at 5:51 PM, Bernt Hansen wrote: > Nathan Neff writes: > >> I know that I can set this variable or define a custom agenda view >> if I only want to see clocked items in the agenda: >> >> (setq org-agenda-log-mode-items (quote (clock))) >> >> But, I like the way that the 'l' and 'R' keys work in the agenda, >> where they show/hide >> the log and the clock report. >> >> Is there a way to define something similar for the showing/hiding of >> Closed log items in the agenda? >> >> I'm not very good at lisp, so something like this pseudo-code: >> >> (defun org-toggle-agenda-show-closed-logs () >> ;; pseudo code -- >> if org-agenda-log-mode-items contains 'closed' then >> remove 'closed' from org-agenda-log-mode-items >> else >> add 'closed' to org-agenda-log-mode-items >> (refresh the agenda view) >> ) >> >> (define-key org-mode-map (kbd "") >> 'org-toggle-agenda-show-closed-logs) > > l in the agenda shows clock times only with your setup. > > C-u l shows task state changes too. Is that what you are looking for or > do you only want the closed states? > I would like to be able to press some key and toggle between these two things: 1) Show Clocked tasks only 2) Show Clocked tasks and Closed items Thanks for any ideas, --Nate ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [Announce:] org-git-link
Dear Reimar, why I feel like I have Birthday today ;) Thanks will try it as soon as possible Greetings Torsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode version 6.32; org-replace-disputed-keys t - breaks time shifts with S-up/down/left/right
At Wed, 28 Oct 2009 17:55:44 +0100,
Hi Carsten,
> >
> > Some days ago i noticed that time shifting in CLOCK lines stopped
> > working.
> > I've now toggled some org config variables and found that this
> > happens when
> > org-replace-disputed-keys is set to t. This was not the case with
> > earlier
> > org-mode versions.
>
> What exactly did work, and what does now no longer work?
>
> - Carsten
Since about a week/10d ago i could use S-up/down/left/right to manipulate
dates and timestamps in CLOCK: lines independent of the value of
org-replace-disputed-keys. Now with org-replace-disputed-keys set to t, the
shifted arrow key just start/extend the region (with
pc-selection-mode/shift-select-mode turned on). It's not a big deal to me. I
just noticed a change in how things work.
/Kai
>
>
> >
> > Emacs : GNU Emacs 23.1.50.1 (i386-mingw-nt5.1.2600)
> > of 2009-10-14 on LENNART-69DE564 (patched)
> > Package: Org-mode version 6.32
> >
> > current state:
> > ==
> > (setq
> > org-empty-line-terminates-plain-lists t
> > org-log-done 'time
> > org-file-apps '((auto-mode . emacs) ("\\.x?html?\\'" . default) ("\
> > \.pdf\\'" . default)
> > (directory dired-other-frame file))
> > org-link-frame-setup '((vm . vm-visit-folder-other-frame) (gnus .
> > gnus-other-frame)
> >(file . find-file-other-frame))
> > org-special-ctrl-a/e 'reversed
> > org-agenda-clockreport-parameter-plist '(:link nil :maxlevel 4)
> > org-agenda-files '("~/.emacs.d/org/agenda")
> > org-clock-persist-query-resume nil
> > org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
> > org-publish-timestamp-directory "~/.emacs.d/tmp/org-timestamps/"
> > org-export-with-sub-superscripts '{}
> > org-hide-leading-stars t
> > org-after-todo-state-change-hook '(org-clock-out-if-current)
> > org-clock-out-when-done nil
> > org-clock-history-length 25
> > org-odd-levels-only t
> > outline-minor-mode-prefix ""
> > org-special-ctrl-k t
> > org-publish-use-timestamps-flag nil
> > org-support-shift-select t
> > org-clock-in-resume t
> > org-export-preprocess-hook '(org-export-blocks-preprocess)
> > org-tags-exclude-from-inheritance '("cmm" "cmn" "cmr")
> > org-tab-first-hook '(org-hide-block-toggle-maybe)
> > outline-regexp "\\*+ "
> > org-src-mode-hook '(org-src-mode-configure-edit-buffer)
> > org-confirm-shell-link-function 'yes-or-no-p
> > org-clock-persist t
> > org-agenda-before-write-hook '(org-agenda-add-entry-text)
> > org-M-RET-may-split-line '((default . t) (headline))
> > org-default-notes-file "~/.emacs.d/org/notes.org"
> > org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-
> > drawers org-cycle-show-empty-lines
> > org-optimize-window-after-visibility-change)
> > org-publish-project-alist '(("NasTCs-org" :base-directory
> > "~/.emacs.d/org/agenda/STF160" :base-extension
> > "org" :exclude "\\(org\\|html\\|css\
> > \)" :include
> > ("index.org"
> > "NasTestcases.org") :publishing-directory "~/NasTcOverview"
> > :publishing-function (kt:publish-html
> > org-publish-org-to-org) :plain-source t
> > :htmlized-source t :link-validation-
> > function kt:copy-and-validate-link :title
> > "NAS Testcase Overview" :style
> > " > \"\n href=\"css/nas.css
> > \"\n type=\"text/css\">"
> > :table-of-contents t :section-numbers
> > nil :headline-levels 3 :sub-superscript
> > nil :todo-keywords t :drawers t :tags
> > not-in-toc :timestamps t :auto-index nil
> > :exclude-tags ("mdesc" "limpl"))
> > ("NasTCs-other" :base-directory
> > "~/.emacs.d/org/agenda/STF160" :recursive t
> > :no-timestamps t :base-extension "css\\|
> > js" :include (".htaccess")
> > :publishing-directory "~/
> > NasTcOverview" :publishing-function
> > org-publish-attachment)
> > ("NasTCs" :components ("NasTCs-other"
> > "NasTCs-org"))
> > ("CMerge" :base-directory "~/.emacs.d/
> > org/agenda/STF160" :exclude ".*" :include
> > ("NasTestcases.org") :publishing-
> > directory "~/NasTcMerge" :publishing-function
> > (kt:publish-html org-publish-org-to-
> > org) :link-validation-function
> > kt:copy-and-validate-link :title "Merge/
> > Align EPS-only/Combined NAS TCs"
> > :table-of-contents nil :section-numbers
> > nil :headline-levels 3
> > :sub-superscript nil :todo-keywords
> > t :drawers ("PROPERTIES") :tags nil
> > :tim
Re: [babel][Orgmode] org-babel: Meta-LaTeX-Python-Environment
Hi Dan,
thanks for helping me to realize my idea.
Actually, I do not know whether it is not working or it is not working as I
expect:
I used the following simple example:
--8<--cut here--start--->8---
* Simple Test of org-babel
#+srcname: test()
#+begin_src python :results latex
a = 1
b = 2
c = a+b
"This is a Test: if a =" + str(a) + " and b = " + str(b) + " then a + b = "
+ str(c) + " right ?!"
#+end_src
#+resname: test
#+BEGIN_LaTeX
This is a Test: if a =1 and b = 2 then a + b = 3 right ?!
#+END_LaTeX
--8<--cut here--end--->8---
As you can see, the result is wrapped now in LaTeX source code blocks.
However, if I export the file by
M-x org-export l
the resulting LaTeX file still contains the source code itself (the part in the
verbatim environment.
What I was looking for was something _without_ the source code just the
result.
Getting export-result (trimmed to relevant part):
...
\section{Simple Test of org-babel}
\label{sec-1}
\begin{verbatim}
a = 1
b = 2
c = a+b
"This is a Test: if a =" + str(a) + " and b = " + str(b) + " then a + b = " +
str(c) + " right ?!"
\end{verbatim}
This is a Test: if a =1 and b = 2 then a + b = 3 right ?!
...
Wished export-result (trimmed to relevant part):
...
\usepackage{color}
\definecolor{gray}{gray}{0.95}
...
\section{Simple Test of org-babel}
\label{sec-1}
\colorbox{gray}{
This is a Test: if a =1 and b = 2 then a + b = 3 right ?!
}
...
As you can see, I like to indicate the source block results resp. the LaTeX
source code blocks in a way which indicate clearly that they belong to the
"official" output. E.g. by adding a slight gray background.
As mentioned before, I like to have mainly three ways of export
1. Export everything
2. Export everything except the source codes itself
3. Export a particular LaTeX source code session (e.g. by using the tangle
function)
Nevertheless, I will try the other very good ideas in this thread. Maybe this
works for me already.
Best regards and thanks again
Torsten
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [babel] Re: [Orgmode] org-babel: Meta-LaTeX-Python-Environment
On Oct 28, 2009, at 12:19 PM, Eric Schulte wrote: "Thomas S. Dye" writes: [...] Eric, I think Torsten has a clearer idea than I do about what kinds of programming structures might be appropriate here, but your suggestion looks to me like an elegant replacement for the file based technique I'm using to pass information into 'begin_src latex' blocks now. Expanding the noweb syntax in the way you propose looks extremely useful. I think it introduces an exciting range of possibilities into the workflow I'm developing with org-babel. So, yes, your proposal sounds appropriate to me. Tom This has now been implemented. To try it out grab the most recent version of Org-mode. Changes include - the ability to insert the *results* of source-code blocks through the use of noweb references in which the source-name is followed by ()s, and - the addition of the org-babel-latex.el file which should make it easier to add latex to the languages known to org-babel To try this out please run org-babel-tangle on the attached org-mode file. which should result in the attached .tex file Let me know if I should make any changes to this new setup. Thanks for the ideas. -- Eric Eric, Yes, the expanded noweb syntax works here as advertised. Wonderful. I look forward to making use of it and will take you up on your offer to make changes as new possibilities make themselves known. All the best, Tom Thomas S. Dye, Ph.D. T. S. Dye & Colleagues, Archaeologists, Inc. Phone: (808) 529-0866 Fax: (808) 529-0884 http://www.tsdye.com ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
