[O] SCHEDULED timestamp becoming empty
Hello, Maybe it's some sort of conflict with custom settings I would have (though, I don't see what could cause such a thing) but I've observed for a couple of weeks (maybe 3 or 4) that changing the SCHEDULED date *from* the agenda view (S-left'ing) removes the timestamp part, leaving such a task: --8---cut here---start-8--- ** Do this SCHEDULED: --8---cut here---end---8--- This is not 100% reproducible. On the contrary, it seems to be the case for the first update only, not the following ones done in the same agenda view (for tasks from the same file? for all?). I still don't get the exact conditions which are necessary to make that update fail, but I wonder if I'm alone or not? Hopefully, I'm working with Git'ted files, so such cases are identified easily, but this is quite scary nonetheless. Best regards, Seb -- Sebastien Vauban
Re: [O] Collaborating with TODO lists and clocks.
Samuel Loury wrote: I recently encountered the issues of having to collaborate with other persons on the same task (all of us would need at some point to clock into this task). I thought that changing the value of the variable org-clock-string could help, but I have not tried it yet. Let me explain why it could help: It is for the time being set to CLOCK:, but imagine that the user A set it to CLOCK-A: and the user B set it to CLOCK-B: (in their respective .emacs files), then after some time a clocked task would then look like: * Do something CLOCK-A: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] = 0:51 CLOCK-A: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] = 0:36 CLOCK-B: [2013-09-04 Wed 08:00]--[2013-09-04 Wed 09:03] = 1:03 Then the agenda for each user would report only the time spent by himself. The time spent by each participant is clearly separated. There are some problems with doing so: - I don't know yet how to configure a report showing the time spent by every body, - I am not sure the clock time sum would work. - grepping for CLOCK: on org sources shows: --8---cut here---start-8--- ./lisp/org-clock.el:782:(while (re-search-forward CLOCK: \\(\\[.*?\\]\\)$ nil t) ./lisp/org.el:851: (defcustom org-clock-string CLOCK: ./lisp/org.el:8501: (while (re-search-forward ^[ \t]*CLOCK:.*$ nil t) ./lisp/org.el:15007: (defconst org-clock-drawer-start-re ^[ \t]*:CLOCK:[ \t]*$ ./lisp/org.el:15578: (while (looking-at ^[ \t]*\\(:CLOCK:\\|:LOGBOOK:\\|CLOCK:\\|:END:\\)) ./lisp/org.el:15579: (if (member (match-string 1) '(CLOCK: :END:)) ./lisp/org.el:17278: (looking-at ^[ \t]*CLOCK:))) --8---cut here---end---8--- Those look like hard coded CLOCK: instead of using org-clock-string. They would need to be fixed. What do you think of this solution? Has anyone already use a solution like this? Best, PS: I have tried changing the org-clock-into-drawer variable to be CLOCK-A and CLOCK-B so that the task would then look like * Do something :CLOCK-A: CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] = 0:51 CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] = 0:36 :END: :CLOCK-B: CLOCK: [2013-09-04 Wed 08:00]--[2013-09-04 Wed 09:03] = 1:03 :END: But it needs org-drawers to contain the values for each collaborators for it to work (and then should be maintained) and the folding mechanism did not seem to work for those special drawers. Having thought about that in the past, I had thought of adding tags after clock lines, such as: --8---cut here---start-8--- CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] = 0:51 :userA: CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] = 0:36 :devB: --8---cut here---end---8--- Though, having separate CLOCK drawers would even be better for Git merges, such as (keeping the idea of pseudo-tags): --8---cut here---start-8--- :CLOCK:userA: CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] = 0:51 CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] = 0:36 :END: :CLOCK:devB: CLOCK: [2013-09-04 Wed 08:00]--[2013-09-04 Wed 09:03] = 1:03 :END: --8---cut here---end---8--- But, of course, a lot of development is required to make this become usable: - clocking reports (`R') must be updated with the knowledge of the current user - clock checking functions (`v c') must be enhanced to ignore clocks from other users - etc. Best regards, Seb -- Sebastien Vauban
Re: [O] Collaborating with TODO lists and clocks.
Samuel Loury wrote: Sebastien Vauban sva-n...@mygooglest.com writes: Having thought about that in the past, I had thought of adding tags after clock lines, such as: --8---cut here---start-8--- CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] = 0:51 :userA: CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] = 0:36 :devB: --8---cut here---end---8--- That sounds good also. Inserting the user is easy to do with: #+begin_src emacs-lisp (defun org-clock-out-mark-clock () (unless remove (insert (format :%s: user-full-name (add-hook 'org-clock-out-hook 'org-clock-out-mark-clock) #+end_src Though, having separate CLOCK drawers would even be better for Git merges, such as (keeping the idea of pseudo-tags): --8---cut here---start-8--- :CLOCK:userA: CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] = 0:51 CLOCK: [2013-09-04 Wed 09:05]--[2013-09-04 Wed 09:41] = 0:36 :END: :CLOCK:devB: CLOCK: [2013-09-04 Wed 08:00]--[2013-09-04 Wed 09:03] = 1:03 :END: --8---cut here---end---8--- I really like this solution. But, of course, a lot of development is required to make this become usable: - clocking reports (`R') must be updated with the knowledge of the current user - clock checking functions (`v c') must be enhanced to ignore clocks from other users - etc. That is my point with the solution by customization of org-clock-string. It appears to need only a few corrections of the hard coded CLOCK: string (that would be required anyway) and it looks like it would work out of the box without further development. Wouldn't it? I've no real idea about how much should be changed for everything to work back as expected [1], as there are so many functions relying on time clocking. Just to add two extra points to the above list of possibly complex code changes: - column view with time summing, - `org-clock-display' (C-c C-x C-d), which shows subtree times in the entire buffer Maybe you want to give it a try? Though, I fear such a support requires more than what we expect -- while not looking at the details (where the devil is). For example, IIUC, different users will share one file with tasks, where they will clock in/out. Then, what about the SCHEDULED and DEADLINE properties? Will the tasks be in all the user agendas? Not acceptable. Then, we need first to add an ASSIGNEE property, and ignore tasks which wouldn't be assigned to me [2]? Don't misunderstand me. I'm not trying to convince you or anybody to stop and cry. On the contrary, I feel that some such possibilities are _needed_ to transform Org from a personal organizer to a team organizer. I'd be happy that this would already be the case (and that we would have a real Web interface for editing the files ;-)). So, this discussion clearly is interesting, at least for providing ideas and a common view on what's missing / what should be nice to have. Best regards, Seb [1] Don't forget we should be backward-compatible as well... [2] For backward-compatibility, I guess we'd need to keep unassigned tasks in all agenda views. Maybe not that nice. -- Sebastien Vauban
Re: [O] The color theme on the official website
Ben Duan wrote: What's the name of the color theme on the official site of orgmode? ( http://orgmode.org/img/main.jpg) Dunno. And do you have any other recommendations for color themes? See http://orgmode.org/worg/color-themes-screenshot.html. Best regards, Seb -- Sebastien Vauban
[O] Outline cycling does not preserve point's position
Hello, Since a little while, I've observed that point's position is not anymore preserved when cycling buffer's view with S-TAB. Sometimes, point stays where it was (even when in the body of entries); sometimes, not. See http://screencast.com/t/1sr6Lezk: - when on the first letter of From, in that example, point's location is preserved; - when on the second letter of it, point's location is lost: new position is at the end of the level 1 parent... 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. Best regards, Seb -- Sebastien Vauban
Re: [O] Outline cycling does not preserve point's position
Hi Carsten, 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. Sometimes, point stays where it was (even when in the body of entries); sometimes, not. See http://screencast.com/t/1sr6Lezk: - when on the first letter of From, in that example, point's location is preserved; - when on the second letter of it, point's location is lost: new position is at the end of the level 1 parent... 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. you say since a little while. Have you tried to bisect? Not yet. I have many Chinese plates turning at the moment, but I'll try to do that very soon. And I have other problems to report or bisect: - 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; - 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. Or has it been like this always? In my mind, this did work before; or, at least, in (many) more cases than it now does. Also, I am not convinced that staying in invisible places is the right behavior at all. Even though I would agree that three S-TAB in a row should be a null operation. 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. May be it would be better to use something like (org-display-outline-path nil t) to see where you are? I know where I am: I'm using that. But, sometimes (in fact, often), I want to see the rest of the entries (brothers, parents, etc.) in the outline view. I simply expect to land back at the entry I was at, when having cycled 3 times. Best regards, Seb -- Sebastien Vauban
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] 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
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
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 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
[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
[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
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
[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)
Hi Carsten, Carsten Dominik wrote: On 10.9.2013, at 04:32, Sebastien Vauban sva-n...@mygooglest.com wrote: 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) --8---cut here---end---8--- Obviously, if you look at the amounts, it isn't correct... 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. Whoa. Did not know that... (or already forgotten about!) Add a header line to the table: OK, thanks! Best regards, Seb -- Sebastien Vauban
Re: [O] [BUG] Links are not followed when in tables
Hi Carsten, Carsten Dominik wrote: On 10.9.2013, at 06:33, Carsten Dominik carsten.domi...@gmail.com wrote: On 10.9.2013, at 04:18, Sebastien Vauban sva-n...@mygooglest.com wrote: Links (both internal and external) are not followed when in tables. 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. 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. I (almost) never use `C-c C-o'... This explains my surprise... P.S. this is actually documented on the docstring of the variable `org-return-follows-link'. ... even if I should have known it... Thanks. Best regards, Seb -- Sebastien Vauban
Re: [O] [PATCH] Center currently clocked headline to top of screen
Hi Carsten, Carsten Dominik wrote: On Sep 2, 2013, at 4:02 PM, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: El Thu, 22 Aug 2013 10:36:00 +0200 Sebastien Vauban va escriure: When jumping to the currently clocked headline (via `C-c C-x C-j'), it seems (to me) more logical to recenter that headline at the top of the screen (vs at the center of the screen, that is the current behavior). Seeing a bit of context is nice; maybe putting it at line 2 or 3 is better than at the top and I think it is better than centered. It could also be configurable. Yup, I have made this a (recenter 2). Non-configurable until arrival of more votes. I'd vote for (recenter 0), as: - I generally only clock on projects, and - I'm not interested by seeing the last action(s) of the previous project, when jumping to the currently clocking task. May I submit a patch with a configurable variable? Yes. Here it is! Best regards, Seb From: Sebastien Vauban sva-n...@mygooglest.com Date: Tue, 10 Sep 2013 11:52:51 +0200 Subject: [PATCH] Add option with number of context lines before currently clocked-in entry * org-clock.el (org-clock-goto-before-context): New option. (org-clock-goto): Use that option. --- lisp/org-clock.el |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/lisp/org-clock.el b/lisp/org-clock.el index 524dbf1..c39b589 100644 --- a/lisp/org-clock.el +++ b/lisp/org-clock.el @@ -1668,6 +1668,9 @@ Optional argument N tells to change by that many units. (message Clock canceled) (run-hooks 'org-clock-cancel-hook)) +(defvar org-clock-goto-before-context 2 + Number of lines of context to display before currently clocked-in entry.) + ;;;###autoload (defun org-clock-goto (optional select) Go to the currently clocked-in entry, or to the most recently clocked one. @@ -1691,7 +1694,7 @@ With prefix arg SELECT, offer recently clocked tasks for selection. (org-show-entry) (org-back-to-heading t) (org-cycle-hide-drawers 'children) -(recenter 2) +(recenter org-clock-goto-before-context) (org-reveal) (if recent (message No running clock, this is the most recently clocked task)) -- 1.7.9
[O] [PATCH] Allow caption and header text in clocktable dblocks
Hello Francesco, Francesco Pizzolante wrote: Nicolas Goaziou wrote: Francesco Pizzolante f...@missioncriticalit.com writes: But if I try what you suggest and move the #+ATTR_LATEX line inside the dynamic block (after the #+BEGIN: clocktable and just before the generated table), then this line gets lost as soon as the dynamic block is regenerated, which is not what I expect. Then some attribute could be added to dynamic block arguments in order to re-create the ATTR_LATEX keyword each time. IIRC we did that for #+CAPTION some months ago. It shouldn't be difficult to do it for this one. I've seen, indeed (thanks!), that there was a :header option, which you can use to add free text in front of the dynamic table. #+BEGIN: clocktable :maxlevel 2 :scope (clock-file.org) :block 2013-08 :fileskip0 t :lang en :header #+ATTR_LaTeX: :environment longtabu :align lXrr\n #+ATTR_LaTeX: :environment longtabu :align lXrr | File | Headline| Time | | |+-++--| || ALL Total time | 1:44 | | |+-++--| | clock-file.org | File time | *1:44* | | || Projet management | 1:44 | | || \__ Writing reports || 1:44 | #+END: Though, doing so, there is no CAPTION anymore... Maybe adding a :header should not strip the autogenerated caption? I need that as well -- here is the patch (if Nicolas is OK with it)... Best regards, Seb From: Sebastien Vauban sva-n...@mygooglest.com Date: Tue, 10 Sep 2013 12:15:26 +0200 Subject: [PATCH] Allow caption and header text in clocktable dblocks * org-clock.el (org-clocktable-write-default): Allow caption and header text in clocktable dblocks. --- lisp/org-clock.el | 26 ++ 1 files changed, 14 insertions(+), 12 deletions(-) diff --git a/lisp/org-clock.el b/lisp/org-clock.el index c39b589..27fba2a 100644 --- a/lisp/org-clock.el +++ b/lisp/org-clock.el @@ -2388,19 +2388,21 @@ from the dynamic block definition. ;; Now we need to output this tsuff (goto-char ipos) -;; Insert the text *before* the actual table +;; Insert the caption (insert-before-markers - (or header -;; Format the standard header -(concat - #+CAPTION: - (nth 9 lwords) [ - (substring - (format-time-string (cdr org-time-stamp-formats)) - 1 -1) - ] - (if block (concat , for range-text .) ) - \n))) + ;; Format the standard header + (concat + #+CAPTION: + (nth 9 lwords) [ + (substring + (format-time-string (cdr org-time-stamp-formats)) + 1 -1) + ] + (if block (concat , for range-text .) ) + \n)) + +;; Insert the header text *before* the actual table +(insert-before-markers header) ;; Insert the narrowing line (when (and narrow (integerp narrow) (not narrow-cut-p)) -- 1.7.9
[O] [BUG] Re: How to trigger the clockcheck in an agenda view.
Hi Nicolas, Nicolas Girard wrote: 2013/8/5 Sebastien Vauban sva-n...@mygooglest.com: Except the above, I definitely don't understand why it wouldn't work for you. Can you reproduce the problem with a minimal Emacs config file (adding the require of `org' and `org-agenda' before)? I think I understand why Rainer has a problem. According to the docstring from `org-agenda-custom-commands', there are two acceptable syntaxes for defining a command: - the simple one : (key desc type match settings files) - and the complex or composite one : (key desc (cmd1 cmd2 ...) general-settings-for-whole-set files). Now, the following code defines two commands, who are functionally identical, but syntactically different. The first one uses the simple syntax, and the second one, the complex syntax. If you evaluate the code and trigger the agenda, you'll see that the first command *doesn't* work as expected, while the second works. I confirm that I can reproduce the bug you've spotted. Great finding you've done there... This is the kind of obvious thing very difficult to spot... And, in fact, the extract I sent early of August wasn't working for me. Well, the same version from a multi-block agenda view. This completely corroborates your sayings... (I just borrowed your scissors to delimit my code, hope you don't mind ;-) ) These are not mine: just the default ones when pressing `C-c M-m' when composing a message in Emacs! (setq org-agenda-custom-commands nil) (setq org-agenda-custom-commands (append org-agenda-custom-commands '( (G Good: Clock Review ((agenda ((org-agenda-show-log 'clockcheck) (org-agenda-clockreport-mode t) (B Bad: Clock Review agenda ((org-agenda-show-log 'clockcheck) (org-agenda-clockreport-mode t)) Indeed, while G is good, B is not firing up the clock check as expected. Best regards, Seb -- Sebastien Vauban
[O] [BUG?] Duplicate agenda entries when enabling archives-mode
Hello, If you use the following block of code, you'll see that all your entries are duplicated. For a clock review, this is much worse, as Org will warn about clocking overlaps everywhere... (because multiple entries, then, happened at the same time). --8---cut here---start-8--- (setq org-agenda-custom-commands nil) (add-to-list 'org-agenda-custom-commands '(C Clock Review ((agenda ( (org-agenda-archives-mode t) ;; (org-agenda-clockreport-mode t) (org-agenda-overriding-header Clocking Review) (org-agenda-show-log 'clockcheck) (org-agenda-span 'day))) t))) --8---cut here---end---8--- Putting the `archives-mode' line in comments does solve the problem. Best regards, Seb -- Sebastien Vauban
[O] [BUG] Re: Troubles with custom agenda commands
Hi Bastien, Sebastien Vauban wrote: Bastien wrote: Sebastien Vauban writes: When getting to the agenda dispatcher (`C-c a'), I see: S Summary Review: set of 3 commands while I only have... 2 commands (`agenda' and `todo'). Why? This is a bug, fixed. Thanks for spotting this! Tested. Confirmed OK. The above problem is back with the following configuration (tested with emacs -Q): --8---cut here---start-8--- (add-to-list 'org-agenda-custom-commands '(C Clock Review ((agenda ((org-agenda-clockreport-mode t) (org-agenda-overriding-header Clocking Review) (org-agenda-show-log 'clockcheck) (org-agenda-span 'day))) t))) --8---cut here---end---8--- Org writes: --8---cut here---start-8--- C Clock Review : set of 2 commands n Agenda and all TODO's: set of 2 commands --8---cut here---end---8--- while there is only 1 command to be run (the agenda view)!? Note, surprisingly, 2 extra spaces before the :, while they're not in the customized header string... Best regards, Seb -- Sebastien Vauban
Re: [O] [BUG] Re: Troubles with custom agenda commands
Hi Bastien, Sebastien Vauban wrote: Sebastien Vauban wrote: Bastien wrote: Sebastien Vauban writes: When getting to the agenda dispatcher (`C-c a'), I see: S Summary Review: set of 3 commands while I only have... 2 commands (`agenda' and `todo'). Why? This is a bug, fixed. Thanks for spotting this! Tested. Confirmed OK. The above problem is back with the following configuration (tested with emacs -Q): (add-to-list 'org-agenda-custom-commands '(C Clock Review ((agenda ((org-agenda-clockreport-mode t) (org-agenda-overriding-header Clocking Review) (org-agenda-show-log 'clockcheck) (org-agenda-span 'day))) t))) Org writes: C Clock Review : set of 2 commands n Agenda and all TODO's: set of 2 commands while there is only 1 command to be run (the agenda view)!? Please IGNORE IT! This bug is due to a faulty placement of the parenthesis. It should have been: (add-to-list 'org-agenda-custom-commands '(C Clock Review ((agenda ((org-agenda-clockreport-mode t) (org-agenda-overriding-header Clocking Review) (org-agenda-show-log 'clockcheck) (org-agenda-span 'day) t) ^^ Sorry for this false alarm. Note, surprisingly, 2 extra spaces before the :, while they're not in the customized header string... Best regards, Seb -- Sebastien Vauban
[O] [BUG] Colored tags generate an error when C-x C-w'ing the agenda
Hello, If you have colors for tags: --8---cut here---start-8--- ;; faces for specific tags (setq org-tag-faces '((home . (:slant italic :foreground #5C88D3 :background #BBDDFF)) (work . (:slant italic :foreground #5F7C43 :background #C1D996 --8---cut here---end---8--- you can't export the agenda views anymore; they all generate the following error: #+begin_src text Debugger entered--Lisp error: (wrong-type-argument listp #5C88D3) ps-face-attributes(#5C88D3) ps-face-attribute-list((:slant italic :foreground #5C88D3 :background #BBDDFF)) ps-plot-with-face(459 463 (:slant italic :foreground #5C88D3 :background #BBDDFF)) ps-generate-postscript-with-faces1(1 6850) ps-generate-postscript-with-faces(1 6850) ps-generate(#buffer Agenda View 1 6850 ps-generate-postscript-with-faces) ps-spool-with-faces(1 6850 nil) ps-print-with-faces(1 6850 ~/agenda.ps) ps-print-buffer-with-faces(~/agenda.ps) ... command-execute(org-agenda-write) #+end_src Best regards, Seb -- Sebastien Vauban
[O] [wish, detail] Resume ordered lists
Hello, Currently, ordered list items may be (re-)started with a different value (e.g., 20), by writing the item with `[@20]'. A nice-to-have feature would be the ability to resume a list at the previous value + 1, such as: ╭ │ 1. This │ 2. That │ │ Some intermediate paragraph. │ │ 3. [@resume] Those ╰ That would allow for more efficiency when adding or deleting items from the previous list. Best regards, Seb -- Sebastien Vauban
Re: [O] Outline cycling does not preserve point's position
Hello Nicolas, Nicolas Goaziou wrote: Some points are still to be discussed: 1. What to do on node properties? I would opt for `forward-paragraph', to have something different than `next-line'. Otherwise, `C-down' and `down' would simply do the same thing. Not forbidden, but seems useless... 2. What to do on source blocks? There, I'd simply clone what happens in the real source code buffers. I've tested `C-down' in Emacs Lisp, Shell and C++ modes. In all of them, `C-down' runs the command `forward-paragraph'. So, this seems to be the obvious choice to me. Best regards, Seb -- Sebastien Vauban
[O] How to avoid time part in date comparisons?
Hello, Suppose you want to make a list of tasks you will have to do tomorrow. The most logical expression would be SCHEDULED = tomorrow: --8---cut here---start-8--- (add-to-list 'org-agenda-custom-commands '(1 Tomorrow tags-todo SCHEDULED=\+1d\ ((org-agenda-overriding-header Tomorrow))) t) --8---cut here---end---8--- However, you'll lose timed tasks such as: --8---cut here---start-8--- ** TODO Check weekend hours at the gym DEADLINE: 2013-09-13 Fri 12:30 --8---cut here---end---8--- Hence, you need to write a more complex expression, like: --8---cut here---start-8--- (add-to-list 'org-agenda-custom-commands '(2 Tomorrow tags-todo SCHEDULED=\+1d\+SCHEDULED\+2d\ ((org-agenda-overriding-header Tomorrow (full t) --8---cut here---end---8--- Is there a better way to write such a basic request? Best regards, Seb -- Sebastien Vauban
Re: [O] How to avoid time part in date comparisons?
Sebastien Vauban wrote: Suppose you want to make a list of tasks you will have to do tomorrow. (add-to-list 'org-agenda-custom-commands '(1 Tomorrow tags-todo SCHEDULED=\+1d\ ((org-agenda-overriding-header Tomorrow))) t) However, you'll lose timed tasks. Hence, you need to write a more complex expression, like: (add-to-list 'org-agenda-custom-commands '(2 Tomorrow tags-todo SCHEDULED=\+1d\+SCHEDULED\+2d\ ((org-agenda-overriding-header Tomorrow (full t) Is there a better way to write such a basic request? BTW, it's the same for Today, for which we *must* replace the intuitive expression --8---cut here---start-8--- tags-todo SCHEDULED=\today\ --8---cut here---end---8--- by --8---cut here---start-8--- tags-todo SCHEDULED\tomorrow\ --8---cut here---end---8--- if we want to see all today's tasks (including the ones with a time component)... Best regards, Seb -- Sebastien Vauban
[O] [BUG] `org-agenda-sorting-strategy' does not work in `tags-todo'
Hello, The following agenda view is supposed to display the tasks by ascending _DEADLINE timestamp_. #+begin_src emacs-lisp (add-to-list 'org-agenda-custom-commands '(B Today tags-todo DEADLINE=\today\ ((org-agenda-overriding-header Today) (org-agenda-sorting-strategy '(deadline-up t) #+end_src However, as you can see with the following ECM: #+begin_src org * Health :PROPERTIES: :CATEGORY: Health :END: ** TODO 3Do jogging DEADLINE: 2013-09-09 Mon ** TODO 2Check weekend hours at the gym DEADLINE: 2013-09-08 Sun * Personal :PROPERTIES: :CATEGORY: Personal :END: ** TODO 4Mail package to Susan DEADLINE: 2013-09-12 Thu * Shopping :PROPERTIES: :CATEGORY: Shopping :END: ** TODO 1Buy dog food DEADLINE: 2013-09-07 Sat #+end_src it sorts the list by _category_, instead! --8---cut here---start-8--- Today (4) Health: TODO 3Do jogging Health: TODO 2Check weekend hours at the gym Personal: TODO 4Mail package to Susan Shopping: TODO 1Buy dog food --8---cut here---end---8--- The same sorting criteria, applied on an `agenda' view, does work. #+begin_src emacs-lisp (add-to-list 'org-agenda-custom-commands '(G Agenda deadline-up agenda ((org-agenda-span 'day) (org-agenda-time-grid nil) (org-agenda-sorting-strategy '(deadline-up t) #+end_src --8---cut here---start-8--- Calendar for today 2013-09-12 Thu 5 d ago TODO 1Buy dog food 4 d ago TODO 2Check weekend hours at the gym 3 d ago TODO 3Do jogging Deadline TODO 4Mail package to Susan --8---cut here---end---8--- Best regards, Seb -- Sebastien Vauban
Re: [O] Visibility cycling for headlines with a specific tag ?
Hi Martin, Martin Leduc wrote: I am currently taking a lot of notes in an org file containing figures, equations, code snippets and text. In my project tree, I have several nodes containing supplementary material and code that will not be part of my final report exported as a LaTeX pdf. These nodes are tagged as :noexport to avoid exporting. However, when editing the buffer, I would like to hide all such parts in order to focus on the important ones. Is there a way to whether: 1) folding (or cycling) all headlines of a specific tag in one key action 2) prevent these tagged headlines to unfold (unless I specifically want to by hitting tab when the cursor is on the headline), by some kind of locking process ? For example, by tagging with :locked ? I don't know whether than can solve your problem, but you may try using the ARCHIVE tag. I know, this is not semantically right; but you could already try if it meets your requirements. Best regards, Seb -- Sebastien Vauban
Re: [O] [export] Should sidewaystable option automatically add rotating package?
Hello, Nicolas Goaziou wrote: My point is: if wrapfig is there, rotating should accompany it, or both should be removed from the variable. Also, there's no reason for longtable to be included. Your analysis makes a lot of sense (somehow looking at what LaTeX knowledge the user has, if he writes `longtabu' in his document). However, I am undecided about doing it the way you propose here above, and having all of them included by default. Hence, I'll be happy with whichever proposition you apply. Best regards, Seb -- Sebastien Vauban
[O] [PATCH] Recenter around #+begin_src when moving to previous/next code block
Hello, When moving with C-c C-v C-n (or p) from one code block to the next (or previous), it's much better if the code block gets centered (vs hidden, forcing the user to scroll down, as it currently is). This is the purpose of this easy patch. Best regards, Seb From: Sebastien Vauban sva-n...@mygooglest.com Date: Fri, 13 Sep 2013 11:56:56 +0200 Subject: [PATCH] Recenter around #+begin_src when moving to previous/next code block * ob-core.el (org-babel-next-src-block): Recenter after jumping to next code block. (org-babel-previous-src-block): Recenter after jumping to previous code block. --- lisp/ob-core.el |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/lisp/ob-core.el b/lisp/ob-core.el index d57806b..fd4b1bd 100644 --- a/lisp/ob-core.el +++ b/lisp/ob-core.el @@ -1748,14 +1748,16 @@ buffer or nil if no such result exists. Jump to the next source block. With optional prefix argument ARG, jump forward ARG many source blocks. (interactive p) - (org-next-block arg nil org-babel-src-block-regexp)) + (org-next-block arg nil org-babel-src-block-regexp) + (recenter)) ;;;###autoload (defun org-babel-previous-src-block (optional arg) Jump to the previous source block. With optional prefix argument ARG, jump backward ARG many source blocks. (interactive p) - (org-previous-block arg org-babel-src-block-regexp)) + (org-previous-block arg org-babel-src-block-regexp) + (recenter)) (defvar org-babel-load-languages) -- 1.7.9
Re: [O] [PATCH] Recenter around #+begin_src when moving to previous/next code block
Hi Carsten, Carsten Dominik wrote: When moving with C-c C-v C-n (or p) from one code block to the next (or previous), it's much better if the code block gets centered (vs hidden, forcing the user to scroll down, as it currently is). This is the purpose of this easy patch. I don't think this patch is the right thing - is feels different from standard Emacs behavior. I'm not sure to understand which Emacs behavior we would deviate from? This is a jump, and it'd be better located at a readable place. Without it, you're forced to follow 90% of your jumps by a `C-l'... And isn't it very similar to the patch I sent earlier this week regarding the recenter after the jump with `C-c C-x C-j'? I'd more easily understand that both are either accepted or rejected, but not a mixed case. Anyway, I'm not bothered if it's not in Org, I can simply defadvice the functions (the `after' case). So I respect your decision, even if it puzzles me: it's just that having to manually recenter after almost all jumps do not feel like a right behavior of Org to me, for the beginners who can't make such defadvice on their own. Best regards, Seb -- Sebastien Vauban
Re: [O] no fontification of #+BEGIN_LaTeX blocks
Julien Cubizolles wrote: org-src-fontify-natively doesn't fontify quoted LaTeX code like #+BEGIN_LaTeX #+END_LaTeX the same as it does for LaTeX src blocks like #+BEGIN_SRC latex #+END_SRC Why is that, and is there a way to get fontification for both ? Yes, you have different faces: `org-block-background' and face `org-block'. It's always better to have more than not enough. Up to you to customize them so that they look the same, if that's what you want. PS- Use `C-u C-x =' with point where you want to know which are the faces in question. Then, M-x customize-face... Best regards, Seb -- Sebastien Vauban
Re: [O] org-schedule vs org-time-stamp
Paul Rudin, Paul Rudin wrote: I'm not clear on how these two are intended to be used. The former prefixes the timestamp with SCHEDULED: but I'm not sure what practical consequences this has. Items appear in the agenda either way. You should absolutely read the chapter 8 (Dates and Times) of the Org manual. In summary, active timestamps only will appear on the day of the timestamp. It's good for meetings or birthdays or events that naturally only occur at a certain day. SCHEDULED timestamps indicate when you want to start working on a task. Such items will appear every day, on and on, in your agenda until you mark them done. Best regards, Seb -- Sebastien Vauban
Re: [O] [BUG] (wrong-type-argument wholenump nil)
Andrew, Andrew Hyatt wrote: On Wed, Jul 24, 2013 at 9:34 AM, Sebastien Vauban wrote: With a *minimal config file* and Org-mode version 8.0.6 (release_8.0.6-357-gf00d75) @ there is a Lisp error generated when trying to split a block of code into two pieces through `C-c C-v C-d' (org-babel-demarcate-block). Debugger entered--Lisp error: (wrong-type-argument wholenump nil) make-string(nil 32) (let ((lang (nth 0 info)) (indent (make-string (nth 5 info) 32))) ...) ... org-babel-demarcate-block(nil) FYI, it works in an old Org version (such as 7.9.2+, bundled with GNU Emacs 24.2.91.1). I see this as well with org-indent-line-to, and org-clock-in. org-clock-in calls org-indent-line-to with a negative number, and org-indent-line-to calls indent-line-to with a negative number, which calls move-to-column with a negative number. But move-to-column doesn't allow negative numbers. I'm glad someone else does get it as well... I'm not crazy! Hopefull, this does not appear anymore with Org-mode version 8.1.1 (release_8.1.1-13-ga1f9a1). Best regards, Seb -- Sebastien Vauban
Re: [O] no fontification of #+BEGIN_LaTeX blocks
Julien Cubizolles wrote: Sebastien Vauban sva-n...@mygooglest.com writes: Julien Cubizolles wrote: org-src-fontify-natively doesn't fontify quoted LaTeX code like #+BEGIN_LaTeX #+END_LaTeX the same as it does for LaTeX src blocks like #+BEGIN_SRC latex #+END_SRC Why is that, and is there a way to get fontification for both ? Yes, you have different faces: `org-block-background' and face `org-block'. Do you mean that getting the BEGIN_LaTeX blocks to use org-block-background would give all the pretty colors I have in BEGIN_SRC latex ? No, you could just have the same color as the default (unfontified) from source blocks. I mean: fontified source blocks add extra text properties, such as comment, string, type, etc. You could have the same default one, with the same background color, if that's what annoys you. But I'm not really sure to understand what you try to achieve. Could you be more explicit? Could you give a minimal example file? PS- Use `C-u C-x =' with point where you want to know which are the faces in question. Then, M-x customize-face... customize-face doesn't seem to offer me a way to choose a particular fontification scheme. I must be missing something here. With customize-face, you don't choose a color theme (that's more or less the right wording; even called custom theme now in Emacs 24, but more generic): you make your own color theme... To choose one color theme, you must first tell us whether you're on Emacs 23 or 24. Looking at http://orgmode.org/worg/color-themes-screenshot.html and at http://orgmode.org/worg/org-color-themes.html could help you as well implement the right choice for you. Best regards, Seb -- Sebastien Vauban
Re: [O] no fontification of #+BEGIN_LaTeX blocks
Hi Julien,
Julien Cubizolles wrote:
But I'm not really sure to understand what you try to achieve. Could you be
more explicit? Could you give a minimal example file?
In the following, begin, center, and braces get different colors
#+BEGIN_SRC latex
\begin{center}
\includegraphics[width=0.5\textwidth]{figures/fresnel}
\end{center}
#+END_SRC
Here everything is the same color, not very good for readability.
#+BEGIN_LaTeX
\begin{center}
\includegraphics[width=0.5\textwidth]{figures/fresnel}
\end{center}
#+END_LaTeX
Since I use them for pieces of code to be exported to Beamer, the latex
block is easier to use (no export options to take care of) but less
readable. Anyway I can edit both with org-edit-src-code, with
fontification, and I'm happy with that so far.
I perfectly understand your need, now: to have *syntax highlighting* of
everything in a #+BEGIN/END_LaTeX block (the same would be true for HTML or
...).
This is something I'd like to get as well, in fact!
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [Babel] Buffer-wide properties ignored ...
Hi Aditya, aditya siram wrote: It appears as though buffer wide properties are ignored when tangling source blocks. This is easily reproducible by add a `#+PROPERTY: :padlines no` to the top of the file and tangling something. The source has padlines. I tried variations on including `#+PROPERTY: padlines no` and `#+PROPERTY: header-args: padlines-no` with the same result. Could you send an ECM [1], please? Best regards, Seb [1] Exemple Complet Minimal, or Minimal Working Example. -- Sebastien Vauban
Re: [O] [Babel] Padlines
aditya siram wrote: What's the rationale for having padlines by default in tangled source? It generates more readable source-code, as blocks are not glued next to each other. It generates wrong programs for languages where whitespace is significant (Haskell) and, for me, doesn't noticeably improve the look of the tangled file in cases where it isn't. Though, I admit that padlines yes should be smarter and add only one line *between* blocks, but NOT before the first one! Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] Buffer-wide properties ignored ...
aditya siram wrote: Here's the org-file with padlines set to no up top: #+PROPERTY: :padlines no ^ Try without the :... * Headline #+BEGIN_SRC c :tangle /tmp/padlines-test.c :comments link hello world #+END_SRC And the tangle file: /* [[file:/tmp/padlines-test.org::*Headline][Headline:1]] */ hello world /* Headline:1 ends here */ You see why an ECM is sometimes the best way to find a problem... Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] Buffer-wide properties ignored ...
aditya siram wrote: Sebastien Vauban sva-n...@mygooglest.comwrote: aditya siram wrote: Here's the org-file with padlines set to no up top: #+PROPERTY: :padlines no ^ Try without the :... ... and without the s to padlines... So, the correct line is: --8---cut here---start-8--- #+PROPERTY: padline no --8---cut here---end---8--- * Headline #+BEGIN_SRC c :tangle /tmp/padlines-test.c :comments link hello world #+END_SRC I tried `#+PROPERTY :padlines no` , `#+PROPERTY: padlines no` and `#+PROPERTY padlines no` all with the same result. Don't forget as well that you must do a C-c C-c on the options block after every change you make to one of them. That's annoying, because we always forget it, but that's necessary for your change to be applied! You see why an ECM is sometimes the best way to find a problem... Same conclusion, except I should have run your ECM! ;-) Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] Padlines
Hi Eric, Eric Schulte wrote: aditya siram aditya.si...@gmail.com writes: What's the rationale for having padlines by default in tangled source? It generates wrong programs for languages where whitespace is significant (Haskell) and, for me, doesn't noticeably improve the look of the tangled file in cases where it isn't. It is possible to change the value of default header arguments on a per-language basis because e.g., while (:padlines yes) may make sense for sh, it probably doesn't for Haskell. Could it be possible that :padline yes does not insert a blank line in front of the very first block, only *between* all blocks? Best regards, Seb -- Sebastien Vauban
Re: [O] [OT] mail followup to (was Re: M-x fill-region equivalent for lists?)
Hi Eric, Eric S Fraga wrote: John Hendy jw.he...@gmail.com writes: Got it. And now that you say that, *that's* what puzzled me when sending it out: I got an email back to myself. So *that* I still do find weird. If I send an email in response to your email on the list, why would I want it sent directly to myself? Is that just because if someone then responds to *that* email, it ensures that I get a direct email as well as the one to the list? Yes, and it does seem to have the annoying side effect that if *you* reply, you might also get a copy. This wouldn't happen to me as I think that gnus filters out any me addresses in doing a followup. Yes, you must have something along that line: --8---cut here---start-8--- ;; addresses to prune (disable `Cc:' to myself) when doing wide replies (setq message-dont-reply-to-names gnus-ignored-from-addresses) --8---cut here---end---8--- in your .gnus. Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] Padlines
Hi Eric,
Eric Schulte wrote:
Sebastien Vauban sva-n...@mygooglest.com writes:
Eric Schulte wrote:
aditya siram aditya.si...@gmail.com writes:
What's the rationale for having padlines by default in tangled source? It
generates wrong programs for languages where whitespace is significant
(Haskell) and, for me, doesn't noticeably improve the look of the tangled
file in cases where it isn't.
It is possible to change the value of default header arguments on a
per-language basis because e.g., while (:padlines yes) may make sense
for sh, it probably doesn't for Haskell.
Could it be possible that :padline yes does not insert a blank line in
front
of the very first block, only *between* all blocks?
I just pushed up a commit which implements this behavior. See the
attached file for an example.
#+Title: Examples with the new padline behavior
#+headers: :tangle pad-yes-with-shebang.sed
#+headers: :shebang #!/bin/sed -f
#+headers: :padline yes
#+begin_src sed
1 {N;s/\n//1}
#+end_src
#+headers: :tangle pad-no-with-shebang.sed
#+headers: :shebang #!/bin/sed -f
#+headers: :padline no
#+begin_src sed
1 {N;s/\n//1}
#+end_src
#+headers: :tangle pad-yes-without-shebang.sed
#+headers: :padline yes
#+begin_src sed
1 {N;s/\n//1}
#+end_src
#+headers: :tangle pad-no-without-shebang.sed
#+headers: :padline no
#+begin_src sed
1 {N;s/\n//1}
#+end_src
1. Tangle the above four blocks with =C-c C-v t=.
2. Execute the following code block to view the contents of the
resulting sed files.
#+begin_src sh :results scalar
head pad*sed
#+end_src
#+RESULTS:
: == padline-example.sed ==
: #!/bin/sed -f
:
: 1 {N;s/\n//1}
:
: == pad-no-without-shebang.sed ==
: 1 {N;s/\n//1}
:
: == pad-no-with-shebang.sed ==
: #!/bin/sed -f
: 1 {N;s/\n//1}
:
: == pad-yes-without-shebang.sed ==
: 1 {N;s/\n//1}
:
: == pad-yes-with-shebang.sed ==
: #!/bin/sed -f
:
: 1 {N;s/\n//1}
That seems perfect, and solves corner-cases I wouldn't have thought of (with
shebang). Thanks a lot!
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Strange Behaviour while rescheduling date
Hello, G. Martin Butz wrote: In case I try to reschedule a date from the weekly agenda view I get the following backtrace; I am under the impression, that this seems not to be the bug, which I have tried to describe in the last message, but at least it shows, that something is wrong (with my setup/emacs/org?) Debugger entered--Lisp error: (error Before first headline at position 1 in buffer date.org) FYI, I also experience that (annoying) message now and then, but I never understood which conditions did make it appear -- and, no, it's not an advised split-window in my case ;-(. Best regards, Seb -- Sebastien Vauban
Re: [O] C-u C-u C-c ! inserts an active timestamp.
Hello Suvayu, Suvayu Ali wrote: On Mon, Sep 23, 2013 at 10:51:33AM +0200, Nicolas Richard wrote: Carsten Dominik carsten.domi...@gmail.com writes: Applied I noticed that the whole mail went into the commit msg (commit 12de6223dcd736c0958eca874def052b407ff5d1) ; did I send the patch incorrectly ? I used git format-patch then inserted the result at the end of the email I wrote. The page http://orgmode.org/worg/org-contribute.html#sec-4 is not very explicit about how to send the result of `git format-patch', but I seem to remember it was ok to just yank the content at the end of a mail. Is that a wrong assumption ? Simply attaching the patch as a text attachment should do fine I think. Though, many guidelines tell: Do not attach your patch, but submit it inline in the mail body, /unless you cannot teach your mailer to leave the formatting of the patch alone/. That allows for easy reviews... and easy comments (after every chunk of code). Best regards, Seb -- Sebastien Vauban
[O] [Babel] Lisp error: (wrong-type-argument listp hline)
Hello Eric, This ECM does generate an error, when run with :hlines yes. #+name: table | Key | Value | |-+---| | ABJ | 1 | | DEK | 2 | As you can see, there is one header and one horizontal line in the input table. * Set :hlines to no Adding `:hlines no' strips the horizontal line, but does keep the header. #+begin_src emacs-lisp :var data=table :results output :hlines no (mapc (lambda (item) (princ (format UPDATE dim SET val=%s WHERE code='%s'\n (nth 1 item) (nth 0 item data) #+end_src #+results: #+begin_example UPDATE dim SET val=Value WHERE code = 'Key' LINE NOT WANTED UPDATE dim SET val=1 WHERE code = 'ABJ' UPDATE dim SET val=2 WHERE code = 'DEK' #+end_example * Set :hlines to yes `:hlines yes' should leave the horizontal line, but generates an error. #+begin_src emacs-lisp :var data=table :results output :hlines yes (mapc (lambda (item) (princ (format UPDATE dim SET val=%s WHERE code='%s'\n (nth 1 item) (nth 0 item data) #+end_src --8---cut here---start-8--- Debugger entered--Lisp error: (wrong-type-argument listp hline) nth(1 hline) (format UPDATE dim SET val=%s WHERE code='%s'\n (nth 1 item) (nth 0 item)) (princ (format UPDATE dim SET val=%s WHERE code='%s'\n (nth 1 item) (nth 0 item))) (lambda (item) (princ (format UPDATE dim SET val=%s WHERE code='%s'\n (nth 1 item) (nth 0 item(hline) mapc((lambda (item) (princ (format UPDATE dim SET val=%s WHERE code='%s'\n (nth 1 item) (nth 0 item ((Key Value) hline (ABJ 1) (DEK 2))) ... call-interactively(org-self-insert-command nil nil) --8---cut here---end---8--- * Ignore the table header Finally, how am I then supposed to *ignore the header line*? By adding #+begin_src emacs-lisp (setq table (cdr table)) #+end_src ? Do I have to do that explicitly in my code block, or is there an option for telling that to Babel? Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] Lisp error: (wrong-type-argument listp hline)
Hi Eric, Eric Schulte wrote: I think you're confused by headers which are re-added by the colnames machinery. Blush! I mixed the two in my head, yes. See the following which returns scalar output avoiding any colnames post-processing. Why are you talking of *post* processing machinery for colnames? The documentation[1] says that :colnames no means no column name *pre* processing takes place. I may miss something important here. #+Property: results scalar #+name: table | Key | Value | |-+---| | ABJ | 1 | | DEK | 2 | #+begin_src emacs-lisp :var data=table :hlines no data #+end_src #+RESULTS: : ((Key Value) (ABJ 1) (DEK 2)) #+begin_src emacs-lisp :var data=table :hlines yes data #+end_src #+RESULTS: : ((Key Value) hline (ABJ 1) (DEK 2)) * Set :hlines to yes `:hlines yes' should leave the horizontal line, but generates an error. #+begin_src emacs-lisp :var data=table :results output :hlines yes (mapc (lambda (item) (princ (format UPDATE dim SET val=%s WHERE code='%s'\n (nth 1 item) (nth 0 item data) #+end_src This is not a babel error, this is an error in your code block body, which assumes that every element of `data' will be a list. The symbol `hline' is not a list. OK, that now becomes clear to me! Finally, how am I then supposed to *ignore the header line*? By adding #+begin_src emacs-lisp (setq table (cdr table)) #+end_src ? Do I have to do that explicitly in my code block, or is there an option for telling that to Babel? Use the :colnames processing to strip the headings. #+begin_src emacs-lisp :var data=table :colnames yes data #+end_src #+RESULTS: : ((ABJ 1) (DEK 2)) I always wondered why emacs-lisp is the _only_ language with :colnames no as its default. Is there a reason therefore? If no really good reason, could we suppress that? Best regards, Seb -- Sebastien Vauban [1] http://orgmode.org/org.html#colnames
Re: [O] [BUG] in Release 8.2 - editing code in indirect buffer
Hello Carsten, Carsten Dominik wrote: On 23.9.2013, at 09:40, Rainer M Krug rai...@krugs.de wrote: When starting to edit a code block via C-c ' everything works as expected and the code block is highlighted and an indirect buffer is opened. When I click into the highlighted block, I an send to the indirect buffer. This behavior changes, after saving with C-s, even when nothing has been edited: the area in the original org file looses its magic, and looks normal again and can also be edited! The indirect buffer stays functional and, upon close via C-c ' saves the changes into the original buffer and *overwrites* changes done in this block in the org document. This is a bug which is difficult to fix in all generality. What should really happen is that the text in the original buffer is made read-only. But so far this does not happen in our implementation (due to Dan Davison IIRC). The reason for this is that read-only text properties left by accident in a buffer are difficult to get rid of. There are many things the user could go back and screw up the original. That's why Org choses to protect with highlighting with an overlay. Note that this is not a protection against editing, but it is a visual warning. I never knew that your goal was to make the code block read-only in the Org buffer. Note that I would be really opposed to such a change. Editing code in the prose would really become a pain to me -- please know that I NEVER use the indirect buffer. I hope that we will block such a functionality, would the read-only feature become possible. However, what happens during saving is indeed a problem - the overlay gets lost (not really, it gets squeezed to zero by first removing the source code and then inserting the modified version). Could you please try this patch and test it to see if it is stable and does the right thing? Best regards, Seb -- Sebastien Vauban
Re: [O] [BUG] in Release 8.2 - editing code in indirect buffer
Hi Carsten, Carsten Dominik wrote: On 24.9.2013, at 18:17, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: On 23.9.2013, at 09:40, Rainer M Krug rai...@krugs.de wrote: When starting to edit a code block via C-c ' everything works as expected and the code block is highlighted and an indirect buffer is opened. When I click into the highlighted block, I an send to the indirect buffer. This behavior changes, after saving with C-s, even when nothing has been edited: the area in the original org file looses its magic, and looks normal again and can also be edited! The indirect buffer stays functional and, upon close via C-c ' saves the changes into the original buffer and *overwrites* changes done in this block in the org document. This is a bug which is difficult to fix in all generality. What should really happen is that the text in the original buffer is made read-only. But so far this does not happen in our implementation (due to Dan Davison IIRC). The reason for this is that read-only text properties left by accident in a buffer are difficult to get rid of. There are many things the user could go back and screw up the original. That's why Org choses to protect with highlighting with an overlay. Note that this is not a protection against editing, but it is a visual warning. I never knew that your goal was to make the code block read-only in the Org buffer. Note that I would be really opposed to such a change. Editing code in the prose would really become a pain to me -- please know that I NEVER use the indirect buffer. I only mean while there is a special buffer also editing this block! Pfff! I'm relieved -- I should have understood it ;-) Best regards, Seb -- Sebastien Vauban
Re: [O] Spurious exporting of text before first header
Hi François, François Pinard wrote: This is an old annoyance of the Org exporter, yet I'm not sure what would be its best resolution. Whenever I use :export: tags on headers within an Org file, I expect only those headers and their contents to be exported (to HTML in my case), and almost nothing else, which I then consider private. However, if I have text and other contents prior to the first header of a file, those contents are indeed exported, while I would prefer not. Of course, #+TITLE and some other directives prior to the first header should be honored for their effect. One might surely debate on the best way to handle #+INCLUDE directive. I wish the above comments might generate either a correction in Org, or an advice for me! :-) P.S. Some might suggest me that I avoid text prior to the first header. Surely, I have hundreds of Org files and for them all, have some personal conventions for their format and structure. For regularity reasons, I would much like to continue having private initial text. If you like text without initial heading in the exported file, but don't mind adding an heading in the Org buffer, you could add this: --8---cut here---start-8--- * Initial text :ignoreheading: --8---cut here---end---8--- and get what you want in the exported file. I thought that the filter to ignore the heading only was already in Org, but a quick test with the ASCII backend makes me thing it isn't. Anyway, you can find recent posts on this. Best regards, Seb -- Sebastien Vauban
Re: [O] Org mode issue tracker
Hi Carsten, Carsten Dominik wrote: we do not have an issue tracker for Org. However, if you have some time to help, the file with open issues that need attention can be found here: https://dl.dropboxusercontent.com/u/530458/org-tracker.html Note that I do not enter every issue into this file. Normally I wait and see if a report gets addressed on the mailing list, and only if that does not happen, than I make a note in this file. I think this keeps it more manageable for me - an official online bug tracker would probably quickly fill with many small things we can better handle on the list. If you feel that this is not going well enough and if I am missing important reports in this way, let me know and we will find a better solution. Some of these bugs still need confirmation by a second party, and patches are always welcome. If possible, reply in the original thread, while still mentioning the bug number in the above link. The other solution that I'd see would be using Emacs' own bug tracker (the `org' package is already known to them), if that's possible. Anyway, having the bugs in an Org file seems natural too! But shouldn't it, maybe, be in a Git project, so that other people can edit it? And choosing to have the `Assignee' (or `ASSIGNEE') property be the official Org way to delegate a task to someone would help? Regarding the list itself, if I may, I would add 3 problems (identified by the date and time it has been sent on the Org mailing list): 1. 20130315.1805: Background color reset for links and DONE headlines Allow to have more faces than just `org-headline-done' when `DONE' (`org-fontify-done-headline'). I looked at it, following Bastien's hints, but never could make it work. 2. 20130909.1657: Clocktable error with multiple source files from parent dir 3. 20130912.1455: `org-agenda-sorting-strategy' does not work in `tags-todo' The following agenda view is supposed to display the tasks by ascending DEADLINE timestamp. (add-to-list 'org-agenda-custom-commands '(B Today tags-todo DEADLINE=\today\ ((org-agenda-overriding-header Today) (org-agenda-sorting-strategy '(deadline-up t) it sorts the list by category, instead! OTOH, you can delegate the problem #24 to me. - 20130911.1448: Colored tags generate an error when C-x C-w'ing the agenda I'll try to debug and fix it myself. I'll come back if I don't succeed. Best regards, Seb -- Sebastien Vauban
Re: [O] Org mode issue tracker
Carsten Dominik wrote: On 25.9.2013, at 09:51, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: we do not have an issue tracker for Org. However, if you have some time to help, the file with open issues that need attention can be found here: https://dl.dropboxusercontent.com/u/530458/org-tracker.html Note that I do not enter every issue into this file. Normally I wait and see if a report gets addressed on the mailing list, and only if that does not happen, than I make a note in this file. I think this keeps it more manageable for me - an official online bug tracker would probably quickly fill with many small things we can better handle on the list. If you feel that this is not going well enough and if I am missing important reports in this way, let me know and we will find a better solution. Some of these bugs still need confirmation by a second party, and patches are always welcome. If possible, reply in the original thread, while still mentioning the bug number in the above link. The other solution that I'd see would be using Emacs' own bug tracker (the `org' package is already known to them), if that's possible. Anyway, having the bugs in an Org file seems natural too! But shouldn't it, maybe, be in a Git project, so that other people can edit it? And choosing to have the `Assignee' (or `ASSIGNEE') property be the official Org way to delegate a task to someone would help? Regarding the list itself, if I may, I would add 3 problems (identified by the date and time it has been sent on the Org mailing list): To make my life easier, cold you please provide gmane links? DONE ;-) See below. 1. 20130315.1805: Background color reset for links and DONE headlines Allow to have more faces than just `org-headline-done' when `DONE' (`org-fontify-done-headline'). I looked at it, following Bastien's hints, but never could make it work. http://permalink.gmane.org/gmane.emacs.orgmode/68552 2. 20130909.1657: Clocktable error with multiple source files from parent dir http://comments.gmane.org/gmane.emacs.orgmode/76207 3. 20130912.1455: `org-agenda-sorting-strategy' does not work in `tags-todo' The following agenda view is supposed to display the tasks by ascending DEADLINE timestamp. (add-to-list 'org-agenda-custom-commands '(B Today tags-todo DEADLINE=\today\ ((org-agenda-overriding-header Today) (org-agenda-sorting-strategy '(deadline-up t) it sorts the list by category, instead! http://permalink.gmane.org/gmane.emacs.orgmode/76347 OTOH, you can delegate the problem #24 to me. - 20130911.1448: Colored tags generate an error when C-x C-w'ing the agenda I'll try to debug and fix it myself. I'll come back if I don't succeed. OK, will do that, thank you. Best regards, Seb -- Sebastien Vauban
Re: [O] Org mode issue tracker
Hi Suvayu, Suvayu Ali wrote: On Wed, Sep 25, 2013 at 09:51:20AM +0200, Sebastien Vauban wrote: The other solution that I'd see would be using Emacs' own bug tracker (the `org' package is already known to them), if that's possible. Anyway, having the bugs in an Org file seems natural too! I think this is a great idea. A combination of an Org file (either public or private) and the Emacs bug tracker with Org package tags should be able to handle our needs. I see only one potential problem, is there an easy way to subscribe to only a specific package tag on the Emacs bug tracker? I imagine most contributors following Org bugs will not be interested in other Emacs bugs. I don't know. I guess this should be asked directly to them. Indeed, it'd be good to have a (virtual) newsgroup with only bugs related to `org', like what exists for Stack Overflow. Best regards, Seb -- Sebastien Vauban
Re: [O] Org mode issue tracker
Hi Michael, Michael Albinus wrote: Sebastien Vauban sva-n...@mygooglest.com The other solution that I'd see would be using Emacs' own bug tracker (the `org' package is already known to them), if that's possible. Anyway, having the bugs in an Org file seems natural too! I think this is a great idea. A combination of an Org file (either public or private) and the Emacs bug tracker with Org package tags should be able to handle our needs. I see only one potential problem, is there an easy way to subscribe to only a specific package tag on the Emacs bug tracker? I imagine most contributors following Org bugs will not be interested in other Emacs bugs. I don't know. I guess this should be asked directly to them. Indeed, it'd be good to have a (virtual) newsgroup with only bugs related to `org', like what exists for Stack Overflow. There is the debbugs package on ELPA. The frontend, debbugs-gnu, allows to filter for packages and tags. Try (debbugs-gnu '(serious important normal) '(org-mode)) I did not know. I must try it, for sure! It may be easier than the Web interface, which I find sometimes difficult to use (to find one's bug without remembering its ID). On my wannabe todo list is a package debbugs-org.el, which shows the entries as TODO items. If the org community decides to use debbugs as issue tracker, it would give me a push. I'd find that a promising feature... (I'm not so experienced with org-mode, so I would need at least some assistance how such a TODO item should look like) I don't think that's the problem ;-) Best regards, Seb -- Sebastien Vauban
Re: [O] Org mode issue tracker
Hi Carsten, Carsten Dominik wrote: I have moved the tracker to Worg, discarding the old tracker file that was at that location. http://orgmode.org/worg/org-issues.html Please note that the Show Org source button still shows the old Org file. Best regards, Seb -- Sebastien Vauban
[O] [PATCH] Display a count of items next to each list (or block)
Hello, In order to make Org much nicer to use, I felt we missed a count of items next to the lists (or blocks, for multi-block agenda views). Here is a patch to add this, depending on the new variable `org-agenda-display-count-of-items' (enabled by default). The count of items must be updated when you apply tag filtering on lists. The patch does it as well. Please enjoy (or be scared by the real number of items you have on your TODO lists)!! Best regards, Seb From: Sebastien Vauban sva-n...@mygooglest.com Date: Wed, 25 Sep 2013 21:56:01 +0200 Subject: [PATCH] Display a count of items next to each list (or block) * org-agenda.el (org-agenda-display-count-of-items): New variable. (org-agenda-insert-count-of-items) (org-agenda-count-visible-lines-block) (org-agenda-remove-filtered-count): New helper functions. (org-search-view, org-todo-list, org-tags-view): Add count of items. (org-agenda-filter-by-tag, org-agenda-filter-apply): Add or remove filtered count of items. (org-agenda-goto-block-beginning): Fix problems for position of point. (org-agenda-goto-next-block): New command. --- lisp/org-agenda.el | 89 --- 1 files changed, 83 insertions(+), 6 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index c48da91..336991f 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -4652,6 +4652,8 @@ in `org-agenda-text-search-extra-files'. (when rtnall (insert (org-agenda-finalize-entries rtnall 'search) \n)) (goto-char (point-min)) + (when org-agenda-display-count-of-items + (org-agenda-insert-count-of-items rtnall)) (or org-agenda-multi (org-agenda-fit-window-to-buffer)) (add-text-properties (point-min) (point-max) `(org-agenda-type search @@ -4663,6 +4665,46 @@ in `org-agenda-text-search-extra-files'. ;;; Agenda TODO list +(defvar org-agenda-display-count-of-items t + Display count of items next to each list.) + +(defun org-agenda-insert-count-of-items (count) + Insert count of items at the end of current line. + (save-excursion +(end-of-line) +(insert + (org-add-props (format (%s) (length rtnall)) nil + 'face 'org-agenda-block-count + +(defun org-agenda-count-visible-lines-block () + Count the number of items visible in the current block. + (interactive) + (let ((count 0)) +(save-excursion + (org-agenda-goto-block-beginning) + (while (equal (get-char-property (point) 'face) 'org-agenda-structure) ; header line(s) + (forward-visible-line 1)) + (while (or (equal (get-char-property (point) 'face) 'default) +(equal (get-char-property (point) 'type) tagsmatch) +(equal (get-char-property (point) 'type) todo)) ; entry line + (unless (get-char-property (point) 'invisible) + (setq count (1+ count))) + (forward-visible-line 1)) + count))) + +(defun org-agenda-remove-filtered-count () + Remove `X/' from filtered count string `(X/Y)'. + +Leaves point at total count. + (org-agenda-goto-block-beginning) + (while (not (equal (get-text-property (point) 'face) +'org-agenda-block-count)) +(forward-char)) + (forward-char); for ( + (when (looking-at [0-9]*/) +(kill-word 1) ; digits +(delete-char 1))) ; slash + (defun org-agenda-propertize-selected-todo-keywords (keywords) Use `org-todo-keyword-faces' for the selected todo KEYWORDS. (concat @@ -4753,6 +4795,8 @@ for a keyword. A numeric prefix directly selects the Nth keyword in (when rtnall (insert (org-agenda-finalize-entries rtnall 'todo) \n)) (goto-char (point-min)) + (when org-agenda-display-count-of-items + (org-agenda-insert-count-of-items rtnall)) (or org-agenda-multi (org-agenda-fit-window-to-buffer)) (add-text-properties (point-min) (point-max) `(org-agenda-type todo @@ -4840,6 +4884,8 @@ The prefix arg TODO-ONLY limits the search to TODO entries. (when rtnall (insert (org-agenda-finalize-entries rtnall 'tags) \n)) (goto-char (point-min)) + (when org-agenda-display-count-of-items + (org-agenda-insert-count-of-items rtnall)) (or org-agenda-multi (org-agenda-fit-window-to-buffer)) (add-text-properties (point-min) (point-max) `(org-agenda-type tags @@ -7448,6 +7494,13 @@ to switch to narrowing. (org-agenda-filter-show-all-tag) (when (get 'org-agenda-tag-filter :preset-filter) (org-agenda-filter-apply org-agenda-tag-filter 'tag)) + ;; count of items + (when org-agenda-display-count-of-items + (save-excursion + (goto-char (point-min)) ; beginning of first block + (while (or (equal (point) (point-min
Re: [O] Org mode issue tracker
regards, Seb -- Sebastien Vauban
Re: [O] Elpa color-theme with emacs24
Hi Rene, Rene wrote: I just tried out color-theme with emacs24. It seems the code on http://orgmode.org/worg/org-color-themes.html is not quite compatible with elpa packages. Here is what I used instead ... For the sake of completion, I think that, starting with Emacs 24, it's better to use their new custom theme mechanism, which is more general than the `color-theme' package (and offers the same services regarding color themes). Best regards, Seb -- Sebastien Vauban
Re: [O] #+END_SRC and recent pull
Noorul Islam Kamal Malmiyoda wrote: I pulled in latest changes from master and the following snippet is not getting tangled. #+begin_src emacs-lisp (message This is a test) #+end_src emacs-lisp Yes, the documentation has plain #+end_src, but somehow the above snippet was working earlier. Sending this mail out, just in case this is useful to someone else. Does the parser should really care about what is next to #+end_src ? I think so. You really should NOT put the language name at the end of the code block. Note that it shouldn't occur, would you use C-c C-v C-d to automatically convert a region in a code block. Neither with the easy templates, nor with custom YASnippets... Now, your code block alone, given above, can't be tangled, as there is no tangle directive. If it still does not work, please provide us with an ECM (Example Complete... and Minimal). Best regards, Seb -- Sebastien Vauban
Re: [O] [PATCH] Display a count of items next to each list (or block)
Hi Achim, Achim Gratz wrote: Am 25.09.2013 22:09, schrieb Sebastien Vauban: In order to make Org much nicer to use, I felt we missed a count of items next to the lists (or blocks, for multi-block agenda views). Here is a patch to add this, depending on the new variable `org-agenda-display-count-of-items' (enabled by default). Minor nit: to my ears item count sounds better than count of items. No problem (I'm no English native speaker, and I'm glad when I'm corrected, for improving myself). You then mean you'd rename the variable (and potentially other comments or names in the code)? To `org-agenda-display-item-count' or `org-agenda-display-items-count'? Best regards, Seb -- Sebastien Vauban
Re: [O] org-html-publish-to-html fails to recognize BEGIN_EXAMPLE/END_EXAMPLE blocks when exporting an example containing org-mode heading
Iannis Zannos, Iannis Zannos wrote: Hello, when trying to export as html an example which contains org-mode headings, the example is not quoted in mono-space as it should be. Example: *1. Failing example: * This is a test of publishing an example which contains org mode code in html: #+BEGIN_EXAMPLE * test #+END_EXAMPLE End of test. *2. Workaround: * This works as expected, but only because the * headline is indented by 1 character: This is a test of publishing an example which contains org mode code in html: #+BEGIN_EXAMPLE * test #+END_EXAMPLE End of test. The official solution (normally automatic[1] for Org code blocks) is to have a , inserted before the *; it is removed automatically when exporting. Best regards, Seb [1] Sometimes, the , is not automatically inserted for me, though, when TAB'ing. -- Sebastien Vauban
Re: [O] org-html-publish-to-html fails to recognize BEGIN_EXAMPLE/END_EXAMPLE blocks when exporting an example containing org-mode heading
Hi Iannis, Iannis Zannos wrote: On Thu, Sep 26, 2013 at 10:36 AM, Sebastien Vauban wrote: Iannis Zannos wrote: when trying to export as html an example which contains org-mode headings, the example is not quoted in mono-space as it should be. Example: *1. Failing example: * This is a test of publishing an example which contains org mode code in html: #+BEGIN_EXAMPLE * test #+END_EXAMPLE End of test. The official solution (normally automatic for Org code blocks) is to have a , inserted before the *; it is removed automatically when exporting. Thank you for the answer. It is clear now. Glad it helped! Perhaps the info manual of org-mode should be updated to indicate this? I would propose to do this in the following places in the manual: 11.3 Literal examples and perhaps also: 15.2 Easy Templates Would you mind providing a patch? Best regards, Seb -- Sebastien Vauban
[O] Convention for tags and properties
Hello, According to the manual [1]: - User-defined tags are written in lowercase; built-in tags with special meaning (such as ARCHIVE) are written with all capitals. - User-defined properties are capitalized; built-in properties with special meaning (such as PRIORITY) are written with all capitals. Following those conventions, I guess that: - The `crypt' tag should be renamed `CRYPT' - The `Effort' property should be renamed `EFFORT' Right? Best regards, Seb [1] http://orgmode.org/manual/Conventions.html -- Sebastien Vauban
Re: [O] Org mode issue tracker
Hi Suvayu, Suvayu Ali wrote: On Thu, Sep 26, 2013 at 09:29:10AM +0200, Sebastien Vauban wrote: (date . 1376383861) * TODO . :24.3: 2013-08-13 Tue I'd use the inactive version of the timestamp, that is (for Michael) [2013-08-13 Tue]. Doesn't the agenda show active timestamps only? Yes, but then I don't expect an event timestamp. Developers working on bugs might want to add the file as their agenda file. Absolutely, but the question comes down to: do they want to have their today's agenda filled with Org bugs? If they add `org-issues.org' to their `org-agenda-files', that's clear they wanna have the pendings bugs, etc. in *some* custom agenda views, but do they want that always in the default agenda? Adding the bug as an event timestamp will show it only on that day. Then, you don't see it anymore... If you want to see them, I'd propose to put a SCHEDULED type of timestamp, or a DEADLINE one, no? If you don't need the bugs in your default agenda view, then you can still put the date as an inactive timestamp to keep track of when the bug was submitted. Another way (to what you show) would be to add it under a property `Created' or `CreatedOn'... Best regards, Seb -- Sebastien Vauban
Re: [O] Spurious exporting of text before first header
Hello Nicolas, Nicolas Goaziou wrote: François Pinard pin...@iro.umontreal.ca writes: Nicolas Goaziou n.goaz...@gmail.com writes: François Pinard pin...@iro.umontreal.ca writes: The spirit behind :export: is [...] I agree, this is a misfeature. This should be fixed in master. Thank you for bringing it out. Thanks as well. :-) OTOH, this fix introduces another problem. What if a user wants to both use :export: tag and export text before first headline? An almost equivalent solution for him would be to add a headline before that text and append it an :export: tag. But in that case, he will get the additional headline in the output, which isn't desirable. He would have to add as well the tag :ignoreheading:, right, and would have no problem in the output? Though, he would see the headline in his Org buffer, what he'd dislike anyway (like François). IOW, it is easier to make that text disappear than to make it appear. IOW, even though the new behaviour is more logical, in the end, I'm not sure it is desirable. It's the old good versus best story. WDYT? At this stage, I don't have any preference for one over the other. Best regards, Seb -- Sebastien Vauban
[O] Invalid function: org-with-silent-modifications
Hello, Trying to provide batch Emacs/Org scripts to colleagues, I must ensure that they have Org 8. I wrote the following code so that users which have a default (Cygwin) Emacs 24.3.1 (with the default Org 7.9.3f) are proposed an upgrade through the `package' manager: --8---cut here---start-8--- (require 'package) (add-to-list 'package-archives '(org . http://orgmode.org/elpa/;)) (package-initialize) ;; version info (let ((org-dir (file-name-directory (locate-library org (message Org mode version %s (org @ %s) (org-version) org-dir)) (unless (string-match ^8 (org-version)) (message This version of Org mode is no longer supported) (if (yes-or-no-p (format Install package `%s'? 'org)) (ignore-errors (package-install 'org)) (setq debug-on-error nil) (error Please upgrade to 8 or later))) --8---cut here---end---8--- Problem experienced by colleagues: Invalid function: org-with-silent-modifications. Looking on the web, I find a post [1] where Bastien tells: When installing from ELPA, please do so from a fresh Emacs session where no Org function has been called. That wasn't the case in the above code, as I first had to call `org-version' to check for their current version, then install from ELPA if they don't have an Org 8... So, - Is there a way to unload Org before installing from ELPA? (= workaround) or better: - Is there a way to fix the problem? (= solution) Best regards, Seb [1] http://comments.gmane.org/gmane.emacs.orgmode/70880 -- Sebastien Vauban
Re: [O] Spurious exporting of text before first header
Hello Nicolas, Nicolas Goaziou wrote: Sebastien Vauban writes: Nicolas Goaziou wrote: What if a user wants to both use :export: tag and export text before first headline? An almost equivalent solution for him would be to add a headline before that text and append it an :export: tag. But in that case, he will get the additional headline in the output, which isn't desirable. He would have to add as well the tag :ignoreheading:, right, and would have no problem in the output? AFAIK, there is no such thing as a :ignoreheading: tag, at least not in the general case (Beamer export back-end has this feature, but it's a kludge). You may be referring to a personal export filter. Entirely possible: I've seen that while reading posts of this ML. Wouldn't it be worth to make such a filter officially present in Org, not only for Beamer? Best regards, Seb -- Sebastien Vauban
Re: [O] Spurious exporting of text before first header
Hello Nicolas, Nicolas Goaziou wrote: Sebastien Vauban writes: Wouldn't it be worth to make such a filter officially present in Org, not only for Beamer? Here we are. No it wouldn't. As I said, it's a kludge used as a workaround in Beamer-specific syntax because headlines, which are not blocks, can only be ended with another headline or the end of buffer. It's a specific solution for a local problem. I understand it *is* needed for Beamer. These do not usually generalize very well. For example, visibility cycling isn't related anymore to sections in export output: * H1 Section 1 * Ignore me! :ignoreheading: Section 1 (continued) * H2 Section 2 For me, visibility in the original Org buffer and sections in export output are orthogonal things. They don't impact each other. You can achieve the same (and, apparently, you already do) with a simple hook, without extending Org syntax. I _really_ think that's better. Yes, but that would solve the problem of having preliminary notes well or not exported in the output, depending on the fact you tag the section or not. That was what you said: there is no good solution between saying that preliminary notes will always be exported (as François wished) or never, if we can't customize that. And that would be not only for me: by putting a hook locally, my file won't produce the same output for all the other users. That was the point of having it in Org, as it seems it is a common request. That said, that's not something I need; so I don't mind that much. Best regards, Seb -- Sebastien Vauban
[O] [Bug?] Search string NOT interpreted as individual parts
Hello, I've observed, with the following minimal Org configuration, --8---cut here---start-8--- (require 'org) (define-key global-map (kbd C-c a) 'org-agenda) (setq org-agenda-files '(~/ecm.org)) ;; turn on individual word search (setq org-agenda-search-view-always-boolean t org-agenda-search-view-search-words-only t) ;; match part of a word (setq org-agenda-search-view-force-full-words nil) --8---cut here---end---8--- that the search string is: - WELL interpreted as individual parts for `C-c a s', but - NOT interpreted as individual parts for `C-c / /' inside the document itself You can see (on http://screencast.com/t/JkjcirV2DZ) that the following ECM document is found when searching `C-c a s histo entre RET'. --8---cut here---start-8--- #+TITLE: ECM #+LANGUAGE: fr * Opérations ** TODO Ajouter l'historique de l'entreprise La question Historique de l'entreprise bon ou pas ? est inutile dans le processus... Intégrer l'*historique PFI de l'entreprise* pour vérifier que ... ** TODO Historique ** TODO Entreprise --8---cut here---end---8--- But, when inside the document, - `C-c / / histo entre RET' FAILS - `C-c / / historique entreprise RET' FAILS - `C-c / / historique de l'entreprise RET' works - `C-c / / rique de l'entreprise RET' works That is: - (setq org-agenda-search-view-always-boolean t) is only honored for `C-c a s', NOT for `C-c / /' - (setq org-agenda-search-view-force-full-words nil) is honored for both `C-c a s' and `C-c / /' Best regards, Seb -- Sebastien Vauban
Re: [O] [BUG] Colored tags generate an error when C-x C-w'ing the agenda
Hi Carsten, Carsten Dominik wrote: On 11.9.2013, at 14:48, Sebastien Vauban sva-n...@mygooglest.com wrote: If you have colors for tags: --8---cut here---start-8--- ;; faces for specific tags (setq org-tag-faces '((home . (:slant italic :foreground #5C88D3 :background #BBDDFF)) (work . (:slant italic :foreground #5F7C43 :background #C1D996 --8---cut here---end---8--- you can't export the agenda views anymore; they all generate the following error: It does seem to work if you specify the faces like this (without the dot). (setq org-tag-faces '((home (:slant italic :foreground #5C88D3 :background #BBDDFF)) (work (:slant italic :foreground #5F7C43 :background #C1D996 Without the dot [1], I confirm that I can export both to HTML and PDF with no error. Though, in the PDF, these tags have a white background, not the one specified. This is a small annoyance... Since Emacs does display correctly with this way to specify a font, I'd say this is a bug in ps-print and should be reported to Emacs as such. ... which I'll report (with your analysis) to Emacs. Thanks for your help! Best regards, Seb [1] I'd never ever have thought to remove the dot. How did you discover or know that? -- Sebastien Vauban
Re: [O] Convention for tags and properties
Nicolas Goaziou wrote: Sebastien Vauban writes: Following those conventions, I guess that: - The `crypt' tag should be renamed `CRYPT' - The `Effort' property should be renamed `EFFORT' Right? FWIW, I think you're correct. Would such a patch be accepted, then, if I can make it? Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] Padlines
Hi Eric, Eric Schulte wrote: Sebastien Vauban sva-n...@mygooglest.com writes: Eric Schulte wrote: aditya siram aditya.si...@gmail.com writes: What's the rationale for having padlines by default in tangled source? It generates wrong programs for languages where whitespace is significant (Haskell) and, for me, doesn't noticeably improve the look of the tangled file in cases where it isn't. It is possible to change the value of default header arguments on a per-language basis because e.g., while (:padlines yes) may make sense for sh, it probably doesn't for Haskell. Could it be possible that :padline yes does not insert a blank line in front of the very first block, only *between* all blocks? I just pushed up a commit which implements this behavior. See the attached file for an example. #+Title: Examples with the new padline behavior The blank line which was inserted between blocks isn't anymore for me. ECM: --8---cut here---start-8--- * Tangle these blocks :PROPERTIES: :tangle: yes :padline: yes :END: #+begin_src emacs-lisp :file test.csv data #+end_src #+begin_src emacs-lisp :file test.csv datb #+end_src --8---cut here---end---8--- results in: --8---cut here---start-8--- data datb --8---cut here---end---8--- Note that I tried adding :padline to yes, but I normally should not, as it is the default. Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] Padlines
Hi Eric, Eric Schulte wrote: The blank line which was inserted between blocks isn't anymore for me. [...] results in: --8---cut here---start-8--- data datb --8---cut here---end---8--- Note that I tried adding :padline to yes, but I normally should not, as it is the default. Thanks for this bug report, there was a problem in my previous patch in this thread. I've just pushed up a fix which should solve this problem. Confirmed! Thanks a lot. Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] :colnames no no longer default for Emacs Lisp [Was] Lisp error: (wrong-type-argument listp hline)
Hi Eric, Eric Schulte wrote: I always wondered why emacs-lisp is the _only_ language with :colnames no as its default. Is there a reason therefore? If no really good reason, could we suppress that? This seemed to make sense early on because Emacs Lisp could easily process hlines itself, but at this point it adds more confusion than it is worth. I've reverted this default for elisp. Thanks. This looks more clear, now. Best regards, Seb -- Sebastien Vauban
Re: [O] [PATCH] Display a count of items next to each list (or block)
Hi Bernt, Bernt Hansen wrote: Sebastien Vauban writes: In order to make Org much nicer to use, I felt we missed a count of items next to the lists (or blocks, for multi-block agenda views). Here is a patch to add this, depending on the new variable `org-agenda-display-count-of-items' (enabled by default). The count of items must be updated when you apply tag filtering on lists. The patch does it as well. This patch doesn't report correct counts when a compact agenda is used and you filter by some task that doesn't match any entries in your block. The block is empty and shows no tasks but the counter is incorrect. ;; Compact the block agenda view (setq org-agenda-compact-blocks t) Filter by some tag not in these blocks / TAB PERSONAL RET Tasks to Refile (15/0) Stuck Projects (15/1) If the counts are correct I think this makes a good addition to org-mode. Thanks for testing! I may have a hard time when there is no explicit separator between blocks. Though, I'll try to fix it ASAP and come back with a solution for that edge case. Best regards, Seb -- Sebastien Vauban
Re: [O] org-export-async-init-file
Hello Rasmus and Thomas, Rasmus wrote: My question: how to change the value of org-export-async-init-file when I export the subtree? Perhaps babel and org-element? I'm not sure of the order of execution, but perhaps you can can check the title and set the init file condtional on that. A detail: maybe checking on some tags (instead of the title), to make the solution applicable in many more documents? Best regards, Seb -- Sebastien Vauban
Re: [O] Limit subtree to a specific export backend
Sebastian Wiesner wrote: can I limit a subtree to be exported with specific backends only? I.e. only to HTML, but not Texinfo or LaTeX? Background: I am trying to simplify the documentation of one of my projects, and combine the website and the user manual into a single document. Naturally, there is some content on the website that should not appear in the manual and vice versa. A partly manual solution would be to use tags for which sections to export in which backend, make a sparse tree with the backend you're interested to export, and export what's visible? If working, such a thing could be automated in a ELisp block. Best regards, Seb -- Sebastien Vauban
Re: [O] Needing help on org-gnus + LaTeX export -
Achim Gratz wrote: Am 30.09.2013 21:05, schrieb Joseph Vidal-Rosset: Here is the beginning of my init.el in my .emacs.d/ : (message * --[ Loading my Emacs init file ]--) (add-to-list 'load-path ~/.emacs.d/org-8.2/lisp) (add-to-list 'load-path /.emacs.d/org-8.2/contrib/lisp t) ^ ~ Missing tilde... (package-initialize) Try this perhaps: (message * --[ Loading my Emacs init file ]--) (add-to-list 'load-path /.emacs.d/org-8.2/contrib/lisp t) (add-to-list 'load-path ~/.emacs.d/org-8.2/lisp) (require 'org-loaddefs) (package-initialize) This is correct only if `org' is not installed via ELPA, right? Otherwise, ~/.emacs.d/elpa/org-date would be added to the load-path and could be a cause of mixed code usage? Best regards, Seb -- Sebastien Vauban
Re: [O] Adding time intervals [OT?]
Hi Marcin, Marcin Borkowski wrote: I am pretty sure that I've read about functions for summing time intervals so that as a result, we don't get the largest possible interval (like in [1,2] + [3,4] = [4,6]), but something more along the lines of time estimate (where assuming that everything will happen at the fastest or slowest possible pace is unrealistic, since the estimates are uncorrelated). Unfortunately, I can't remember where I read that. I did a quick grep on Calc and Org manuals and didn't find it - but maybe I'm missing something? Or maybe I was just dreaming and Emacs does not have anything like that? See Estimate ranges in column view on http://www.mail-archive.com/emacs-orgmode@gnu.org/msg26175.html. Best regards, Seb -- Sebastien Vauban
Re: [O] Limit subtree to a specific export backend
Hi Sebastian, Sebastian Wiesner wrote: 2013/9/30 Sebastien Vauban sva-n...@mygooglest.com: A partly manual solution would be to use tags for which sections to export in which backend, make a sparse tree with the backend you're interested to export, and export what's visible? I am by far not an Org mode expert, and have never used sparse trees. Would you mind to point me to the appropriate manual section, or give me some details on how to create a sparse tree matching a specific tag only? See section 2.6 Sparse trees: ╭ │ An important feature of Org mode is the ability to construct _sparse │ trees_ for selected information in an outline tree, so that the entire │ document is folded as much as possible, but the selected information is │ made visible along with the headline structure above it(1). Just try │ it out and you will see immediately how it works. │ │Org mode contains several commands creating such trees, all these │ commands can be accessed through a dispatcher: │ │ `C-c /' (`org-sparse-tree') │ This prompts for an extra key to select a sparse-tree creating │ command. ╰ It will help to expand all entries which contain a certain keyword (see `C-c / /') and collapse all others. Though, it won't help for tagged entries: their contents won't be opened automatically by doing `C-c / m' (match for a tag). Anyway, `C-c /' is a very interesting (set of) commands to know! Best regards, Seb -- Sebastien Vauban
Re: [O] [BUG?] Strange message in minibuffer while exporting into HTML
Hello Vladimir, Vladimir Lomov wrote: please consider this sample Org document (ex-call.org): #+TITLE: Example with CALL directive #+AUTHOR: Vladimir Lomov #+OPTIONS: num:nil * This is first section Recently I faced with a strange message in minibuffer: #+BEGIN_EXAMPLE Marker points into wrong buffer: #marker in no buffer #+END_EXAMPLE when exporting the Org document into HTML. At first I was puzzled what causes this message in that particular Org document, while rest my Org documents are exported to HTML just fine. After a while I tried to strip down that document to figure out what may cause that message. And seems that problem is in CALL strings. In that particural document I have several CALL directive, commenting out them (just added a ~#~ at beginning of a line with a space after it) allows me to export that document into HTML. The purpose of this example document to ensure that even simple CALL line could cause such behaviour. This is CALL directive, it calls function defined below #+CALL: simple-func() Even without evaluation of this directive exporting into HTML fails with above message. Commenting that directive make it possible to export into HTML. Another attempt: #+CALL: simple-func(name=Vladimir Lomov) * The simple Emacs Lisp function This simple Emacs Lisp function has to be called by CALL directive: #+NAME: simple-func #+BEGIN_SRC emacs-lisp :var name=My name (format [You told me:] %S name) #+END_SRC My system: - Archlinux x86_64, gcc 4.8.1, make 4.0 - emacs: GNU Emacs 24.3.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.0) of 2013-10-10 on smoon4 (compile from bzr trunk, revno 114606) - org-mode: Org-mode version 8.2.1 (release_8.2.1-77-g8aaf3c @ /usr/share/emacs/site-lisp/org/) I have typed above document in Emacs run as emacs -Q -l min-org.el --eval (require 'ox-html) ex-call.org Is this really a bug or my misunderstanding of 'CALL' directive usage? I confirm the problem on my Windows environment: - GNU Emacs 24.3.50.1 (i686-pc-mingw32) of 2013-09-30 on LEG570 - Org-mode version 8.1.1 (release_8.1.1-13-ga1f9a1) ... and I don't see any problem with your syntax. I'm as puzzled as you are. Would you wanna help, I think trying to bisect Org mode would be a great step into fixing what I think to be a problem in Org. Best regards, Seb -- Sebastien Vauban
Re: [O] Dynsite: easier configuration of projects, with config.or instead of emacs lisp and dynamic relative paths
Hello John,
John Kitchin wrote:
I implemented a version of elisp links to dynamically generated content at
export time here:
http://jkitchin.github.io/blog/2013/10/14/Lisp-links-in-org-mode-to-dynamically-generated-content/
I am not sure it was you are thinking about, but maybe it could give you
some ideas.
In this case, instead of special link handling, I'd have used something which
already exists:
--8---cut here---start-8---
This file was exported on src_emacs-lisp{(format-time-string %Y-%m-%d at %H:%m
%p)}.
The answer to 2 + 3 is src_emacs-lisp{(+ 2 3)}.
--8---cut here---end---8---
Or is there a reason for doing it with links?
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [RFC] Change some defcustoms into defcont
Hello Nicolas, Nicolas Goaziou wrote: I'd like to suggest changing the following defcustom variables into defconst: - org-deadline-string - org-scheduled-string - org-closed-string - org-clock-string - org-comment-string - org-quote-string - org-effort-property - org-archive-tag At first, I thought: I certainly have changed at least one of them (such `org-log-note-headings' for which I changed the `state' string to State %-12S - %-12s %t -- as I prefer the FROM - TO presentation of state changes). Though, FWIW, no, these are still the original values in my case as well. There's no fundamental reason to change these, as they belong to Org syntax, much like star character for headlines and :END: closing string for drawers. They can also introduce bugs in code when modified (e.g. modifying `org-effort-property' breaks `ox-taskjuggler'). Of course, this can be avoided with careful checks, but this puts an extra burden on developers for a tiny benefit for the user. Eventually, they can be costly, since changing any of them implies that cache in every Org buffer must be erased. Allowing customization is generally good, but I think Org syntax should never be a moving target. Note that this shouldn't introduce much backward incompatibility (unless user changes them through customize interface) since a defconst can still be setq'ed and variables will still be used in code base. I thought that users never ever could change constants. But the docstring of `defconst' indeed tells that this constancy is not actually enforced by Emacs Lisp. Though, can we be sure that this will stay true? Opinions? OK for me. Best regards, Seb -- Sebastien Vauban
Re: [O] Beamer export: How to handle overlayarea
Hello James,
James Harkins wrote:
Per the beamer user guide, the syntax of the overlayarea environment is:
\begin{overlayarea}{area width}{area height}
environment contents
\end{overlayarea}
I can't figure out how to get the width and height in properly.
Have a look at
http://lists.gnu.org/archive/html/emacs-orgmode/2013-06/msg00922.html.
You see you could use :options. HTH.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Custom forwarding for a scheduled task
Hello Fletcher, Fletcher Charest wrote: First of all, apologies if I'm doing something wrong - I'm not used to posting in mailing lists. I read in the Org manual, about scheduled tasks : A reminder that the scheduled date has passed will be present in the compilation for today, until the entry is marked DONE, i.e., the task will automatically be forwarded until completed. Sometimes, I schedule a task but can only carry out my second day of work on that task one week later (or my first day if I couldn't work on it on the scheduled day). I would like to know if it is possible to schedule a task, for example, on a Sunday, and see it appear in the agenda the next Sunday with the mention Sched. 2x: TODO my task. This way I know I have to carry out my second day of work on that task on that day. I tried to use delays for this but couldn't obtain anything. I'm sorry if this is standard functionality or if it has been answered somewhere. I usually find all my answers about org-mode online but this time I couldn't find any info. This hasn't been answered yet, neither is it a common request. FWIW, I removed such scheduling info (2x, 3x...) because it scared me to hell when it went over 99 days delay. But, to answer you, no, I don't think it's doable in the current system. Though, you could get more or less the same functionality by clocking time, rescheduling your task for the available Sunday, and clock again. On that day, you would see that you're clocking hours 8 to 15 of your work. Best regards, Seb -- Sebastien Vauban
Re: [O] Org-mode and continuing BBDB compatibility
Hi Charles, Charles Philip Chan wrote: Christopher Culver crcul...@christopherculver.com writes: I do not see anniversaries from my .bbdb file in the agenda. I know that some work was done in the past with making org-mode compatible with bbdb3, but are the two projects no longer compatible, or do I probably have some other problem on my end? Works fine here (I am using the git version of both). How are you loading bbdb? You should just do a: (require 'bbdb-loaddefs) You mean bbdb-autoloads? Best regards, Seb -- Sebastien Vauban
Re: [O] Org-mode and continuing BBDB compatibility
Charles Philip Chan wrote: Sebastien Vauban sva-n...@mygooglest.com writes: You mean bbdb-autoloads? No, bbdb-loaddefs.el is part of bbdb3. Here is the instructions from the README file: 4) Activate BBDB: i) If the BBDB lisp files are in a directory /path/to/bbdb/lisp you can use in your emacs init file (require 'bbdb-loaddefs /path/to/bbdb/lisp/bbdb-loaddefs.el) This adds /path/to/bbdb/lisp to the load-path; so it is all you need to make BBDB known to your Emacs. ii) The user variable bbdb-print-tex-path should point to the directory where the BBDB TeX files reside (default /usr/local/share/bbdb). Weird. In the BBDB 3 version that I have from ELPA [1], I do have a file `bbdb-autoloads.el', but no `bbdb-loaddefs.el'... Best regards, Seb [1] ~/.emacs.d/elpa/bbdb-20130728.2143 -- Sebastien Vauban
Re: [O] [BUG] `org-agenda-sorting-strategy' does not work in `tags-todo'
Hello, Sebastien Vauban wrote: The following agenda view is supposed to display the tasks by ascending _DEADLINE timestamp_. #+begin_src emacs-lisp (add-to-list 'org-agenda-custom-commands '(B Today tags-todo DEADLINE=\today\ ((org-agenda-overriding-header Today) (org-agenda-sorting-strategy '(deadline-up t) #+end_src However, as you can see with the following ECM: #+begin_src org * Health :PROPERTIES: :CATEGORY: Health :END: ** TODO 3Do jogging DEADLINE: 2013-09-09 Mon ** TODO 2Check weekend hours at the gym DEADLINE: 2013-09-08 Sun * Personal :PROPERTIES: :CATEGORY: Personal :END: ** TODO 4Mail package to Susan DEADLINE: 2013-09-12 Thu * Shopping :PROPERTIES: :CATEGORY: Shopping :END: ** TODO 1Buy dog food DEADLINE: 2013-09-07 Sat #+end_src it sorts the list by _category_, instead! Today (4) Health: TODO 3Do jogging Health: TODO 2Check weekend hours at the gym Personal: TODO 4Mail package to Susan Shopping: TODO 1Buy dog food The same sorting criteria, applied on an `agenda' view, does work. #+begin_src emacs-lisp (add-to-list 'org-agenda-custom-commands '(G Agenda deadline-up agenda ((org-agenda-span 'day) (org-agenda-time-grid nil) (org-agenda-sorting-strategy '(deadline-up t) #+end_src Calendar for today 2013-09-12 Thu 5 d ago TODO 1Buy dog food 4 d ago TODO 2Check weekend hours at the gym 3 d ago TODO 3Do jogging Deadline TODO 4Mail package to Susan Anybody having a hint on this? Best regards, Seb -- Sebastien Vauban
Re: [O] Can I export a file into another target directory by setting one variable?
Hello Arne, Arne Babenhauserheide IMK wrote: For my autotools setup, I need a way to export org-mode files into a different directory (for make distcheck). Shouldn't you try to bake something with org-publish? It offers the different directory feature for free ;-) Best regards, Seb -- Sebastien Vauban
Re: [O] Problem with automatic recursive adding of org-agenda-files
Tor Eriksson wrote: In fact, now I can not get the snippet to pick up *any *new .org file in the directory .../important-directory or subdiretory! Even when the new .org file sits adjacent to a file that is picked up by the snippet. Also, if I do the same procedure again to another file that is picked up by the snippet by: changing the name of the file, updating agenda with g and pressing Abort. Then this file is also not picked up any more; not under the new name or, if I change the name back, under it's old name. This is causing serious trouble to me, since I use this system to keep track of deadlines that are really important. Does anybody have any ideas? Check you don't have a customize-variables section at the end of your .emacs file. If you once did `[' or `]' or some such to add one Org file, Org adds a line in your .emacs file. And that one will override your settings!! Really hard to find, if we don't think at such... Best regards, Seb -- Sebastien Vauban
Re: [O] [RFC] Slight change to asynchronous export
Hello Nicolas, Nicolas Goaziou wrote: At the moment, by default, external emacs process for asynchronous export is called with: /path/to/emacs -Q --batch -l org-export-async-init-file ... export stuff... where `org-export-async-init-file' defaults to `user-init-file'. It is, by default, not the same as calling emacs, because of the -Q. I suggest allowing a nil (default) value for `org-export-async-init-file'. In that case, the command will become: /path/to/emacs --batch ... export stuff... If it is a file, it will be the same as before. WDYT? IIUC, the default `user-init-file' still gets read because you drop the `-Q' option. And you allow adding a supplementary configuration file for the export process. Right? The only drawback would be for people having a long .emacs config file (which takes a long time to load): they would experience a longer running time for the async export, but it's async, so they wouldn't mind much. That seems good to me. BTW, is there no possibility of doing the same with emacsclient (but with no visible buffer)? That'd drop the startup time of Emacs. But, once again, that's not a problem per se, as it's async. It's for my own understanding. Best regards, Seb -- Sebastien Vauban
Re: [O] Insert a heading in every sibling
Marcin Borkowski wrote: Scot Becker scot.bec...@gmail.com napisał(a): I'm using org-mode to keep track of student grades. How can I easily add a bunch of identical headings at a certain level in my tree? Specifically,I have a L2 heading for each student, and I want to put a node (heading, with some properties) under each L2 student heading for that class. Personally, I'd just write a small Elisp function to do that. (It's easier than you might think - even I could do that;).) Here's a thing that is (remotely) similar: http://mbork.pl/2013-09-23_Automatic_insertion_of_habit_templates_%28en%29 Or, you could record a keyboard macro, and even save it as Elisp. Other solutions include: - using YASnippets, or - writing a skeleton in the Org document and cloning it N times at once (see C-c C-x c). Best regards, Seb -- Sebastien Vauban
Re: [O] In buffer setting for Ordered
Joe M wrote: I am trying to figure out how to add in-buffer (for all tasks in the file) setting to enforce TODO dependencies. I tried #+PROPERTY: ORDERED t but it did not work. Any thoughts, please? Just an idea: did you press C-c C-c on the property line, after adding it? If not, it's not taken into account. Well, reloading the file would do it automatically, so it's only for the first time you add it. Best regards, Seb -- Sebastien Vauban
Re: [O] org-clock-save.el state unwanted Resume clock prompt
Hello Jeff, Jeff Kowalczyk wrote: When opening any org mode files or using M-x org-mode on a buffer, I get the following prompt: : Resume clock (bsmith re: status update) (y or n) n Which refers to a specific heading in one specific org file, used all day most days. : ** DONE bsmith re: status update :CLOSED: [2013-08-06 Tue 13:12] ::LOGBOOK: :CLOCK: [2013-08-06 Tue 12:53]--[2013-08-06 Tue 13:12] = 0:19 ::END: The cause of the prompt is easily found (org-clock-save.el, source wrapped): : ;; org-persist.el - myhost at 2013-08-06 Tue 13:42 : (setq resume-clock '(/home/jtk/org/upwind.org . 2049565)) : : (setq stored-clock-history : '((/home/myuser/org/acme.org . 2044203) : (/home/myuser/org/acme.org . 2044243) : (/home/myuser/org/acme.org . 2046954) : (/home/myuser/org/acme.org . 2049576) : (/home/myuser/org/acme.org . 2049494))) The above headline corresponds to the last position character mark, 2049494. My questions are: - What's different about that heading that it isn't closed? - Is there another lisp source of clock insinuate data besides org-persist.el? - What lisp data edit operation would safely clear the open clock status? On a few occasions I've deleted org-clock-save.el to clear the problem, and had a recurrence on a different heading some weeks later. There could be some behavior related to running clocks when emacs daemon stops abruptly on system or X shutdown. Reading (late) your post. I don't know the answer, but I confirm similar behaviors: - duplicate entries in my history of clock items - there are clock items for which I did not clock for years, and which suddenly become visible when doing C-u C-c C-x C-i. Unfortunately, I've no idea why or when these problems occur. Hence, can't make an ECM right now. Best regards, Seb -- Sebastien Vauban
Re: [O] [RFC] Slight change to asynchronous export
Rick Frankel wrote: For Aaron and others concerned about e.g, `server-start', it's easy to check if emacs is not running in batch or, in the case of server start, if emacs is running in a multi-window environment. The server-start thing was a question of mine, trying to see if using emacsclient would be possible. It isn't. So, please forget about this. The async process launches a new Emacs process, with no interaction whatsoever with the Emacs you edit in. Best regards, Seb -- Sebastien Vauban
Re: [O] [PATCH] make comment-dwim in source code blocks more DWIM-ish
Hi Bastien, Bastien wrote: This patch makes it easier to (un)comment lines of babel source. Now M-; in a soucre code block should Just Work. It does! Something I've been wanting since long. It did work for me (since long) with: --8---cut here---start-8--- ;; allow comment region in the code edit buffer (according to language) (defun my-org-comment-dwim (optional arg) (interactive P) (or (org-babel-do-key-sequence-in-edit-buffer (kbd M-;)) (comment-dwim arg))) ;; make `C-c C-v C-x M-;' more convenient (define-key org-mode-map (kbd M-;) 'my-org-comment-dwim) --8---cut here---end---8--- Best regards, Seb -- Sebastien Vauban
Re: [O] org mode and eev
Hello Alan, Alan Schmitt wrote: I finally took the time to watch the eev video (http://angg.twu.net/eev-videos/video2.mp4) and I'm quite impressed by it. I find it may be redundant for some features of org mode (such as basic links to files) but I find the driving of external shell-based programs very nice. As I've seen it mentioned on this list before, I was wondering if some of you use it in addition to org mode. I've always dreamed of being able to use it from Org, to document deployment procedures (for example), and execute them. With Org only, we're not far when we execute sh code blocks in a session. Though, it's possible there must be missing things. Best regards, Seb -- Sebastien Vauban
