Hi, I have uploaded release 6.28. Once more I urge you to read the release notes carefully, there are many very interesting changes. Enjoy! - Carsten Changes in Version 6.28 ======================= Agenda changes ~~~~~~~~~~~~~~~ Refiling now works from the agenda =================================== The command `C-c C-w' can be executed to refile an entry shown in the agenda. After the command, the entry will no longer be shown in the agenda. It it is still in an agenda file, refresh the agenda to bring it up from it's new context. Bulk action ============ You can now use the `s' key to select entries in the agenda. When one or more entries have been selected, the `B' key will execute an action on all selected entries. I believe this bulk action makes mainly sense for the commands that require answering interactive prompts. So far the supported actions are - Refile all selected entries to a single destination - Archive all selected entries - Set the TODO state of all selected entries, bypassing any blocking or note-taking. - Add or remove a tag to/from all selected entries We can add more actions, if you convince me they make sense. Improvements related to `#+begin' blocks ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Indented blocks ================ `#+begin_ ... +#end_...' blocks may now be indented along with the structure of your document. So the `#+' lines no longer need to start in column 0, these lines can be, along with the block contents, indented arbitrarily. Org supports this during editing with "C-c '", and now finally treats them consistently during export across all backends. This makes these blocks work much better with plain list structure editing, and it also looks better if you like to indent text under outline headings. For example: *** This is some headline #+begin_example here we have an example #+end_example - a plain list - a sublist item - a second sublist item ORG-CENTER-START centering within the plain list item ORG-CENTER-END #+begin_example This example does terminate the sublist, the indentation of the #+begin line counts. #+end_example - but the top level plain lists continues here From now on, the indentation of such a block decides whether it is part of a plain list item or if it is actually terminating the list. This was so far inconsistent between editing behavior and export, now it is consistent. The content of the block, i.e. the text between the #+ lines gets an extra indentation of two space characters, which I find visually pleasing. You can change the amount of extra indentation using the variable `org-src-content-indentation'. This was a pretty complex change, achieved in many small steps over the last couple of weeks. It cleans up one of the more annoying inconsistencies in Org. I hope it will work, but I am sure you will let me know if not. Indented tables ================ Also tables can be fully indented now. What is new here is that the `#+TBLFM' line, and also things like `#+caption', `#+label', `#+attr_...' etc can be indented along with the table. Again, this makes the look of the document better and allows for proper plain list structure editing. Protected blocks ================= Some `#+begin_ ... +#end_...' blocks contain text that should not be processed like normal Org-mode text. `example' and `src' block fall into this class, and so do `ditaa' blocks, for example. The content in such blocks is now properly fontified in a single face (called `org-block'). This was a frequently requested feature. The list of blocks that should be protected from normal Org-mode fontification is defined in the variable `org-protecting-blocks'. Modules defining new blocks should add to this variable when needed. `org-exp-blocks.el' does this already. Hide and show the contents of blocks ===================================== Blocks can now be folded and unfolded with `TAB'. If you want to have all blocks folded on startup, customize `org-hide-block-startup' or use the `#+STARTUP' options `hideblocks' or `showblocks' to overrule this variable on a per-file basis. Thanks to Eric Schulte for a patch to this effect. Moved Eric Schulte's org-exp-blocks.el into the core ===================================================== This seems to be getting a lot of use now, so it is now part of the core and loaded automatically. This package can now also be used to define new blocks. Customize the variable `org-export-blocks' or use the function `org-export-blocks-add-block'. New and updated contributed modules ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ org-export-generic.el is now a contributed package. ==================================================== This new module allows users to export an Org page to any type of output by constructing the output using a list of prefixes, format specifications and suffixes for the various types of org data (headlines, paragraphs, list bullets, etc). Use the `org-set-generic-type' function to define your own export types and have them bound to a key (use an upper-case letter for user export definitions). Thanks to Wes Hardaker for this contribution with a lot of potential. New contributed modules org-mac-iCal.el by Christopher Suckling ================================================================ See the [documentation on Worg]. [documentation on Worg]: http://orgmode.org/worg/org-contrib/org-mac-iCal.php org-jira.el: New file, by Jonathan Arkell ========================================== Links to Jira tickets. org-R.el: Updated. =================== /org-R.el/ has been updated, thanks to Dan Davison for this. `[ TABLE-OF-CONTENTS]' is now also used for LaTeX export ========================================================= This cookie will mark the location of the `\tableofcontents' macro. Triggered by a report by Yuva. Changes to the clocking system ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New option `org-clock-out-switch-to-state'. ============================================ Clocking out can now switch the task to a particular state. This was a request by Manish. More control about what time is shown in mode line while clocking ================================================================== - If you have an `Effort' property defined, its value is also shown in the mode line, and you can configure `org-clock-sound' to get an alert when your planned time for a particular item is over. - When an entry has been clocked earlier, the time shown in the mode line while the item is being clocked is now the sum of all previous, and the current clock. - The exception to the previous rule are repeating entries: There the clock time will only be clocking instances recorded since the last time the entry when through a repeat event. The time of that event is now recorded in the `LAST_REPEAT' property. - You can use the property CLOCK_MODELINE_TOTAL to get control over what times are displayed in the mode line, see the manual for more information. - The new command `C-c C-x C-e' can be used to change the Effort estimate and therefore to change the moment when the clock sound will go off. - The clock string in the modeline now has a special font, `org-mode-line-clock'. This was a proposal by Samuel Wales. - Clicking on the mode line display of the clock now offers a menu with important clock functions like clocking out, or switching the clock to a different task. Thanks to Konstantin Antipin for part of the implementation, and thanks to Bernt Hansen for helping to iron out the issues related to repeated tasks. Miscellaneous changes ~~~~~~~~~~~~~~~~~~~~~~ Allow to specify the alignment in table columns by hand ======================================================== Similar to the `<20>' cookies that allow to specify a maximum width for a table column, you can now also specify the alignment in order to overrule the automatic alignment choice based on the dominance of number or non-number fields in a column. The corresponding cookies are `<l>' and `<r>' for left and right side alignment, respectively. These can be combined with maximum width specification like this: `<r15>'. This was a proposal by Michael Brand. Stop logging and blocking when selecting a TODO state ====================================================== Sometimes you want to quickly select or change a TODO state of an item, without being bothered by your setup for blocking state changes and logging entries. So in this case, you don't want the change be seen as a true state change. You can now set the variable `org-treat-S-cursor-todo-selection-as-state-change' to nil. Then, when you use `S-left' and `S-right' to quickly flip through states, blocking and logging will be temporarily disabled. Export BBDB anniversaries to iCalendar ======================================= See the variable `org-icalendar-include-bbdb-anniversaries'. This was a request by Richard Riley, thanks to Thomas Baumann for the prompt implementation. Macro definitions can be collected in an #+SETUPFILE ===================================================== If you want to use many macros in different files, collect the `#+macro' lines into a file and link to them with #+SETUPFILE: path/to-file Subtree cloning now also shifts inactive dates =============================================== When using the command `org-clone-subtree-with-time-shift', time stamps will be shifted for each clone. So far, this applied only to active timestamps, but now it does apply to inactive ones as well. HTML table export: Assign alternating classes to rows ====================================================== The new variable `org-export-table-row-tags' can now be set up in a way so that different table lines get special CSS classes assigned. This can be used for example to choose different background colors for odd and even lines, respectively. The docstring of the variable contains this example: (setq org-export-table-row-tags (cons '(if head "<tr>" (if (= (mod nline 2) 1) "<tr class=\"tr-odd\">" "<tr class=\"tr-even\">")) "</tr>")) It makes use of the local variables `head' and `nline' which are used to check whether the current line is a header line, and whether it is an odd or an even line. Since this is fully programmable, you can do other things as well. This was a request by Xin Shi. Remember: target headline may be a function ============================================ When setting up remember templates, the target headline may now be a function, similarly to what is allowed for the target file. The functions needs to return the headline that should be used. Remove flyspell overlays in places where they are not wanted ============================================================= We now keep flyspell from highlighting non-words in links. Update targets in the Makefile =============================== Some new targets in the default Makefile make it easier to update through git to the latest version: `update' and `up2'. Here are the definitions. update: git pull ${MAKE} clean ${MAKE} all up2: update sudo ${MAKE} install This was a request by Konstantin Antipin. BUG fixes ========= As always, lots and lots of bug fixes. Thanks for all who contributed with reports, analysis and patches.
On Jun 25, 2009, at 9:10 AM, Carsten Dominik wrote:
> Changes in Version 6.28
> =======================
>
> Bulk action
> ============
>
> You can now use the `s' key to select entries in the agenda.
> When one or more entries have been selected, the `B' key will
> execute an action on all selected entries. I believe this bulk
> action makes mainly sense for the commands that require answering
> interactive prompts. So far the supported actions are
>
> - Refile all selected entries to a single destination
> - Archive all selected entries
> - Set the TODO state of all selected entries, bypassing any
> blocking or note-taking.
> - Add or remove a tag to/from all selected entries
>
> We can add more actions, if you convince me they make sense.
Note that this new command is not yet tested well and has
destructive potential. Please test it under appropriate
security measures, i.e. backups or git-protected files.
- Carsten
Thanks for this release!
Carsten Dominik <carsten.dominik@gmail.com> writes:
> - If you have an `Effort' property defined, its value is also
> shown in the mode line, and you can configure `org-clock-sound'
> to get an alert when your planned time for a particular item is
> over.
I love this new feature.
Perhaps it would make sense to have an option `org-clock-default-effort'
(or `org-clock-default-timer') for tasks that have no Effort property?
--
Bastien
Carsten Dominik <carsten.dominik@gmail.com> writes:
> Bulk action
> ============
>
> You can now use the `s' key to select entries in the agenda.
> When one or more entries have been selected, the `B' key will
> execute an action on all selected entries. I believe this bulk
> action makes mainly sense for the commands that require answering
> interactive prompts. So far the supported actions are
>
> - Refile all selected entries to a single destination
> - Archive all selected entries
> - Set the TODO state of all selected entries, bypassing any
> blocking or note-taking.
> - Add or remove a tag to/from all selected entries
>
> We can add more actions, if you convince me they make sense.
I'm a bit disoriented with the new keybinding for `s' -- I got used
to it the same way I'm used to `C-x C-s'.
Also, I think it would be nice to make this "bulk action" feature more
consistent with bulk action mechanisms from other packages like dired,
buff-menu.el or bookmark-mode.el.
Here is how the keys are mapped on various modes:
| key | dired & bookmark-mode & buff-menu | Org |
|-----+------------------------------------+---------------|
| m | mark | month view |
| u | unmark | |
| d | mark for deletion | day view |
| D | delete marked | include diary |
| x | perform actions | exit agenda |
| U | unmark (only in dired) | [unset] |
I propose to use [dmuUx] the same way in Org. We could move the daily,
weekly, monthly view to respectively D,W,M.
This would discard the diary inclusion (currently on 'D') and the
display of the Moon's phases (currently on 'M') -- not sure whether a
lot of people use this anyway, and these commands can still find key
bindings.
I like 'U' from dired, it's very convenient to be able to delete all
marks at once (I which this could be implemented in buff-menu.el and
bookmark-mode as well...)
Carsten, what do you think?
--
Bastien
On 25 Jun 2009, at 15:19, Bastien wrote: > Carsten Dominik <carsten.dominik@gmail.com> writes: > Bulk action >> =========== [snip] > I'm a bit disoriented with the new keybinding for `s' -- I got used > to it the same way I'm used to `C-x C-s'. Same here. It'll take some time to adopt. But... > Also, I think it would be nice to make this "bulk action" feature more > consistent with bulk action mechanisms from other packages like dired, > buff-menu.el or bookmark-mode.el. I also support this request. > Here is how the keys are mapped on various modes: > > | key | dired & bookmark-mode & buff-menu | Org | > |-----+------------------------------------+---------------| [snip] > | D | delete marked | include diary | [snip] > I propose to use [dmuUx] the same way in Org. We could move the > daily, > weekly, monthly view to respectively D,W,M. Mapping the D to 'daily view' would not make it the same as in dired. Of course, if the perception of the Agenda's content and behavior is sufficiently different from that of dired, the keybindings do not have to be the same. Maybe it's worth looking at how other packages (like gnus and friends) are treating their summaries? Having said all that, I'll take whatever bindings org-mode ships with; you can always change them :-) Cheers, Peter.
Thank's Carsten! Carsten Dominik <carsten.dominik@gmail.com> writes: > Improvements related to `#+begin' blocks > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Indented blocks > ================ > Indented tables > ================ Yeeess! This is sooo good! These are my favourites! They solves indentation problems in the text following such blocks too! We now can just type ahead, no need to indent the following text by hand again! Best regards Sebastian
On Jun 25, 2009, at 3:19 PM, Bastien wrote: > Carsten Dominik <carsten.dominik@gmail.com> writes: > >> Bulk action >> ============ >> >> You can now use the `s' key to select entries in the agenda. >> When one or more entries have been selected, the `B' key will >> execute an action on all selected entries. I believe this bulk >> action makes mainly sense for the commands that require answering >> interactive prompts. So far the supported actions are >> >> - Refile all selected entries to a single destination >> - Archive all selected entries >> - Set the TODO state of all selected entries, bypassing any >> blocking or note-taking. >> - Add or remove a tag to/from all selected entries >> >> We can add more actions, if you convince me they make sense. > > I'm a bit disoriented with the new keybinding for `s' -- I got used > to it the same way I'm used to `C-x C-s'. This is why `C-x C-s' seems to me the perfect key for this. > > Also, I think it would be nice to make this "bulk action" feature more > consistent with bulk action mechanisms from other packages like dired, > buff-menu.el or bookmark-mode.el. You know, I have been agonizing over these bindings, switching them back and forward. Obviously, I would like to have things like in dired and similar programs. I don't want to switch `d' to `D', no way. One of the consistent things in the agenda keymap is that caleandar/diary related keys are upper case. `d' and `w' are not negotiable. With `d' and `w' in place, `m' and `y' are consistent, logical. However, I don't believe anyone uses monthly views, I am sure that no-one uses yearly views, right? So I will negotiate over `m', i someone can propose a viable alternative that makes sense. u and U are free, so this will be good and we should use this. I strongly hesitate to use "x" for action, because it has been "exit" for so many years, and because I don't want anyone to execute this command by accident.... - Carsten > > Here is how the keys are mapped on various modes: > > | key | dired & bookmark-mode & buff-menu | Org | > |-----+------------------------------------+---------------| > | m | mark | month view | > | u | unmark | | > | d | mark for deletion | day view | > | D | delete marked | include diary | > | x | perform actions | exit agenda | > | U | unmark (only in dired) | [unset] | > > I propose to use [dmuUx] the same way in Org. We could move the > daily, > weekly, monthly view to respectively D,W,M. > > This would discard the diary inclusion (currently on 'D') and the > display of the Moon's phases (currently on 'M') -- not sure whether a > lot of people use this anyway, and these commands can still find key > bindings. > > I like 'U' from dired, it's very convenient to be able to delete all > marks at once (I which this could be implemented in buff-menu.el and > bookmark-mode as well...) > > Carsten, what do you think? > > -- > Bastien
On 25 Jun 2009, at 16:24, Carsten Dominik wrote: > > On Jun 25, 2009, at 3:19 PM, Bastien wrote: > >> Carsten Dominik <carsten.dominik@gmail.com> writes: >> >>> Bulk action >>> ============ > With `d' and `w' in place, `m' and `y' are consistent, logical. > However, I don't believe anyone uses monthly views, I am sure > that no-one uses yearly views, right? So I will negotiate over > `m', i someone can propose a viable alternative that makes sense. With 'd' and 'w' in place, I would keep the 'm', even if it is less used (especially for less used interactions, consistency is a must). > I strongly hesitate to use "x" for action, because it has > been "exit" for so many years, and because I don't want > anyone to execute this command by accident.... Through, but for many new [org-mode] users it wont be a problem. AFAIK, `x' in dired requires a confirmation, so you've got an escape hatch. The `x' could be remapped to `Q' (I believe gnus makes the same distinction between q and Q). A possible way out it that we can switch between two sets of keybindings, a 'compatibility' one and a 'dired'-like one. Default would be the compatibility set. Sometimes one spends much more time thinking about such things than actually implementing stuff... :-( But in the end, it is usually worth it. Cheers, Peter.
Carsten Dominik <carsten.dominik@gmail.com> writes:
> With `d' and `w' in place, `m' and `y' are consistent, logical.
> However, I don't believe anyone uses monthly views, I am sure
> that no-one uses yearly views, right? So I will negotiate over
> `m', i someone can propose a viable alternative that makes sense.
I use monthly view... monthly :) To get my clock report usage for the
file over the past month. I restrict the agenda to the single file when
doing this monthly view to get clock time just for this project and that
could possibly be done with a dynamic block.
I've been enjoying not having my generated clock reports in my git
history though and the agenda monthly view is perfect for that.
-Bernt
On Jun 25, 2009, at 4:57 PM, Bernt Hansen wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> With `d' and `w' in place, `m' and `y' are consistent, logical.
>> However, I don't believe anyone uses monthly views, I am sure
>> that no-one uses yearly views, right? So I will negotiate over
>> `m', i someone can propose a viable alternative that makes sense.
>
> I use monthly view... monthly :) To get my clock report usage for the
> file over the past month. I restrict the agenda to the single file
> when
> doing this monthly view to get clock time just for this project and
> that
> could possibly be done with a dynamic block.
>
> I've been enjoying not having my generated clock reports in my git
> history though and the agenda monthly view is perfect for that.
Nobody is talking about abandoning monthly view - only about putting
it on a different key.
- Carsten
Carsten Dominik <carsten.dominik@gmail.com> writes: >> I'm a bit disoriented with the new keybinding for `s' -- I got used >> to it the same way I'm used to `C-x C-s'. > > This is why `C-x C-s' seems to me the perfect key for this. I was not aware `C-x C-s' is also available from the agenda, great. > You know, I have been agonizing over these bindings, > switching them back and forward. Obviously, I would like > to have things like in dired and similar programs. > > I don't want to switch `d' to `D', no way. One of the consistent things > in the agenda keymap is that caleandar/diary related keys are upper > case. `d' and `w' are not negotiable. What about having those dired-like keys with a modifier? M-d: mark for deletion M-m: mark for operation M-u: unmark this entry M-x: operate on marked entries M-D: delete marked entries M-U: unmark all This way, no need to change anything from the current keybindings just add these new ones. Having a modifier is also safer for M-x and reflect the fact that we are in a special operating mode in the agenda... (By no means I want to be fussy about the current keybindings, it just I thought it was worth discussing this before we got used to the default keybindings.) -- Bastien
Peter Frings <peter.frings@agfa.com> writes:
> Of course, if the perception of the Agenda's content and behavior is
> sufficiently different from that of dired, the keybindings do not have
> to be the same. Maybe it's worth looking at how other packages (like
> gnus and friends) are treating their summaries?
FWIW, Gnus has a completely different way of handling marks,
using # and other keybindings... but I wouldn't take this as
an example of some *core* emacs package like buff-menu.el and
bookmark-mode...
--
Bastien
Hi Carsten, As always this is a great release. On 2009-06-25, Carsten Dominik <carsten.dominik@gmail.com> wrote: > This is why `C-x C-s' seems to me the perfect key for this. Agree. >> Also, I think it would be nice to make this "bulk action" feature more >> consistent with bulk action mechanisms from other packages like dired, >> buff-menu.el or bookmark-mode.el. Agree. > You know, I have been agonizing over these bindings, > switching them back and forward. Obviously, I would like > to have things like in dired and similar programs. > > I don't want to switch `d' to `D', no way. One of the consistent > things in the agenda keymap is that caleandar/diary related keys are > upper case. `d' and `w' are not negotiable. OK, how about this? (Not trying to /negotiate/, but offer another poss :).) Keep archive-related commands together. Also allow room for the future. aa does what a does now av does what v does Keep view-related commands together. Also keep dwmy consistency. Also allow room for the future. vd does what d does now vw vm vy Keep dired compatibility. m marks <-- i like this a lot something reasonable to execute, like x or M u unmarks U unmarks all Possible? Or still not enough? -- Myalgic encephalomyelitis denialism is causing death and severe suffering, worse than MS. Conflicts of interest are destroying research. /You/ can get the disease at any time permanently. Do science and justice matter to you? http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
On Thu, Jun 25, 2009 at 8:59 AM, Sebastian Rose<sebastian_rose@gmx.de> wrote:
> Thank's Carsten!
>
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>> Improvements related to `#+begin' blocks
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> Indented blocks
>> ================
>
>> Indented tables
>> ================
>
>
> Yeeess! This is sooo good! These are my favourites! They solves
> indentation problems in the text following such blocks too!
>
> We now can just type ahead, no need to indent the following text by hand
> again!
>
This message is one of the reasons org-mode deserves to win the
contest over at SourceForge. It seems the community inspires the
developers and the developers then inspire the community.
Edd
On Thu, Jun 25, 2009 at 2:10 AM, Carsten
Dominik<carsten.dominik@gmail.com> wrote:
>
> Improvements related to `#+begin' blocks
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
These are fantastic changes! They fix the main warts I've come across
in trying to use org-mode to take development notes, and I'm happy to
see them land. Thanks!
At Thu, 25 Jun 2009 15:58:11 +0200, Peter Frings wrote: > On 25 Jun 2009, at 15:19, Bastien wrote: > > Carsten Dominik <carsten.dominik@gmail.com> writes: > > Bulk action > >> =========== > [snip] > > I'm a bit disoriented with the new keybinding for `s' -- I got used > > to it the same way I'm used to `C-x C-s'. > > Same here. It'll take some time to adopt. But... Funny thing is that I had *finally* got to the point of remembering to use 's' instead of C-xs! > > I propose to use [dmuUx] the same way in Org. We could move the > > daily, > > weekly, monthly view to respectively D,W,M. I would prefer to leave d, w and m as they are; after all, an agenda view is about days, weeks, months, ... and so the time based actions seem most appropriate as simple keys. > Having said all that, I'll take whatever bindings org-mode ships with; > you can always change them :-) Yes, of course! So, in that context, you can all ignore my comment above. However, for newbies, I would argue that the day/week/month views are more likely to be understood and used than bulk commands, at least until they cease to be newbies? Just my 2 cents (euro or dollar) worth.
[-- Attachment #1.1: Type: text/plain, Size: 1395 bytes --] Hi Carsten, On Thu, Jun 25, 2009 at 3:10 AM, Carsten Dominik <carsten.dominik@gmail.com>wrote: > Hi, > > I have uploaded release 6.28. Once more I urge you to read > the release notes carefully, there are many very interesting changes. > > Enjoy! > > - Carsten > > Changes in Version 6.28 > ======================= > > Agenda changes > ...... > > Miscellaneous changes > ~~~~~~~~~~~~~~~~~~~~~~ > > .... > > HTML table export: Assign alternating classes to rows > ====================================================== > > The new variable `org-export-table-row-tags' can now be set up in > a way so that different table lines get special CSS classes > assigned. This can be used for example to choose different > background colors for odd and even lines, respectively. The > docstring of the variable contains this example: > > (setq org-export-table-row-tags > (cons '(if head > "<tr>" > (if (= (mod nline 2) 1) > "<tr class=\"tr-odd\">" > "<tr class=\"tr-even\">")) > "</tr>")) > > > It makes use of the local variables `head' and `nline' which are > used to check whether the current line is a header line, and whether > it is an odd or an even line. Since this is fully programmable, > you can do other things as well. > > This was a request by Xin Shi. > I've just tested it. It works great! Thank you! Xin [-- Attachment #1.2: Type: text/html, Size: 1962 bytes --] [-- Attachment #2: Type: text/plain, Size: 204 bytes --] _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
At Thu, 25 Jun 2009 18:15:24 +0200,
Bastien wrote:
>
> What about having those dired-like keys with a modifier?
>
> M-d: mark for deletion
> M-m: mark for operation
> M-u: unmark this entry
> M-x: operate on marked entries
All the others could be reasonable but I think you'd have problems
with this one (M-x) in Emacs... sorry for pedantic email! ;-)
Carsten Dominik <carsten.dominik@gmail.com> writes:
> Hi,
>
> I have uploaded release 6.28. Once more I urge you to read
> the release notes carefully, there are many very interesting changes.
Thanks, as ever, for this fantastic update! I'm looking forward to using
the new batch agenda operations.
- Matt
On Jun 25, 2009, at 7:00 PM, Samuel Wales wrote: > Hi Carsten, > > As always this is a great release. > > On 2009-06-25, Carsten Dominik <carsten.dominik@gmail.com> wrote: >> This is why `C-x C-s' seems to me the perfect key for this. > > Agree. > >>> Also, I think it would be nice to make this "bulk action" feature >>> more >>> consistent with bulk action mechanisms from other packages like >>> dired, >>> buff-menu.el or bookmark-mode.el. > > Agree. > >> You know, I have been agonizing over these bindings, >> switching them back and forward. Obviously, I would like >> to have things like in dired and similar programs. >> >> I don't want to switch `d' to `D', no way. One of the consistent >> things in the agenda keymap is that caleandar/diary related keys are >> upper case. `d' and `w' are not negotiable. > > OK, how about this? (Not trying to /negotiate/, but offer another > poss :).) > > Keep archive-related commands together. Also allow room for the > future. > > aa does what a does now > av does what v does > > Keep view-related commands together. Also keep dwmy consistency. > Also allow room for the future. > > vd does what d does now > vw > vm > vy > > Keep dired compatibility. > > m marks <-- i like this a lot > something reasonable to execute, like x or M > u unmarks > U unmarks all > > Possible? Or still not enough? These are pretty good ideas. I do like using v as a prefix key for changing the view. I do like vd vw vm vy. I still want to keep "d" and "w" as fast access keys for day and week view, but month and year view are used much less, I am sure, so we could free "m" in this way. I don't think we shoud make "a" into a double key, instead also the current "v" could become a double key under "v". In fact, log mode could go there as well if we needed the "l" key at some point. Other candidates would be clock report, grid, and maybe more. Opinions? - Carsten > > -- > Myalgic encephalomyelitis denialism is causing death and severe > suffering, > worse than MS. Conflicts of interest are destroying research. / > You/ can > get the disease at any time permanently. Do science and justice > matter to > you? http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
I have changed the key bindings now: s back to save files, even tough I think C-x C-s is fine If I find a use for "s" later, I will probably take it vd vw vm vy for the day, week, month, year views d w still available shortcuts for day and week view vl for log mode, "l" still available as shortcut va include :ARCHIVE: tree stuff vA include :ARCHIVE: tree stuff and archive files m mark u unmark U unmark all B execute bulk action This does feel pretty consistent to me and breaks as little habits and tutorials as possible. - Carsten
On 26 Jun 2009, at 10:03, Carsten Dominik wrote: > I have changed the key bindings now: Your response time continues to amaze me! And your willingness to accept requests... Chapeau! [shortcuts snipped] > This does feel pretty consistent to me and breaks as > little habits and tutorials as possible. Great, thanks a lot! Cheers, Peter.
At Fri, 26 Jun 2009 07:18:46 +0200, Carsten Dominik wrote:
> These are pretty good ideas. I do like using v as a prefix key
> for changing the view. I do like vd vw vm vy. I still want to
> keep "d" and "w" as fast access keys for day and week view,
> [...]
> Opinions?
+1
I like v as a prefix key for all "views" (as opposed to "actions")
including not only d and w but also the other items you mentioned
(clock report, etc).
On Jun 26, 2009, at 12:59 PM, Eric S Fraga wrote:
> At Fri, 26 Jun 2009 07:18:46 +0200, Carsten Dominik wrote:
>
>> These are pretty good ideas. I do like using v as a prefix key
>> for changing the view. I do like vd vw vm vy. I still want to
>> keep "d" and "w" as fast access keys for day and week view,
>> [...]
>> Opinions?
>
> +1
>
> I like v as a prefix key for all "views" (as opposed to "actions")
> including not only d and w but also the other items you mentioned
> (clock report, etc).
One advantage being that I can prompt you for the
second key, so there are fewer keys to rememeber.
Do you know Emacs calc? It has this two-key interface
perfekted.
- Carsten
Carsten Dominik <dominik@uva.nl> writes:
> I have changed the key bindings now:
>
> s back to save files, even tough I think C-x C-s is fine
> If I find a use for "s" later, I will probably take it
> vd
> vw
> vm
> vy for the day, week, month, year views
>
> d
> w still available shortcuts for day and week view
>
> vl for log mode, "l" still available as shortcut
> va include :ARCHIVE: tree stuff
> vA include :ARCHIVE: tree stuff and archive files
>
> m mark
> u unmark
> U unmark all
> B execute bulk action
>
That'll work :)
-Bernt
Carsten Dominik <dominik@uva.nl> writes:
> s back to save files, even tough I think C-x C-s is fine
> If I find a use for "s" later, I will probably take it
> vd
> vw
> vm
> vy for the day, week, month, year views
>
> d
> w still available shortcuts for day and week view
>
> vl for log mode, "l" still available as shortcut
> va include :ARCHIVE: tree stuff
> vA include :ARCHIVE: tree stuff and archive files
>
> m mark
> u unmark
> U unmark all
> B execute bulk action
>
>
> This does feel pretty consistent to me and breaks as
> little habits and tutorials as possible.
Yeah, great solution - thanks!
--
Bastien
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> Bulk action
> ============
>
> You can now use the `s' key to select entries in the agenda.
> When one or more entries have been selected, the `B' key will
> execute an action on all selected entries. I believe this bulk
> action makes mainly sense for the commands that require answering
> interactive prompts. So far the supported actions are
>
> - Refile all selected entries to a single destination
> - Archive all selected entries
> - Set the TODO state of all selected entries, bypassing any
> blocking or note-taking.
> - Add or remove a tag to/from all selected entries
>
> We can add more actions, if you convince me they make sense.
IMHO setting scheduled (and maybe deadline) date would make sense.
Ulf
On Jul 1, 2009, at 9:20 AM, Ulf Stegemann wrote:
> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
>> Bulk action
>> ============
>>
>> You can now use the `s' key to select entries in the agenda.
>> When one or more entries have been selected, the `B' key will
>> execute an action on all selected entries. I believe this bulk
>> action makes mainly sense for the commands that require answering
>> interactive prompts. So far the supported actions are
>>
>> - Refile all selected entries to a single destination
>> - Archive all selected entries
>> - Set the TODO state of all selected entries, bypassing any
>> blocking or note-taking.
>> - Add or remove a tag to/from all selected entries
>>
>> We can add more actions, if you convince me they make sense.
>
> IMHO setting scheduled (and maybe deadline) date would make sense.
In what sense? Shifting all dates by the same amount, or setting them
all to a fixed date?
- Carsten
Hi all
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Jul 1, 2009, at 9:20 AM, Ulf Stegemann wrote:
>> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>>> Bulk action
>>> ============
>>>
>>> We can add more actions, if you convince me they make sense.
>>
>> IMHO setting scheduled (and maybe deadline) date would make sense.
>
> In what sense? Shifting all dates by the same amount, or setting them
> all to a fixed date?
I usually display unscheduled TODO items in my agenda as well
(org-agenda-include-all-todo), so if I decide that I should work on some
of them next week then a bulk action to schedule them might come in
handy.
So one use case is to set a fixed scheduled date for a number of TODOs.
In my case these are tasks that have not been scheduled yet.
Another use case is when I decide that there will not be enough time
this week to complete all scheduled tasks. I want to move some of the
tasks to next week. This could be either a shift by 7 days or a
rescheduling to next monday (a fixed date).
Thanks
Christian
Christian Egli <christian.egli@sbszh.ch> wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Jul 1, 2009, at 9:20 AM, Ulf Stegemann wrote:
>>> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>>>> Bulk action
>>>> ============
>>>>
>>>> We can add more actions, if you convince me they make sense.
>>>
>>> IMHO setting scheduled (and maybe deadline) date would make sense.
>>
>> In what sense? Shifting all dates by the same amount, or setting them
>> all to a fixed date?
>
> I usually display unscheduled TODO items in my agenda as well
> (org-agenda-include-all-todo), so if I decide that I should work on some
> of them next week then a bulk action to schedule them might come in
> handy.
>
> So one use case is to set a fixed scheduled date for a number of TODOs.
> In my case these are tasks that have not been scheduled yet.
>
> Another use case is when I decide that there will not be enough time
> this week to complete all scheduled tasks. I want to move some of the
> tasks to next week. This could be either a shift by 7 days or a
> rescheduling to next monday (a fixed date).
Yes, both shifting by the same amount and setting a fixed date can be
useful. I usually re-schedule leftover todos by shifting them by one
or two working days to the future. So originally I had a bulk version of
`org-agenda-do-date-later' and friends in mind as opposed to
`org-agenda-schedule'. But the latter one would be useful to. Ideally,
S-left, C-cC-s et al. would trigger a bulk shift/bulk schedule whenever
there are marked agenda items.
Ulf
On Jul 1, 2009, at 1:17 PM, Ulf Stegemann wrote:
> Yes, both shifting by the same amount and setting a fixed date can be
> useful. I usually re-schedule leftover todos by shifting them by one
> or two working days to the future. So originally I had a bulk
> version of
> `org-agenda-do-date-later' and friends in mind as opposed to
> `org-agenda-schedule'. But the latter one would be useful to. Ideally,
> S-left, C-cC-s et al. would trigger a bulk shift/bulk schedule
> whenever
> there are marked agenda items.
I am not so sure about this last point. I am not a
fan of automatic bulk action if several items are selected.
- these lists can become long, and selected entries might
be off the screen
- for this to make sense, selected entries should remain
selected after action, increasing the danger of unwanted action
- you might be in the process of selecting some entries, when you
want to do a quick action on an individual entry you come across.
But you cannot, because any action will act on all selected ones.
So I do prefer a special command like "B" to introduce bulk action.
Opinions?
- Carsten
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> On Jul 1, 2009, at 1:17 PM, Ulf Stegemann wrote:
>> Yes, both shifting by the same amount and setting a fixed date can be
>> useful. I usually re-schedule leftover todos by shifting them by one
>> or two working days to the future. So originally I had a bulk version of
>> `org-agenda-do-date-later' and friends in mind as opposed to
>> `org-agenda-schedule'. But the latter one would be useful to. Ideally,
>> S-left, C-cC-s et al. would trigger a bulk shift/bulk schedule whenever
>> there are marked agenda items.
>
> I am not so sure about this last point. I am not a
> fan of automatic bulk action if several items are selected.
>
> - these lists can become long, and selected entries might
> be off the screen
> - for this to make sense, selected entries should remain
> selected after action, increasing the danger of unwanted action
> - you might be in the process of selecting some entries, when you
> want to do a quick action on an individual entry you come across.
> But you cannot, because any action will act on all selected ones.
>
> So I do prefer a special command like "B" to introduce bulk action.
I undecided on this, too. Automagically working on marked entries should
they exists seems more natural to me but you are right more dangerous,
too. So I'm perfectly with you except that I'd say that marked entries
should be unmarked after the action. But anyway, triggering bulk actions
with a special command appears absolutely fine to me.
Ulf
On Jul 2, 2009, at 1:14 PM, Ulf Stegemann wrote:
> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
>> On Jul 1, 2009, at 1:17 PM, Ulf Stegemann wrote:
>>> Yes, both shifting by the same amount and setting a fixed date can
>>> be
>>> useful. I usually re-schedule leftover todos by shifting them by one
>>> or two working days to the future. So originally I had a bulk
>>> version of
>>> `org-agenda-do-date-later' and friends in mind as opposed to
>>> `org-agenda-schedule'. But the latter one would be useful to.
>>> Ideally,
>>> S-left, C-cC-s et al. would trigger a bulk shift/bulk schedule
>>> whenever
>>> there are marked agenda items.
>>
>> I am not so sure about this last point. I am not a
>> fan of automatic bulk action if several items are selected.
>>
>> - these lists can become long, and selected entries might
>> be off the screen
>> - for this to make sense, selected entries should remain
>> selected after action, increasing the danger of unwanted action
>> - you might be in the process of selecting some entries, when you
>> want to do a quick action on an individual entry you come across.
>> But you cannot, because any action will act on all selected ones.
>>
>> So I do prefer a special command like "B" to introduce bulk action.
>
> I undecided on this, too. Automagically working on marked entries
> should
> they exists seems more natural to me but you are right more dangerous,
> too. So I'm perfectly with you except that I'd say that marked entries
> should be unmarked after the action.
The reason why I said they would have to stay marked is that when
you use S-right to reschedule, you want to be able to repeat
this command several times to reach the desired date.....
OK, settled, we will use the special command.
- Carsten
On Jul 1, 2009, at 12:26 PM, Christian Egli wrote:
>
> Hi all
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Jul 1, 2009, at 9:20 AM, Ulf Stegemann wrote:
>>> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>>>> Bulk action
>>>> ============
>>>>
>>>> We can add more actions, if you convince me they make sense.
>>>
>>> IMHO setting scheduled (and maybe deadline) date would make sense.
>>
>> In what sense? Shifting all dates by the same amount, or setting
>> them
>> all to a fixed date?
>
> I usually display unscheduled TODO items in my agenda as well
> (org-agenda-include-all-todo), so if I decide that I should work on
> some
> of them next week then a bulk action to schedule them might come in
> handy.
>
> So one use case is to set a fixed scheduled date for a number of
> TODOs.
> In my case these are tasks that have not been scheduled yet.
>
> Another use case is when I decide that there will not be enough time
> this week to complete all scheduled tasks. I want to move some of the
> tasks to next week. This could be either a shift by 7 days or a
> rescheduling to next monday (a fixed date).
This should work now, I added "s" and "d" as bulk commands.
Both commands will prompt for a date, and that date will be set for
all entries.
If you specify something like "++2d" at the prompt, all
dates will be shifted by the same amount.
- Carsten
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> On Jul 1, 2009, at 12:26 PM, Christian Egli wrote:
>
>>
>> Hi all
>>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> On Jul 1, 2009, at 9:20 AM, Ulf Stegemann wrote:
>>>> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>>>>> Bulk action
>>>>> ============
>>>>>
>>>>> We can add more actions, if you convince me they make sense.
>>>>
>>>> IMHO setting scheduled (and maybe deadline) date would make sense.
>>>
>>> In what sense? Shifting all dates by the same amount, or setting them
>>> all to a fixed date?
>>
>> I usually display unscheduled TODO items in my agenda as well
>> (org-agenda-include-all-todo), so if I decide that I should work on some
>> of them next week then a bulk action to schedule them might come in
>> handy.
>>
>> So one use case is to set a fixed scheduled date for a number of TODOs.
>> In my case these are tasks that have not been scheduled yet.
>>
>> Another use case is when I decide that there will not be enough time
>> this week to complete all scheduled tasks. I want to move some of the
>> tasks to next week. This could be either a shift by 7 days or a
>> rescheduling to next monday (a fixed date).
>
> This should work now, I added "s" and "d" as bulk commands.
> Both commands will prompt for a date, and that date will be set for all
> entries.
>
> If you specify something like "++2d" at the prompt, all
> dates will be shifted by the same amount.
Works like a charm and proves to be a useful time-saver from the very
fist moment on. Thanks for implementing it :)
Ulf