Re: [O] Index of cases
Alan L Tyree alanty...@gmail.com writes: ... I am now senior enough to insist that the editor edit my files directly. That single sentence really answers the question pretty effectively! The whole explanation does make perfect sense, though. I admit that the entire structure of the work-flow is not something I really understand - it seems to have developed over time in response to changing situations, and therefore has elements that one might not choose if one were starting from scratch. But (just throwing an additional idea out there) - the possibility of having a considerable apparatus for yourself in Org-mode, and your final step before sending to the editor being export to plain text. (so that your editor has bare plain text with no markup of any kind.) -- David
Re: [O] Edit current tree-node?
On 2013-09-09 02:39, Suvayu Ali wrote: On Sun, Sep 08, 2013 at 07:58:33PM +0200, Fredrik wrote: My cursor is on SubTree2 and I would like to open that part in a new buffer to brainstorm around it and then put the changes back in to the original file. C-x n s, `org-narrow-to-subtree'. Perfect! Thank you!
Re: [O] Index of cases
On 09/09/13 16:58, David Rogers wrote: Alan L Tyree alanty...@gmail.com writes: ... I am now senior enough to insist that the editor edit my files directly. That single sentence really answers the question pretty effectively! The whole explanation does make perfect sense, though. I admit that the entire structure of the work-flow is not something I really understand - it seems to have developed over time in response to changing situations, and therefore has elements that one might not choose if one were starting from scratch. Sigh! Isn't that always the case? :-(. But (just throwing an additional idea out there) - the possibility of having a considerable apparatus for yourself in Org-mode, and your final step before sending to the editor being export to plain text. (so that your editor has bare plain text with no markup of any kind.) My real problem is that I don't know how to generate the multiple indexes that I need if I use org mode. Everything else is easy. Any potential solution that I see involves adding lots more markup, but if I do that I might as well stick with LaTeX. At least a lot of simple editors (the software) are LaTeX aware, so my editor (the human being) should be able to handle it. Thanks again for your thoughts. Cheers, Alan -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:typh...@iptel.org
[O] BUG: Decimal numbers using commata not recognised
Given the table below cash 20,000 short term debt 89,000 cash 20,000 short term debt 89,000 cash 20,000 short term debt 89,000 cash 20,000 short term debt 89,000 cash 20,000 short term debt 89,000 cash 20,000 short term debt 89,000 M-x org-table-convert-region - | cash 20 | 000 short term debt 89 | 000 | | cash 20 | 000 short term debt 89 | 000 | | cash 20 | 000 short term debt 89 | 000 | | cash 20 | 000 short term debt 89 | 000 | | cash 20 | 000 short term debt 89 | 000 | | cash 20 | 000 short term debt 89 | 000 | Decimal numbers using commata not recognised by org-table-convert-region Thanks, Andreas
Re: [O] Outline cycling does not preserve point's position
Hi Carsten, Carsten Dominik wrote: On 7.9.2013, at 21:28, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: On 7.9.2013, at 14:11, Sebastien Vauban sva-n...@mygooglest.com wrote: Since a little while, I've observed that point's position is not anymore preserved when cycling buffer's view with S-TAB. That's very annoying when you want to just look at your tree structure, but don't expect to land somewhere else by doing so. At the very least, we could agree that point should always be part of the entry we were on; so never go up to the *parent* entry. I have fixed this now, point does now completely stay put during global cycling. Simply perfect! And the fact that the blinking cursor stays at the end of the closest headling displayed (outline level 1, then outline level N) just shows where your point is in the real contents. Great... See http://screencast.com/t/dEbKjNlk Thanks! Best regards, Seb -- Sebastien Vauban
Re: [O] Index of cases
Hi Alan, On Mon, Sep 09, 2013 at 05:14:17PM +1000, Alan L Tyree wrote: My real problem is that I don't know how to generate the multiple indexes that I need if I use org mode. Everything else is easy. Any potential solution that I see involves adding lots more markup, but if I do that I might as well stick with LaTeX. This is indeed a subtle problem. I am having a hard time thinking of an Org way of doing this without special markup. It would have to be auto-generated in someway. So I have a somewhat non-technical suggestion. How about you give the LaTeX macros you use human readable aliases. The editors then might find it easier to edit LaTeX source directly. Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] Outline cycling does not preserve point's position
Hi Carsten, Carsten Dominik wrote: - not possible anymore to use C-a or C-e in code blocks to select regions; not reported yet, though I reported similar problems with C-arrows (apparently due to a change which is now officially part of 8.1). IMO, that renders editing of code block in the original buffer much more annoying. Also this is now fixed. Regarding C-a/e, same remark: perfect! Thanks a lot for these quick fixes... Regarding C-down, is it possible to get it back working for selecting parts of code? In the video captured at http://screencast.com/t/1WjWohviyjE, we see that we can move from an heading to the next with C-down (which is a nice extra addition to the already existing speed commands), but also select subelements in a region (paragraphs or list items). Though, in the code block, C-down still looses the region... Best regards, Seb -- Sebastien Vauban
Re: [O] Outline cycling does not preserve point's position
On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote: Hi Carsten, Carsten Dominik wrote: - not possible anymore to use C-a or C-e in code blocks to select regions; not reported yet, though I reported similar problems with C-arrows (apparently due to a change which is now officially part of 8.1). IMO, that renders editing of code block in the original buffer much more annoying. Also this is now fixed. Regarding C-a/e, same remark: perfect! Thanks a lot for these quick fixes... Regarding C-down, is it possible to get it back working for selecting parts of code? In the video captured at http://screencast.com/t/1WjWohviyjE, we see that we can move from an heading to the next with C-down (which is a nice extra addition to the already existing speed commands), but also select subelements in a region (paragraphs or list items). Though, in the code block, C-down still looses the region... Hi Sebastien, is this about loosing the active mark, or about the effect that C-down now jumps elements, not paragraphs? - Carsten Best regards, Seb -- Sebastien Vauban signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] BUG: Decimal numbers using commata not recognised
Hi Andreas, Andreas Röhler andreas.roeh...@easy-emacs.de writes: Decimal numbers using commata not recognised by org-table-convert-region Did you try to customize `org-table-number-regexp'? -- Bastien
Re: [O] Outline cycling does not preserve point's position
Hi Carsten, Carsten Dominik wrote: On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: - not possible anymore to use C-a or C-e in code blocks to select regions; not reported yet, though I reported similar problems with C-arrows (apparently due to a change which is now officially part of 8.1). IMO, that renders editing of code block in the original buffer much more annoying. Regarding C-down, is it possible to get it back working for selecting parts of code? In the video captured at http://screencast.com/t/1WjWohviyjE, we see that we can move from an heading to the next with C-down (which is a nice extra addition to the already existing speed commands), but also select subelements in a region (paragraphs or list items). Though, in the code block, C-down still looses the region... is this about loosing the active mark, or about the effect that C-down now jumps elements, not paragraphs? In fact, both... If we wanna still allow nice editing of code blocks, without forcing the users to use the indirect buffer, one must be able to quickly select, let's say a defvar, and copy it somewhere else; like we would do in the programming mode buffer (and like we did in the Org buffer, up to the change with C-down). Best regards, Seb -- Sebastien Vauban
Re: [O] Outline cycling does not preserve point's position
On 9.9.2013, at 10:23, Sebastien Vauban sva-n...@mygooglest.com wrote: Hi Carsten, Carsten Dominik wrote: On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: - not possible anymore to use C-a or C-e in code blocks to select regions; not reported yet, though I reported similar problems with C-arrows (apparently due to a change which is now officially part of 8.1). IMO, that renders editing of code block in the original buffer much more annoying. Regarding C-down, is it possible to get it back working for selecting parts of code? In the video captured at http://screencast.com/t/1WjWohviyjE, we see that we can move from an heading to the next with C-down (which is a nice extra addition to the already existing speed commands), but also select subelements in a region (paragraphs or list items). Though, in the code block, C-down still looses the region... is this about loosing the active mark, or about the effect that C-down now jumps elements, not paragraphs? In fact, both... If we wanna still allow nice editing of code blocks, without forcing the users to use the indirect buffer, one must be able to quickly select, let's say a defvar, and copy it somewhere else; like we would do in the programming mode buffer (and like we did in the Org buffer, up to the change with C-down). So maybe you just want to bing C-down to forward-paragraph again? - Carsten Best regards, Seb -- Sebastien Vauban signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] Outline cycling does not preserve point's position
Hi Carsten, Carsten Dominik wrote: On 9.9.2013, at 10:23, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: - not possible anymore to use C-a or C-e in code blocks to select regions; not reported yet, though I reported similar problems with C-arrows (apparently due to a change which is now officially part of 8.1). IMO, that renders editing of code block in the original buffer much more annoying. Regarding C-down, is it possible to get it back working for selecting parts of code? In the video captured at http://screencast.com/t/1WjWohviyjE, we see that we can move from an heading to the next with C-down (which is a nice extra addition to the already existing speed commands), but also select subelements in a region (paragraphs or list items). Though, in the code block, C-down still looses the region... is this about loosing the active mark, or about the effect that C-down now jumps elements, not paragraphs? In fact, both... If we wanna still allow nice editing of code blocks, without forcing the users to use the indirect buffer, one must be able to quickly select, let's say a defvar, and copy it somewhere else; like we would do in the programming mode buffer (and like we did in the Org buffer, up to the change with C-down). So maybe you just want to bing C-down to forward-paragraph again? This is a possibility, yes, but it completely defeats the nice `C-down' add-on (when outside of code block), and I guess I won't be the only one with that problem. Of course, the nicest would be to have both: the current `C-down' for text, and the programmatic behavior when _in code blocks_. Maybe, that's not possible, though... Best regards, Seb -- Sebastien Vauban
Re: [O] Outline cycling does not preserve point's position
Hi Sébastien, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Of course, the nicest would be to have both: the current `C-down' for text, and the programmatic behavior when _in code blocks_. Maybe, that's not possible, though... We could have org-ctrldown and friends the same way we have org-shift* commands. org-ctrldown would use `org-forward-element' when on some Org element, and `forward-paragraph' elsewhere. I acknowledge binding C-down to `org-forward-element' instead of `forward-paragraph' is a bit disruptive, and maybe not ideal in all situations. -- Bastien
Re: [O] Outline cycling does not preserve point's position
On 9.9.2013, at 10:33, Sebastien Vauban sva-n...@mygooglest.com wrote: Hi Carsten, Carsten Dominik wrote: On 9.9.2013, at 10:23, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: On 9.9.2013, at 10:11, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: - not possible anymore to use C-a or C-e in code blocks to select regions; not reported yet, though I reported similar problems with C-arrows (apparently due to a change which is now officially part of 8.1). IMO, that renders editing of code block in the original buffer much more annoying. Regarding C-down, is it possible to get it back working for selecting parts of code? In the video captured at http://screencast.com/t/1WjWohviyjE, we see that we can move from an heading to the next with C-down (which is a nice extra addition to the already existing speed commands), but also select subelements in a region (paragraphs or list items). Though, in the code block, C-down still looses the region... is this about loosing the active mark, or about the effect that C-down now jumps elements, not paragraphs? In fact, both... If we wanna still allow nice editing of code blocks, without forcing the users to use the indirect buffer, one must be able to quickly select, let's say a defvar, and copy it somewhere else; like we would do in the programming mode buffer (and like we did in the Org buffer, up to the change with C-down). So maybe you just want to bing C-down to forward-paragraph again? This is a possibility, yes, but it completely defeats the nice `C-down' add-on (when outside of code block), and I guess I won't be the only one with that problem. Of course, the nicest would be to have both: the current `C-down' for text, and the programmatic behavior when _in code blocks_. Maybe, that's not possible, though... This might be difficult, but not impossible. I think this might be a question for Nicolas to answer? - Carsten Best regards, Seb -- Sebastien Vauban signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] Outline cycling does not preserve point's position
Hi Eric, Eric Schulte wrote: not possible anymore to cut a code snippet in two parts with C-c C-v C-d (demarcate block); already reported (without bisect), no answer; This works for me, could you report a minimal recipe for reproduction, and maybe a git bisect commit? This does work again for me in the current Org version (Org-mode version 8.1.1, release_8.1.1-7-gaecdf5). Case closed! Thanks. Best regards, Seb -- Sebastien Vauban
Re: [O] Outline cycling does not preserve point's position
On 9.9.2013, at 10:38, Bastien b...@gnu.org wrote: Hi Sébastien, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Of course, the nicest would be to have both: the current `C-down' for text, and the programmatic behavior when _in code blocks_. Maybe, that's not possible, though... We could have org-ctrldown and friends the same way we have org-shift* commands. org-ctrldown would use `org-forward-element' when on some Org element, and `forward-paragraph' elsewhere. I acknowledge binding C-down to `org-forward-element' instead of `forward-paragraph' is a bit disruptive, and maybe not ideal in all situations. Yes, it produces unexpected results. - Carsten -- Bastien signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] Index of cases
Alan L Tyree alanty...@gmail.com writes: My real problem is that I don't know how to generate the multiple indexes that I need if I use org mode. Everything else is easy. Any potential solution that I see involves adding lots more markup, but if I do that I might as well stick with LaTeX. I'm not sure that needs to be the case. I don't use org-mode for LaTeX documents, but a bit of boiler-plate to generate the indexes shouldn't be too tricky. A good starting point is the manual for biblatex oscola package - which shows you to get your case, statute etc. tables with relatively little effort. http://mirror.ox.ac.uk/sites/ctan.org/macros/latex/contrib/biblatex-contrib/oscola/oscola.pdf
Re: [O] [PATCH] Add Microsoft Outlook Support to org-mac-link
I don't and I do need to check with my current employer before I could sign
them (*I* don't have a problem with it, but I'm just not sure of the
policies).
On Sun, Sep 8, 2013 at 1:50 AM, Carsten Dominik
carsten.domi...@gmail.comwrote:
Hi Mike,
we don't need papers for contrib stuff - but let
me ask anyway: Do you have signed FSF papers?
Thanks
- Carsten
On 7.9.2013, at 22:29, Mike McLean mike.mcl...@pobox.com wrote:
* contrib/lisp/org-mac-link.el: Add “o”utlook to capture descriptors
along with
functions to capture links from Microsoft Outlook for Mac.
The functions here replicate those that capture from Mail.app.
---
contrib/lisp/org-mac-link.el | 140
+++
1 file changed, 140 insertions(+)
diff --git a/contrib/lisp/org-mac-link.el b/contrib/lisp/org-mac-link.el
index 59b88d2..2ff6711 100644
--- a/contrib/lisp/org-mac-link.el
+++ b/contrib/lisp/org-mac-link.el
@@ -13,6 +13,11 @@
;; Version: 1.1
;; Keywords: org, mac, hyperlink
;;
+;; Version: 1.2
+;; Keywords: outlook
+;; Author: Mike McLean mike.mcl...@pobox.com
+;; Add support for Microsoft Outlook for Mac as Org mode links
+;;
;; This file is not part of GNU Emacs.
;;
;; This program is free software; you can redistribute it and/or modify
@@ -51,6 +56,7 @@
;; Google Chrome.app - Grab the url of the frontmost tab in the
frontmost window
;; Together.app - Grab links to the selected items in the library list
;; Skim.app - Grab a link to the selected page in the topmost pdf
document
+;; Microsoft Outlook.app - Grab a link to the selected message in the
message list
;;
;;
;; Installation:
@@ -97,6 +103,12 @@ applications and inserting them in org documents
:group 'org-mac-link
:type 'boolean)
+(defcustom org-mac-grab-Outlook-app-p t
+ Enable menu option [o]utlook to grab links from Microsoft
Outlook.app
+ :tag Grab Microsoft Outlook.app links
+ :group 'org-mac-link
+ :type 'boolean)
+
(defcustom org-mac-grab-Addressbook-app-p t
Enable menu option [a]ddressbook to grab links from AddressBook.app
:tag Grab AddressBook.app links
@@ -179,6 +191,7 @@ applications and inserting them in org documents
(interactive)
(let* ((descriptors `((F inder org-mac-finder-insert-selected
,org-mac-grab-Finder-app-p)
(m ail org-mac-message-insert-selected
,org-mac-grab-Mail-app-p)
+(o utlook
org-mac-outlook-message-insert-selected ,org-mac-grab-Outlook-app-p)
(a ddressbook
org-mac-addressbook-insert-selected ,org-mac-grab-Addressbook-app-p)
(s afari org-mac-safari-insert-frontmost-url
,org-mac-grab-Safari-app-p)
(f irefox
org-mac-firefox-insert-frontmost-url ,org-mac-grab-Firefox-app-p)
@@ -574,6 +587,133 @@ applications and inserting them in org documents
;;
;;
+;; Handle links from Microsoft Outlook.app
+;;
+
+(org-add-link-type mac-outlook 'org-mac-outlook-message-open)
+
+(defun org-mac-outlook-message-open (msgid)
+ Open a message in outlook
+ (let* ((record-id-string (format mdfind
com_microsoft_outlook_recordID==%s msgid))
+ (found-message (replace-regexp-in-string \n$
+ (shell-command-to-string record-id-string
+(if (string= found-message )
+ (message org-mac-link: error could not find Outlook message %s
(substring-no-properties msgid))
+ (shell-command (format open \`mdfind
com_microsoft_outlook_recordID==%s`\ msgid)
+
+(defun org-as-get-selected-outlook-mail ()
+ AppleScript to create links to selected messages in Microsoft
Outlook.app.
+ (do-applescript
+ (concat
+tell application \Microsoft Outlook\\n
+set msgCount to count current messages\n
+if (msgCount 1) then\n
+return\n
+end if\n
+set theLinkList to {}\n
+set theSelection to (get current messages)\n
+repeat with theMessage in theSelection\n
+set theID to id of theMessage as string\n
+set theURL to \mac-outlook:\ theID\n
+set theSubject to subject of theMessage\n
+set theLink to theURL \::split::\ theSubject \\n\\n
+copy theLink to end of theLinkList\n
+end repeat\n
+return theLinkList as string\n
+end tell)))
+
+(defun org-sh-get-flagged-outlook-mail ()
+ Shell commands to create links to flagged messages in Microsoft
Outlook.app.
+ (mapconcat
+ (lambda (x)
+ (concat
+ mac-outlook:
+ (mapconcat
+ (lambda (y) y)
+ (split-string
+ (shell-command-to-string
+ (format mdls -raw -name com_microsoft_outlook_recordID -name
kMDItemDisplayName \%s\ x))
+ \000)
+ ::split::)
+ \n))
+ (with-temp-buffer
+ (let ((coding-system-for-read (or file-name-coding-system 'utf-8))
+(coding-system-for-write 'utf-8))
+
Re: [O] Outline cycling does not preserve point's position
Hello, Carsten Dominik carsten.domi...@gmail.com writes: On 9.9.2013, at 10:38, Bastien b...@gnu.org wrote: We could have org-ctrldown and friends the same way we have org-shift* commands. org-ctrldown would use `org-forward-element' when on some Org element, and `forward-paragraph' elsewhere. elsewhere doesn't make sense here since point is _always_ on an element (except on the first blank lines in a buffer). I acknowledge binding C-down to `org-forward-element' instead of `forward-paragraph' is a bit disruptive, and maybe not ideal in all situations. Yes, it produces unexpected results. I find it pretty predictable. May you elaborate on that? Regards, -- Nicolas Goaziou
Re: [O] Outline cycling does not preserve point's position
Hello, Carsten Dominik carsten.domi...@gmail.com writes: This might be difficult, but not impossible. I think this might be a question for Nicolas to answer? It boils down to something like: (if (eq (org-element-type (org-element-at-point)) 'src-block) ;; Do forward-paragraph according to language. ... (org-forward-element)) Though, I suggest to introduce a variable similar to `org-src-tab-acts-natively', or group both features in the same variable like `org-act-natively-on-src-block'. Regards, -- Nicolas Goaziou
Re: [O] Outline cycling does not preserve point's position
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: We could have org-ctrldown and friends the same way we have org-shift* commands. org-ctrldown would use `org-forward-element' when on some Org element, and `forward-paragraph' elsewhere. elsewhere doesn't make sense here since point is _always_ on an element (except on the first blank lines in a buffer). Right. But you got the idea: use `org-forward-element' when moving within structural elements of various kinds make sense and use `forward-paragraph' otherwise. I acknowledge binding C-down to `org-forward-element' instead of `forward-paragraph' is a bit disruptive, and maybe not ideal in all situations. Yes, it produces unexpected results. I find it pretty predictable. May you elaborate on that? It is predictable, but sometimes counter-intuitive: for example, when on the first headline, C-up will throw an error instead of moving to the top of the buffer. Also, it is predictable but not reversible: hitting C-down three times then C-up three times will not always go back to the point where the user was at the beginning. -- Bastien
[O] Error when setting `org-agenda-ignore-drawer-properties' to t
Hello, Before doing an update of Org, I already had used `org-agenda-ignore-drawer-properties' (to t) to try and speed up the agenda. Though, I did not know that it wasn't a `t/nil' answer, and the results was that all the agenda views were broken (with an error generated, mysterious for the lambda user). I now know I had to write something like: --8---cut here---start-8--- (setq org-agenda-ignore-drawer-properties '(effort category)) --8---cut here---end---8--- But my question is: are such errors allowed (because they result of a wrong user customization), or do they have to be wrapped in order no to result in an error? What's the philosophy to be taken: leave it as is (knowing that it does work the expected way, when set'ted correctly)? Best regards, Seb PS- BTW, the speedup is really feel-able... Thanks! -- Sebastien Vauban
Re: [O] BUG: Decimal numbers using commata not recognised
Am 09.09.2013 10:22, schrieb Bastien: Hi Andreas, Andreas Röhler andreas.roeh...@easy-emacs.de writes: Decimal numbers using commata not recognised by org-table-convert-region Did you try to customize `org-table-number-regexp'? Hi Bastiens, okay, for me that customization would be fine probably - even if a respectable regexp is waiting :) The question showed up today at Emacs help, OP asked for a quick way to make up a sheet. So, if org-table would be smart enough to detect the common dot-or-comma issue here, maybe that's a plus. Thanks all, Andreas
[O] error message at line break
When writing at every automatic break at the end of a line I get this error message: org-comment-line-break-function: Wrong type argument: char-or-string-p, nil It doesn't hurt much though it's a bit annoying. Org-mode version 8.1.1 (release_8.1.1-7-gaecdf5-git) Greetings, henry
Re: [O] Outline cycling does not preserve point's position
On 9.9.2013, at 13:32, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
On 9.9.2013, at 10:38, Bastien b...@gnu.org wrote:
We could have org-ctrldown and friends the same way we have org-shift*
commands. org-ctrldown would use `org-forward-element' when on some
Org element, and `forward-paragraph' elsewhere.
elsewhere doesn't make sense here since point is _always_ on an element
(except on the first blank lines in a buffer).
I acknowledge binding C-down to `org-forward-element' instead of
`forward-paragraph' is a bit disruptive, and maybe not ideal in all
situations.
Yes, it produces unexpected results.
I find it pretty predictable. May you elaborate on that?
Hi Nicolas,
It is extremely predictable if you know about the structure of an Org document
and if you think in elements.
It is unexpected for a user who is used to C-arrow doing paragraph motion. In
Org, org-backward-element climbs out if a hierarchy. This is not what happens
in other modes with this command. That is what I mean with unexpected.
Don't get me wrong. I love the element motion stuff. But I am satisfied for
it to be available on M-{ and M-}.
I like your proposal to introduce a variable for special src behavior. I
personally would also like a variable that allows me to keep the paragraph
commands on C-arrow (because I have almost equally convenient bindings with
M-{}) - but maybe that is just me?
Regards
- Carsten
[O] [BUG] Clocktable error with multiple source files from parent dir
Hello, While generating a clock table report with source data in files from the current directory works, it does not work if there are *more than one* such source file in the parent directory. Yes, I known, the description is strange... Though, it seems to be the criteria... ECM and recipe: 1. Source file `clock-file.org' (with clocking lines) --8---cut here---start-8--- #+TITLE: Clock file * Tasks Task with a CLOCK line. ** Design *** TODO Do this :LOGBOOK: CLOCK: [2013-06-19 Wed 09:00]--[2013-06-19 Wed 10:11] = 1:11 :END: --8---cut here---end---8--- 2. Report file `report-same-level.org', in the same directory --8---cut here---start-8--- #+TITLE: Reporting * Summary #+BEGIN: clocktable :scope (./clock-file.org ./clock-file.org) :block 2013-06 :indent t #+END: --8---cut here---end---8--- When updating the dblock, you'll get the right report, in double (as I've included twice the same input file). 3. Report file `report-subdir-level.org', in a sub-directory --8---cut here---start-8--- #+TITLE: Reporting * Summary #+BEGIN: clocktable :scope (../clock-file.org ../clock-file.org) :block 2013-06 :indent t #+END: --8---cut here---end---8--- When updating the dblock, you'll get the error: --8---cut here---start-8--- Non-existent agenda file ../clock-file.org. [R]emove from list or [A]bort? --8---cut here---end---8--- Though, if you just put one instance of the source file, you'll get the right report (once, then). In the ECM, I'm using twice the same file, for the sake of simplicity, to reproduce the problem. But it's not due to that. You can get the same error with a local (to the dir) file and one from the parent directory: - :scope (clock-file.org clock-file.org) will work. 2 local files. - :scope (../clock-file.org clock-file.org) as well. 1 local file, 1 from parent directory. - :scope (clock-file.org ../clock-file.org) as well. 1 local file, 1 from parent directory. - :scope (../clock-file.org ../clock-file.org) WON'T! 2 files from PARENT directory. You can see the bug reproduced in a 37-second video session on http://screencast.com/t/xMCMe9kRU. Best regards, Seb -- Sebastien Vauban
Re: [O] Outline cycling does not preserve point's position
It is extremely predictable if you know about the structure of an Org document and if you think in elements. Move over the smart navigation to C-M-f and friends. (info (emacs) Expressions) Programmers among us can exploit it. Org mode is essentially a text mode. The paragraph movement commands should more or less behave right like what it would do in a text-mode document. One lane for Programmers to move around. Another lane for Text-Mode folks to around. Minimal collision. Smoother traffic. Everyone happy, happy!
Re: [O] Outline cycling does not preserve point's position
Hello, Bastien b...@gnu.org writes: But you got the idea: use `org-forward-element' when moving within structural elements of various kinds make sense and use `forward-paragraph' otherwise. No, I still don't get the idea, really. It is predictable, but sometimes counter-intuitive: for example, when on the first headline, C-up will throw an error instead of moving to the top of the buffer. Sure, but otherwise it would conflict with your point below. Also, it is predictable but not reversible: hitting C-down three times then C-up three times will not always go back to the point where the user was at the beginning. You need to return an error when there is no element at the same level. IIRC, it was initially the case. But then a user complained that, in the following example, X being the point: :PROPERTIES: X:PROP1: value :END: `org-forward-element' would return an error Cannot move further down, which was difficult to understand. predictable, intuitive, reversible, pick two. Regards, -- Nicolas Goaziou
[O] 'org-calendar-holiday's not in an org agenda org file
In order to include holidays in the org agenda for current day or week (M-x org-agenda RET a), you have to put the following line in one of the org-agenda-files: %%(org-calendar-holiday) Is there a way to include holidays in the org agenda for current day or week without putting %%(org-calendar-holiday) in one of the org agenda org files? -- Enda
Re: [O] Outline cycling does not preserve point's position
Carsten Dominik carsten.domi...@gmail.com writes:
It is extremely predictable if you know about the structure of an Org
document and if you think in elements.
It's a Sexp motion.
It is unexpected for a user who is used to C-arrow doing paragraph
motion. In Org, org-backward-element climbs out if a hierarchy. This
is not what happens in other modes with this command. That is what
I mean with unexpected.
OK. Do you want it to return an error if there's no element at the same
level above (or below for the forward counterpart)?
Don't get me wrong. I love the element motion stuff. But I am
satisfied for it to be available on M-{ and M-}.
I like your proposal to introduce a variable for special src behavior.
I personally would also like a variable that allows me to keep the
paragraph commands on C-arrow (because I have almost equally
convenient bindings with M-{}) - but maybe that is just me?
But `org-forward-element'/`org-backward-element' are the paragraph
commands for Org. Unlike to Text mode, contents in Org have a depth. So
it's not just about stopping at blank lines. Even stopping at blank
lines is not satisfying:
XParagraph
| a | table |
Another paragraph
A decent forward paragraph command should stop at the table here. On the
other hand, it doesn't make much sense to stop at the blank line below:
X#+begin_src emacs-lisp
;; line 1
;; line 2
#+end_src
Another paragraph
When depth isn't involved, I think that `org-forward-element' is as good
as it can get as a paragraph motion command, and far better than
`forward-paragraph' from paragraphs.el.
Regards,
--
Nicolas Goaziou
Re: [O] error message at line break
Hello, henry atting s...@online.de writes: When writing at every automatic break at the end of a line I get this error message: org-comment-line-break-function: Wrong type argument: char-or-string-p, nil It doesn't hurt much though it's a bit annoying. Org-mode version 8.1.1 (release_8.1.1-7-gaecdf5-git) I cannot reproduce the problem. Could you check your installation? Regards, -- Nicolas Goaziou
Re: [O] org-insert-heading rewritten from scratch
Hi Carsten On Thu, Aug 8, 2013 at 8:43 AM, Carsten Dominik carsten.domi...@gmail.com wrote: I have rewritten org-insert-heading, because it had become an unmaintainable beast. Please follow up in this thread if you find problems with the new implementation. Very likely there will be bugs, but now I am at least confident they can be fixed. On the way of rewiring my muscle memory from C-RET to M-RET for some cases, I stumbled across this: #+DRAWERS: MyStructuredDrawer :MyStructuredDrawer: - a :END: To insert a new item I once changed to use C-RET also on items. How is one supposed to do this now within a drawer? M-RET just inserts an empty line. I would like to suggest the attached patches with an ERT. They change (fix?) org-meta-return to insert a new item in this case. About the following different issue I don't care as much and only wanted to report: C-RET before any headline when within a drawer, or generally before any headline(?), could bark instead of changing to a headline leading to invalid Org syntax within a drawer. Michael From 6bc4c15c4a76a98c841e8a200c75f5a0737ffece Mon Sep 17 00:00:00 2001 From: Michael Brand michael.ch.br...@gmail.com Date: Mon, 9 Sep 2013 18:38:58 +0200 Subject: [PATCH 1/2] Add ERTs for org-meta-return * testing/lisp/test-org-list.el (test-org-list/insert-item): Adapt docstring. * (test-org-list/meta-return): New `ert-deftest' to test `org-meta-return'. --- testing/lisp/test-org-list.el | 18 +- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/testing/lisp/test-org-list.el b/testing/lisp/test-org-list.el index ac81d4d..ea19606 100644 --- a/testing/lisp/test-org-list.el +++ b/testing/lisp/test-org-list.el @@ -627,7 +627,7 @@ (should (org-invisible-p2 (ert-deftest test-org-list/insert-item () - Test item insertion. + Test item insertion with `org-insert-item'. ;; Blank lines specifications. ;; ;; Non-nil `org-blank-before-new-entry': insert a blank line, unless @@ -713,6 +713,22 @@ (forward-line -1) (looking-at $) +(ert-deftest test-org-list/meta-return () + Test item insertion with `org-meta-return'. + (should + (org-test-with-temp-text - a + (org-meta-return) + (beginning-of-line) + (looking-at - $))) + ;; TODO Insert an item also in a drawer. + (should + (let ((org-drawers '(MYDRAWER))) + (org-test-with-temp-text :MYDRAWER:\n- a\n:END: + (forward-line) + (org-meta-return) + (forward-line -1) + (looking-at $) + (ert-deftest test-org-list/repair () Test `org-list-repair' specifications. ;; Repair indentation. -- 1.7.12.4 (Apple Git-37) From 9896499fb7f497a13857b5b86f33cfbf1b918029 Mon Sep 17 00:00:00 2001 From: Michael Brand michael.ch.br...@gmail.com Date: Mon, 9 Sep 2013 18:40:07 +0200 Subject: [PATCH 2/2] org-meta-return: Insert an item also in a drawer * lisp/org.el (org-meta-return): Exclude item from cond for drawer. * testing/lisp/test-org-list.el (test-org-list/meta-return): On an item in a drawer expect an item to be inserted. --- lisp/org.el | 3 ++- testing/lisp/test-org-list.el | 6 +++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 59a22a2..edc8725 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -20698,7 +20698,8 @@ See the individual commands for more information. (org-check-before-invisible-edit 'insert) (cond ((run-hook-with-args-until-success 'org-metareturn-hook)) - ((or (org-at-drawer-p) (org-in-drawer-p) (org-at-property-p)) + ((and (or (org-at-drawer-p) (org-in-drawer-p) (org-at-property-p)) +(not (org-in-item-p))) (newline-and-indent)) ((org-at-table-p) (call-interactively 'org-table-wrap-region)) diff --git a/testing/lisp/test-org-list.el b/testing/lisp/test-org-list.el index ea19606..f3ced15 100644 --- a/testing/lisp/test-org-list.el +++ b/testing/lisp/test-org-list.el @@ -720,14 +720,14 @@ (org-meta-return) (beginning-of-line) (looking-at - $))) - ;; TODO Insert an item also in a drawer. + ;; Insert an item also in a drawer. (should (let ((org-drawers '(MYDRAWER))) (org-test-with-temp-text :MYDRAWER:\n- a\n:END: (forward-line) (org-meta-return) - (forward-line -1) - (looking-at $) + (beginning-of-line) + (looking-at - $) (ert-deftest test-org-list/repair () Test `org-list-repair' specifications. -- 1.7.12.4 (Apple Git-37)
Re: [O] error message at line break
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, henry atting s...@online.de writes: When writing at every automatic break at the end of a line I get this error message: org-comment-line-break-function: Wrong type argument: char-or-string-p, nil It doesn't hurt much though it's a bit annoying. Org-mode version 8.1.1 (release_8.1.1-7-gaecdf5-git) I cannot reproduce the problem. Could you check your installation? Ah, I see, it has something to do with org-tree-slide. I start tree-slide as default with a hook and disable it when I work on an org file. As this problem is very special I will not explain it further (but if someone is interested I will do so) Regards, Greetings, henry
Re: [O] Outline cycling does not preserve point's position
Hello Nicolas,
Nicolas Goaziou wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
It is extremely predictable if you know about the structure of an Org
document and if you think in elements.
It's a Sexp motion.
It is unexpected for a user who is used to C-arrow doing paragraph
motion. In Org, org-backward-element climbs out if a hierarchy. This
is not what happens in other modes with this command. That is what
I mean with unexpected.
OK. Do you want it to return an error if there's no element at the same
level above (or below for the forward counterpart)?
Don't get me wrong. I love the element motion stuff. But I am
satisfied for it to be available on M-{ and M-}.
I like your proposal to introduce a variable for special src behavior.
I personally would also like a variable that allows me to keep the
paragraph commands on C-arrow (because I have almost equally
convenient bindings with M-{}) - but maybe that is just me?
But `org-forward-element'/`org-backward-element' are the paragraph
commands for Org. Unlike to Text mode, contents in Org have a depth. So
it's not just about stopping at blank lines. Even stopping at blank
lines is not satisfying:
XParagraph
| a | table |
Another paragraph
A decent forward paragraph command should stop at the table here. On the
other hand, it doesn't make much sense to stop at the blank line below:
X#+begin_src emacs-lisp
;; line 1
;; line 2
#+end_src
Another paragraph
When depth isn't involved, I think that `org-forward-element' is as good
as it can get as a paragraph motion command, and far better than
`forward-paragraph' from paragraphs.el.
I think everybody would be happy if what you proposed at 13:32 can be
implemented:
From: Nicolas Goaziou n.goaz...@gmail.com
Date: Mon, 09 Sep 2013 13:30:33 +0200 (6 hours, 7 minutes, 27 seconds ago)
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
This might be difficult, but not impossible.
I think this might be a question for Nicolas to answer?
It boils down to something like:
(if (eq (org-element-type (org-element-at-point)) 'src-block)
;; Do forward-paragraph according to language.
...
(org-forward-element))
Though, I suggest to introduce a variable similar to
`org-src-tab-acts-natively', or group both features in the same variable
like `org-act-natively-on-src-block'.
That way, one has `org-forward-element' for moving inside most elements of the
documents, but, inside code blocks, the behavior is similar to the one we
would get if we were editing the code in an indirect buffer.
Eventually, this behavior can be controlled, as you suggested, by a variable.
I guess this is very good, and would content most, if not all, of us!
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Index of cases
Suvayu Ali writes: Hi Alan, On Mon, Sep 09, 2013 at 05:14:17PM +1000, Alan L Tyree wrote: My real problem is that I don't know how to generate the multiple indexes that I need if I use org mode. Everything else is easy. Any potential solution that I see involves adding lots more markup, but if I do that I might as well stick with LaTeX. This is indeed a subtle problem. I am having a hard time thinking of an Org way of doing this without special markup. It would have to be auto-generated in someway. So I have a somewhat non-technical suggestion. How about you give the LaTeX macros you use human readable aliases. The editors then might find it easier to edit LaTeX source directly. Not a bad idea - that coupled with a LaTeX aware editor should help the human editor get past the unfamiliarity. Thanks! Hope this helps, -- Alan L Tyree http://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
[O] org-clock-time% does not parse 1d 12:50. This is a fix. (org-mode 8.1.1)
Dear all, While I was experimenting with clock tables #+BEGIN: clocktable :maxlevel 2 :scope file :formula % I found a surprising result : if *total time* is formatted as 1d 12:50 then the percentages column gives wrong results. The reason is that org-clock-time% does not take 1d 12:50 format into account but only 12:50 format. You will find my fix of org-clock-time% below. Thank you. PH my version (defun org-clock-time% (total rest strings) Compute a time fraction in percent. TOTAL is a time string like '1d 10:21' specifying the total times. STRINGS is a list of strings that should be checked for a time. The first string that does have a time will be used. This function is made for clock tables. (let ((re \\(\\([0-9]+\\)d[[:space:]]\\)?\\([0-9]+\\):\\([0-9]+\\)) clock-str-to-minutes (tot 0) s) ;; 00:10 - 10 ;; 5d 00:00 - 7200 (setq clock-str-to-minutes (lambda (clock) (let ((minutes 0) (hours 0) (days 0) (tot 0)) (save-match-data (catch 'exit (if (not (string-match re clock)) ;; ill formatted = 0 (throw 'exit 0.) ;; parse minutes, hours, days (setq minutes (string-to-number (match-string 4 clock))) (setq hours (string-to-number (match-string 3 clock))) (if (match-string 2 clock) (setq days (string-to-number (match-string 2 clock ;; compute the time in minutes (setq tot (+ minutes (* 60 hours) (* 60 24 days) ;; compute time fraction in percent (save-match-data (catch 'exit (setq tot (funcall clock-str-to-minutes total)) (if (= tot 0.) (throw 'exit 0.)) (while (setq s (pop strings)) (throw 'exit (/ (* 100.0 (funcall clock-str-to-minutes s)) tot))) 0 original version : org-8.1.1/lisp/org-clock.el (defun org-clock-time% (total rest strings) Compute a time fraction in percent. TOTAL s a time string like 10:21 specifying the total times. STRINGS is a list of strings that should be checked for a time. The first string that does have a time will be used. This function is made for clock tables. (let ((re \\([0-9]+\\):\\([0-9]+\\)) tot s) (save-match-data (catch 'exit (if (not (string-match re total)) (throw 'exit 0.) (setq tot (+ (string-to-number (match-string 2 total)) (* 60 (string-to-number (match-string 1 total) (if (= tot 0.) (throw 'exit 0.))) (while (setq s (pop strings)) (if (string-match \\([0-9]+\\):\\([0-9]+\\) s) (throw 'exit (/ (* 100.0 (+ (string-to-number (match-string 2 s)) (* 60 (string-to-number (match-string 1 s) tot 0
Re: [O] Index of cases
Alan L Tyree writes: My real problem is that I don't know how to generate the multiple indexes that I need if I use org mode. You'd likely have to use macros (one for each index) and have a filters or derived backends sort things out. Getting to something as elaborate as the various index packages would take some time, though. Everything else is easy. Any potential solution that I see involves adding lots more markup, but if I do that I might as well stick with LaTeX. If you've organized the LaTeX maybe by using your own style file, then you could still use LaTeX as the backend and keep the actual editing in Org. At least a lot of simple editors (the software) are LaTeX aware, so my editor (the human being) should be able to handle it. I guess here's your point to stick with LaTeX: there's a good number of editors that support LaTeX, but only one that suppports all of Org, so this might be a hard sell in some places (especially those that want book manuscripts in Word, shudder). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ DIY Stuff: http://Synth.Stromeko.net/DIY.html
Re: [O] org-insert-heading rewritten from scratch
Hi Nicolas On Mon, Sep 9, 2013 at 9:10 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: FWIW, I think the test belongs to test-org.el, not to test-org-list.el. Ok, I assume, then better also with more tests than only for list items. See the attached patches that replace the previous ones. Michael From 66f6d15234bda97fc2e197efd2f9cb7c6439fef1 Mon Sep 17 00:00:00 2001 From: Michael Brand michael.ch.br...@gmail.com Date: Mon, 9 Sep 2013 22:32:36 +0200 Subject: [PATCH 1/2] Add ERTs for org-meta-return * testing/lisp/test-org.el (test-org/meta-return): New `ert-deftest' to test `org-meta-return'. --- testing/lisp/test-org.el | 45 + 1 file changed, 45 insertions(+) diff --git a/testing/lisp/test-org.el b/testing/lisp/test-org.el index 8a1e9f1..4944c24 100644 --- a/testing/lisp/test-org.el +++ b/testing/lisp/test-org.el @@ -365,6 +365,51 @@ +;;; Editing + + Insert elements + +(ert-deftest test-org/meta-return () + Test M-RET (`org-meta-return'). + ;; In a table field insert a row above. + (should + (org-test-with-temp-text | a | + (forward-char) + (org-meta-return) + (forward-line -1) + (looking-at | |$))) + ;; In a paragraph change current line into a header. + (should + (org-test-with-temp-text a + (org-meta-return) + (beginning-of-line) + (looking-at \* a$))) + ;; In an item insert an item, in this case above. + (should + (org-test-with-temp-text - a + (org-meta-return) + (beginning-of-line) + (looking-at - $))) + ;; In a drawer and paragraph insert an empty line, in this case above. + (should + (let ((org-drawers '(MYDRAWER))) + (org-test-with-temp-text :MYDRAWER:\na\n:END: + (forward-line) + (org-meta-return) + (forward-line -1) + (looking-at $ + ;; TODO In a drawer and item insert an item, in this case above. + (should + (let ((org-drawers '(MYDRAWER))) + (org-test-with-temp-text :MYDRAWER:\n- a\n:END: + (forward-line) + (org-meta-return) + (forward-line -1) + (looking-at $) + + + + ;;; Links Fuzzy Links -- 1.7.12.4 (Apple Git-37) From fddcaaed03630e7acc26ed701937b2ca17184fe5 Mon Sep 17 00:00:00 2001 From: Michael Brand michael.ch.br...@gmail.com Date: Mon, 9 Sep 2013 22:33:47 +0200 Subject: [PATCH 2/2] org-meta-return: Insert an item also in a drawer * lisp/org.el (org-meta-return): Exclude item from cond for drawer. * testing/lisp/test-org.el (test-org/meta-return): In a drawer and item insert an item. --- lisp/org.el | 3 ++- testing/lisp/test-org.el | 6 +++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 59a22a2..edc8725 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -20698,7 +20698,8 @@ See the individual commands for more information. (org-check-before-invisible-edit 'insert) (cond ((run-hook-with-args-until-success 'org-metareturn-hook)) - ((or (org-at-drawer-p) (org-in-drawer-p) (org-at-property-p)) + ((and (or (org-at-drawer-p) (org-in-drawer-p) (org-at-property-p)) +(not (org-in-item-p))) (newline-and-indent)) ((org-at-table-p) (call-interactively 'org-table-wrap-region)) diff --git a/testing/lisp/test-org.el b/testing/lisp/test-org.el index 4944c24..3538242 100644 --- a/testing/lisp/test-org.el +++ b/testing/lisp/test-org.el @@ -398,14 +398,14 @@ (org-meta-return) (forward-line -1) (looking-at $ - ;; TODO In a drawer and item insert an item, in this case above. + ;; In a drawer and item insert an item, in this case above. (should (let ((org-drawers '(MYDRAWER))) (org-test-with-temp-text :MYDRAWER:\n- a\n:END: (forward-line) (org-meta-return) - (forward-line -1) - (looking-at $) + (beginning-of-line) + (looking-at - $) -- 1.7.12.4 (Apple Git-37)
Re: [O] org-insert-heading rewritten from scratch
Hello, Michael Brand michael.ch.br...@gmail.com writes: About the following different issue I don't care as much and only wanted to report: C-RET before any headline when within a drawer, or generally before any headline(?), could bark instead of changing to a headline leading to invalid Org syntax within a drawer. I don't think it should bark, but it should insert the headline after the drawer, i.e. just before the first headline, if there's one at all, or at the end of the buffer. From 9896499fb7f497a13857b5b86f33cfbf1b918029 Mon Sep 17 00:00:00 2001 From: Michael Brand michael.ch.br...@gmail.com Date: Mon, 9 Sep 2013 18:40:07 +0200 Subject: [PATCH 2/2] org-meta-return: Insert an item also in a drawer * lisp/org.el (org-meta-return): Exclude item from cond for drawer. * testing/lisp/test-org-list.el (test-org-list/meta-return): On an item in a drawer expect an item to be inserted. FWIW, I think the test belongs to test-org.el, not to test-org-list.el. Regards, -- Nicolas Goaziou
Re: [O] Index of cases
Paul Rudin writes: Alan L Tyree alanty...@gmail.com writes: My real problem is that I don't know how to generate the multiple indexes that I need if I use org mode. Everything else is easy. Any potential solution that I see involves adding lots more markup, but if I do that I might as well stick with LaTeX. I'm not sure that needs to be the case. I don't use org-mode for LaTeX documents, but a bit of boiler-plate to generate the indexes shouldn't be too tricky. A good starting point is the manual for biblatex oscola package - which shows you to get your case, statute etc. tables with relatively little effort. http://mirror.ox.ac.uk/sites/ctan.org/macros/latex/contrib/biblatex-contrib/oscola/oscola.pdf Oscola is good and approaches the problem by maintaining a bibtex database of cases. I maintain a plain text file of my cases and retrieve them with a custom built function. I'm not sure that the resulting markup in the manuscript is much more readable with Oscola, but I need to look into it further. Thanks for the tip. -- Alan L Tyree http://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
[O] Inline plot with matplotlib
Hi all, I would like to create a plot with matplotlib and have it exported to a beamer presentation without storing the plot in a file. Is that possible? Can someone point me to an example or a good starting point? BR / Johan
Re: [O] Inline plot with matplotlib
Johan Ekh ekh.jo...@gmail.com writes: Hi all, I would like to create a plot with matplotlib and have it exported to a beamer presentation without storing the plot in a file. Is that possible? Can someone point me to an example or a good starting point? BR / Johan If matplotlib supports tikz or raw tex output formats, you could use a python code block, e.g., something like the following. #+begin_src python :results latex # Python code to print latex code for a graph #+end_src -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] Inline plot with matplotlib
Johan Ekh ekh.jo...@gmail.com writes:
Hi all,
I would like to create a plot with matplotlib and have it exported to a
beamer presentation without storing the plot in a file. Is that possible?
I guess you'd want to plot is as a pgf file, whether real of
'virtual'. You could send the result to STDOUT but it may take a bit
more effort. Also, a simple test with sys.stdout says the pgf backend
doesn't support stdout. . .
If *printing* to a pgf file everything works out of the box in recent
versions of Org.
Can someone point me to an example or a good starting point?
http://matplotlib.org/users/pgf.html
Here's an example of a simple plot.
#+TITLE: =matplotlib= and =pgf=
#+LATEX_HEADER: \usepackage{pgf}
#+NAME:spectrum
#+BEGIN_SRC python :var OUT=test.pgf :exports results :results value file
import matplotlib as mpl
pgf_with_pdflatex = {
pgf.texsystem: pdflatex,
text.usetex: True,
'pgf.rcfonts': False,
'font.size': 9,
'fond.family': 'serif',
pgf.preamble: [
r\usepackage[utf8]{inputenc},
r\usepackage[T1]{fontenc}]}
mpl.rcParams.update(pgf_with_pdflatex)
import matplotlib.pyplot as plt
from numpy import pi, cos, linspace
s1, t1, t2 = 1, .8, .2
s = lambda w: s1 / (2 * pi) * (1 + t1 ** 1 + t2 ** 2 + (1 + t2) * 2 * t1 *
cos(w) + 2 * t2 * cos(4 * w))
x = linspace(0, pi, 1000)
plt.figure(figsize=(4,1.5))
plt.plot(x, s(x))
plt.xlim( 0, pi)
plt.xlabel($\\omega$)
plt.ylabel(Spectrum)
plt.tight_layout(0)
plt.savefig(OUT, format = 'pgf')
return(OUT)
#+END_SRC
#+RESULTS: spectrum
[[file:test.pgf]]
--
. . . The proofs are technical in nature and provides no real understanding.
Re: [O] Adding text properties to all Org mode links
Hello again everyone, On Sun, Jul 14, 2013 at 08:41:25AM +0200, Suvayu Ali wrote: On Sat, Jul 13, 2013 at 11:01:08PM -0400, Nick Dokos wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: How do I add text properties to org elements? In my particular case, I want to echo tooltips when I move my cursor over an org link (or other org elements for that matter). To do this, I need to add the properties point-left and point-entered to all org-links. How do I do that? Thanks for any ideas. Not sure if this is the best method: o go to (point-min) o loop (goto-char (cdr (org-element-link-successor (point-max (org-element-link-parser) and extract :begin and :end values from the returned list Untested (mostly) - termination, error handling (and who knows what else) left to the interested reader... I was afraid of this. I think the safest way of not screwing up the parsing and error handling would be to implement it as a patch to org-activate-*-links in org.el. I was taking a shot at this again. This is where I stand at the moment: - I want to add the properties `point-left' and `point-entered' to all links where the target is invisible (hidden), so for the moment I'm focusing on bracket links. - I tried to patch `org-activate-bracket-links' to this end; in the let* bind I extended the list of properties with like this: (let* ((hl (org-match-string-no-properties 1)) (help (concat LINK: (save-match-data (org-link-unescape hl (ip (org-maybe-intangible (list 'invisible 'org-link 'keymap org-mouse-map 'mouse-face 'highlight 'font-lock-multiline t 'help-echo help 'point-left sa-echo-tooltip ; -- my addition 'point-entered sa-echo-tooltip; -- my addition 'htmlize-link `(:uri ,hl (vp (list 'keymap org-mouse-map 'mouse-face 'highlight 'font-lock-multiline t 'help-echo help 'point-left sa-echo-tooltip; -- my addition 'point-entered sa-echo-tooltip ; -- my addition 'htmlize-link `(:uri ,hl ;; rest of the code is unchanged ) With this new org-activate-bracket-links, when I open an Org file, I see some bad fontification (e.g. keywords are in default face) and the invisible parts of backet links are visible. As in: instead of showing this is a link (in org-link face) I see [[http://www.example.com/target][this is a link]] (the http part is in org-link face, the rest in default) I tried to run edebug-defun on org-activate-bracket-links before opening the org file, but that doesn't trigger the step by step execution of org-activate-bracket-links I was expecting. I tested with `get-text-property' interactively, my properties were not added to the links. So I'm wondering what am I doing wrong? Better yet, is there a better way to do this? Thanks for any help or ideas. Cheers, -- Suvayu Open source is the future. It sets us free.
[O] How to represent parse-tree so that 'org-element-interpret-data' works?
Hi List, how do I get the printed representation of an org-file parse-tree that can be reverted to the original org-file with `'org-element-interpret-data'? No matter if I use print, princ, prin1, (format %s ) or (format %S ...) to get the parse-tree in textual form, with or without setting (print-circle nil), there are always errors. E.g. given file tmp.org: ,--- | #+options: toc:nil | * A | B `--- #+begin_src emacs-lisp (with-current-buffer tmp.org (org-element-interpret-data (org-element-parse-buffer))) #+end_src yields: , | #+OPTIONS: toc:nil | * A | B | ` but, e.g., this #+begin_src emacs-lisp (with-current-buffer tmp.org (print (org-element-parse-buffer))) #+end_src yields: #+begin_src emacs-lisp (org-data nil (section (:begin 1 :end 20 :contents-begin 1 :contents-end 20 :post-blank 0 :parent #0) (keyword (:key OPTIONS :value toc:nil :begin 1 :end 20 :post-blank 0 :post-affiliated 1 :parent #1))) (headline (:raw-value A :begin 20 :end 26 :pre-blank 0 :hiddenp nil :contents-begin 24 :contents-end 26 :level 1 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 0 :footnote-section-p nil :archivedp nil :commentedp nil :quotedp nil :CATEGORY nil :title (#(A 0 1 (:parent #1))) :parent #0) (section (:begin 24 :end 26 :contents-begin 24 :contents-end 26 :post-blank 0 :parent #1) (paragraph (:begin 24 :end 26 :contents-begin 24 :contents-end 26 :post-blank 0 :post-affiliated 24 :parent #2) #(B 0 2 (:parent #3)) #+end_src what can't be used with 'org-element-interpret-data. -- cheers, Thorsten
Re: [O] Index of cases
On Sep 9, 2013 3:14 AM, Alan L Tyree alanty...@gmail.com wrote: snip At least a lot of simple editors (the software) are LaTeX aware, so my editor (the human being) should be able to handle it. I don't know it well, but Lyx http://wiki.lyx.org/FAQ/LyX purports to almost be LaTeX and almost be WYSIWYG, so that might be an editor to try for those who will find markup scary. HTH, Brian vdB
[O] When will the BEGIN_/END_HTML block be ignored?
Hi, I am tracking an issue in the org-reveal exporter, which is about the BEGIN_/END_HTML blocks being not exported. I am wondering whether there is some variable or configurations that can disable the BEGIN_/END_HTML block exporting? Thanks, Yujie
[O] [BUG] Links are not followed when in tables
Hello, Links (both internal and external) are not followed when in tables. ECM: --8---cut here---start-8--- #+TITLE: ECM Reference Card * Options The following table lists the options that one can use. | [[aaa][aaa]] | [[#ccc][ccc]] | | [[bbb][bbb]] | [[#ddd][ddd]] | (and many, many more) ** aaa :PROPERTIES: :CUSTOM_ID: aaa :END: Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. ** bbb :PROPERTIES: :CUSTOM_ID: bbb :END: Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. Aenean ultricies mi vitae est. Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi... ** ccc :PROPERTIES: :CUSTOM_ID: ccc :END: Phasellus ut libero. Nulla in libero non enim tristique sollicitudin. Ut tempor. Phasellus pellentesque augue eget ante. Mauris malesuada. Donec sit amet diam sit amet dolor placerat blandit. Morbi enim purus, imperdiet in, molestie sit amet, pellentesque eu, mauris. In vel erat vel ipsum bibendum commodo. Curabitur accumsan. Nam sed metus. Etiam tristique bibendum justo. *** See also [[aaa][aaa]] \\ [[bbb][bbb]] ** ddd :PROPERTIES: :CUSTOM_ID: ddd :END: --8---cut here---end---8--- Recipe: 1. Press RET on links you can find in the table - RET simply goes to the following line. 2. Press RET on links you can find in the See also section - the cursor moves to the right location. Best regards, Seb -- Sebastien Vauban
[O] [BUG] Table not recomputed (incorrect results)
Hello, I'm loosing my latin with the following table, which Org declares as converged or already stable. --8---cut here---start-8--- #+TITLE: Birthday * Commande | mini sandwiches | 261 | 1.00 | 260.00 | | rauwkostchotels | 2 | 36. | 72.00 | | koude hapjes| 130 | | 0.00 | | dessertjes (in hapjes glaasjes) | 90 |3 | 0.00 | |-+-+--+| | total | | | 332. | #+TBLFM: $4=$2*$3;%.2f::@2$3=30*1.2::@5$4=vsum(@1..@-1) Total paid: *580 EUR*... --8---cut here---end---8--- Obviously, if you look at the amounts, it isn't correct... What am I not seeing? Best regards, Seb -- Sebastien Vauban
Re: [O] [BUG] Table not recomputed (incorrect results)
On 10.9.2013, at 04:32, Sebastien Vauban sva-n...@mygooglest.com wrote: Hello, I'm loosing my latin with the following table, which Org declares as converged or already stable. --8---cut here---start-8--- #+TITLE: Birthday * Commande | mini sandwiches | 261 | 1.00 | 260.00 | | rauwkostchotels | 2 | 36. | 72.00 | | koude hapjes| 130 | | 0.00 | | dessertjes (in hapjes glaasjes) | 90 |3 | 0.00 | |-+-+--+| | total | | | 332. | #+TBLFM: $4=$2*$3;%.2f::@2$3=30*1.2::@5$4=vsum(@1..@-1) Total paid: *580 EUR*... --8---cut here---end---8--- Obviously, if you look at the amounts, it isn't correct... Hi Sebastien, The first four lines are all above the first hline and are therefore treated as header and are exempt from calculation. Formular applying to these fields are ignored. Add a header line to the table: | a | b |c |d | |-+-+--+--| | mini sandwiches | 261 | 1.00 | 261. | | rauwkostchotels | 2 | 36. | 72. | | koude hapjes| 130 | |0 | | dessertjes (in hapjes glaasjes) | 90 |3 | 270 | |-+-+--+--| | total | | |0 | #+TBLFM: $4=$2*$3;%.2f::@2$3=30*1.2::@5$4=vsum(@1..@-1) Cheers - Carsten What am I not seeing? Best regards, Seb -- Sebastien Vauban signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] Outline cycling does not preserve point's position
On 9.9.2013, at 17:41, Nicolas Goaziou n.goaz...@gmail.com wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
It is extremely predictable if you know about the structure of an Org
document and if you think in elements.
It's a Sexp motion.
It is unexpected for a user who is used to C-arrow doing paragraph
motion. In Org, org-backward-element climbs out if a hierarchy. This
is not what happens in other modes with this command. That is what
I mean with unexpected.
OK. Do you want it to return an error if there's no element at the same
level above (or below for the forward counterpart)?
No, I guess not. Lets just leave it the way it is, but implement
alternative behavior in source code blocks. I agree with the arguments you
make below.
Thank you.
- Carsten
Don't get me wrong. I love the element motion stuff. But I am
satisfied for it to be available on M-{ and M-}.
I like your proposal to introduce a variable for special src behavior.
I personally would also like a variable that allows me to keep the
paragraph commands on C-arrow (because I have almost equally
convenient bindings with M-{}) - but maybe that is just me?
But `org-forward-element'/`org-backward-element' are the paragraph
commands for Org. Unlike to Text mode, contents in Org have a depth. So
it's not just about stopping at blank lines. Even stopping at blank
lines is not satisfying:
XParagraph
| a | table |
Another paragraph
A decent forward paragraph command should stop at the table here. On the
other hand, it doesn't make much sense to stop at the blank line below:
X#+begin_src emacs-lisp
;; line 1
;; line 2
#+end_src
Another paragraph
When depth isn't involved, I think that `org-forward-element' is as good
as it can get as a paragraph motion command, and far better than
`forward-paragraph' from paragraphs.el.
Regards,
--
Nicolas Goaziou
signature.asc
Description: Message signed with OpenPGP using GPGMail
Re: [O] Index of cases
Lyx is brilliant - I used it to typeset a cookbook that my wife wrote and then I wrote a small text Self-publishing with LyX. Anyone can learn to use it in a short time. It was my first thought, but unfortunately there doesn't seem to be an easy way to import LaTeX where the LaTeX file has multiple indexes. The LyX folks are working on that. Cheers, Alan On Tue, Sep 10, 2013 at 10:40 AM, Brian van den Broek brian.van.den.br...@gmail.com wrote: On Sep 9, 2013 3:14 AM, Alan L Tyree alanty...@gmail.com wrote: snip At least a lot of simple editors (the software) are LaTeX aware, so my editor (the human being) should be able to handle it. I don't know it well, but Lyx http://wiki.lyx.org/FAQ/LyX purports to almost be LaTeX and almost be WYSIWYG, so that might be an editor to try for those who will find markup scary. HTH, Brian vdB -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206sip:typh...@iptel.org
Re: [O] [BUG] Links are not followed when in tables
Hi Sebastien, use C-c C-o to follow links in tables. That is the general command to follow links - RET is only a convenience hack. In tables, the row motion action of RET is considered to be more important, as this is the standard behavior in spreadsheet applications. Regards - Carsten On 10.9.2013, at 04:18, Sebastien Vauban sva-n...@mygooglest.com wrote: Hello, Links (both internal and external) are not followed when in tables. ECM: --8---cut here---start-8--- #+TITLE: ECM Reference Card * Options The following table lists the options that one can use. | [[aaa][aaa]] | [[#ccc][ccc]] | | [[bbb][bbb]] | [[#ddd][ddd]] | (and many, many more) ** aaa :PROPERTIES: :CUSTOM_ID: aaa :END: Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. ** bbb :PROPERTIES: :CUSTOM_ID: bbb :END: Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. Aenean ultricies mi vitae est. Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi... ** ccc :PROPERTIES: :CUSTOM_ID: ccc :END: Phasellus ut libero. Nulla in libero non enim tristique sollicitudin. Ut tempor. Phasellus pellentesque augue eget ante. Mauris malesuada. Donec sit amet diam sit amet dolor placerat blandit. Morbi enim purus, imperdiet in, molestie sit amet, pellentesque eu, mauris. In vel erat vel ipsum bibendum commodo. Curabitur accumsan. Nam sed metus. Etiam tristique bibendum justo. *** See also [[aaa][aaa]] \\ [[bbb][bbb]] ** ddd :PROPERTIES: :CUSTOM_ID: ddd :END: --8---cut here---end---8--- Recipe: 1. Press RET on links you can find in the table - RET simply goes to the following line. 2. Press RET on links you can find in the See also section - the cursor moves to the right location. Best regards, Seb -- Sebastien Vauban signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] [BUG] Links are not followed when in tables
On 10.9.2013, at 06:33, Carsten Dominik carsten.domi...@gmail.com wrote: Hi Sebastien, use C-c C-o to follow links in tables. That is the general command to follow links - RET is only a convenience hack. In tables, the row motion action of RET is considered to be more important, as this is the standard behavior in spreadsheet applications. P.S. this is actually documented on the docstring of the variable `org-return-follows-link'. - Carsten Regards - Carsten On 10.9.2013, at 04:18, Sebastien Vauban sva-n...@mygooglest.com wrote: Hello, Links (both internal and external) are not followed when in tables. ECM: --8---cut here---start-8--- #+TITLE: ECM Reference Card * Options The following table lists the options that one can use. | [[aaa][aaa]] | [[#ccc][ccc]] | | [[bbb][bbb]] | [[#ddd][ddd]] | (and many, many more) ** aaa :PROPERTIES: :CUSTOM_ID: aaa :END: Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. ** bbb :PROPERTIES: :CUSTOM_ID: bbb :END: Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Vestibulum tortor quam, feugiat vitae, ultricies eget, tempor sit amet, ante. Donec eu libero sit amet quam egestas semper. Aenean ultricies mi vitae est. Mauris placerat eleifend leo. Quisque sit amet est et sapien ullamcorper pharetra. Vestibulum erat wisi... ** ccc :PROPERTIES: :CUSTOM_ID: ccc :END: Phasellus ut libero. Nulla in libero non enim tristique sollicitudin. Ut tempor. Phasellus pellentesque augue eget ante. Mauris malesuada. Donec sit amet diam sit amet dolor placerat blandit. Morbi enim purus, imperdiet in, molestie sit amet, pellentesque eu, mauris. In vel erat vel ipsum bibendum commodo. Curabitur accumsan. Nam sed metus. Etiam tristique bibendum justo. *** See also [[aaa][aaa]] \\ [[bbb][bbb]] ** ddd :PROPERTIES: :CUSTOM_ID: ddd :END: --8---cut here---end---8--- Recipe: 1. Press RET on links you can find in the table - RET simply goes to the following line. 2. Press RET on links you can find in the See also section - the cursor moves to the right location. Best regards, Seb -- Sebastien Vauban signature.asc Description: Message signed with OpenPGP using GPGMail
