Release 6.30

Release 6.30

[Carsten Dominik]

Hi,

I am releasing Org-mode version 6.30.

Enjoy!

- Carsten

              Changes in Version 6.30
              =======================

Inconsistent changes
~~~~~~~~~~~~~~~~~~~~~

Agenda now uses `f' and `b' to move through time
=================================================

Up to now, the Org-mode agenda used the cursor keys `left' and
`right' to switch the agenda view forward an backward through
time.  However, many people found this confusing, and others
wanted to be able to do cursor motion in the agenda, for example
to select text.  Therefore, after an extensive discussion on
`emacs-orgmode@gnu.org', it was decided to use the `b' and
`f' keys instead, and to let the cursor keys do cursor motion
again.

Agenda follow mode is now on the `F' key
=========================================

This was necessary to free up the `f' key, see above.

Details
~~~~~~~~

Maintenance
============

New command to submit a bug report
-----------------------------------

There is now a special command `M-x org-submit-bug-report'.  This
command will create a mail buffer with lots of useful details.
In particular, it contains complete version information for Emacs
and Org-mode.  It will also (if you agree to it) contain all
non-standard settings of org-mode and outline-mode related
variables.  Even if you do not sent your emails from within
Emacs, please still use this command to generate the information
and then copy it into your mail program.

The command will not generate and include a `*Backtrace*' buffer,
please do this yourself if you have hit an error.  For more
information, see the [feedback section] of the manual.

[feedback section]: http://orgmode.org/manual/Feedback.html#Feedback

New contributed package org-track.el
-------------------------------------

This package allows to keep up-to-date with current Org
development, using only Emacs on-board means.  So if you don't
want or cannot use `git', but still want to run the latest and
hottest Org-mode, this is for you.

Thanks to Sebastian Rose for this contribution.

Agenda
=======

Agenda now uses `f' and `b' to move through time
-------------------------------------------------

Up to now, the Org-mode agenda used the cursor keys `left' and
`right' to switch the agenda view forward an backward through
time.  However, many people found this confusing, and others
wanted to be able to do cursor motion in the agenda, for example
to select text.  Therefore, after an extensive discussion on
`emacs-orgmode@gnu.org', it was decided to use the `b' and
`f' keys instead, and to let the cursor keys do cursor motion
again.

Agenda follow mode is now on the `F' key
-----------------------------------------

This was necessary to free up the `f' key, see above.

The agenda can be put into a dedicated frame
---------------------------------------------

When the variable `org-agenda-window-setup' has the value
`separate-frame', then the new frame created to show the agenda
will now have the window marked as /dedicated/.  As a
consequence, exiting the agenda while the agenda is the only
window on the frame will kill that frame.

This was a request by Henry Atting.

New mode to show some entry body text in the agenda
----------------------------------------------------

There is now a new agenda sub-mode called
`org-agenda-entry-text-mode'.  It is toggled with the `E' key.
When active, all entries in the agenda will be accompanied by a
few lines from the outline entry.  The amount of text can be
customized with the variable `org-agenda-entry-text-maxlines'.

This was a request by Anthony Fairchild, Manish, and others.

Improve following links from the agenda
----------------------------------------

`C-c C-o' in the agenda will now offer all links in the headline
and text of an entry.  If there is only a single link, it will be
followed immediately.

Avoid some duplicate entries
-----------------------------

There is a new variable that can be used to avoid some duplicate
agenda entries: `org-agenda-skip-scheduled-if-deadline-is-shown'
If that is set, it avoids that an entry shows up in the agenda for
today for both a scheduling and a deadline entry.  See the
docstring of the variables for more details.

This partially addresses a request by Samuel Wales.

Mark the running clock in the agenda.
--------------------------------------

If the entry currently being clocked is present in the agenda, it
will be highlighted with the face `org-agenda-clocking'.

This was a request by Rainer Stengele.


Export
=======

Allow LaTeX export to use the listings package
-----------------------------------------------

The LaTeX `listings' package can now be used for formatting
fontified source code in many programming languages.  For more
information, see
http://thread.gmane.org/gmane.emacs.orgmode/16269
http://orgmode.org/worg/org-faq.php#fontified_source_code_w_latex

Thanks to Eric Schulte for this patch.

Remove table rows that only contain width and alignment markers
----------------------------------------------------------------

The width and alignment in table columns can be set with a cookie
like "<10>" or "<r>" or "<r10>".  In order to keep Org from
exporting such lines, the first column of a line should contain
only "/".  However, for convenience, there is now a special case:
If the entire row contains only such markers, the line will
automatically be discarded during export, even is the first
column is not "/".

Allow Macro calls to span several lines.
-----------------------------------------

Macro calls may now span several lines, to write several
arguments in a cleaner way.  The result of a macro call can also
span several lines, by inserting the string "\n" (backslash
followed by n) into the value in the macro definition.

These were requests by Stefan Vollmar.

Misc
=====

Quick access to all links in an entry
--------------------------------------

If `C-c C-o' is called while the cursor is in a headline, but not
directly on a link, then all links in the entry will be offered
in a small menu.  If there is only a single link, it will be
followed without a prompt.

Visibility Cycling: Allow to show all empty lines after a headline
-------------------------------------------------------------------

`org-cycle-separator-lines' can now be set to a negative value,
to indicate that, if the number of empty lines before a visible
entry is greater than the specified number, then *all* empty
lines should be shown.

This was a request by "PT" whatever this means.

Allow language names to replace some strange major mode names
--------------------------------------------------------------

Sometimes a language uses a major mode which can't be guessed
from it's name.  There is now a new variable `org-src-lang-modes'
which can be used to map language names to major modes when this
is the case.  This is used when editing a source-code
block, or when exporting fontified source-code with htmlize.

Thanks to Eric Schulte for a patch to this effect.

iswitchb support for many completion prompts
---------------------------------------------

This is enabled using `org-completion-use-iswitchb', and follows
the same model of usage as for ido users.

Thanks to John Wiegley for a patch to this effect.

New commands to set the effort property of an entry
----------------------------------------------------

There is now a special command, `C-c C-x e' to set the `Effort'
property of an entry.  From the agenda you can even use `e'.
If you have set up allowed values for the `Effort' property, then
using a prefix argument will directly select the nth allowed
value.  For example, in the agenda, `5 e' will select the 5th
allowed value.

This was a request by Michael Gilbert

Edit src works now better with killing buffers and exiting Emacs
----------------------------------------------------------------

Thanks to Dan Davison for a patch to this effect.

Bug fixes
---------

Thanks to Bastien for a umber of bug fixes.

Re: Release 6.30

[Sebastian Rose]

Hi Carsten,

thanks for another great release of my favorite mode!

> Allow LaTeX export to use the listings package

I will definitively test this one extensively :)
We always wanted to have this, but... Thanks Eric!

I hope to get rid of all that weired stuff I used to typeset source code
as seen in
http://orgmode.org/img/screenshots/vmap-org-export-to-pdf2.jpg


Best wishes

     Sebastian

Re: Release 6.30

[Bernt Hansen]

Carsten Dominik <carsten.dominik@gmail.com> writes:

> New command to submit a bug report
> -----------------------------------
>
> There is now a special command `M-x org-submit-bug-report'.  This
> command will create a mail buffer with lots of useful details.
> In particular, it contains complete version information for Emacs
> and Org-mode.  It will also (if you agree to it) contain all
> non-standard settings of org-mode and outline-mode related
> variables.  Even if you do not sent your emails from within
> Emacs, please still use this command to generate the information
> and then copy it into your mail program.
>
> The command will not generate and include a `*Backtrace*' buffer,
> please do this yourself if you have hit an error.  For more
> information, see the [feedback section] of the manual.
>
> [feedback section]: http://orgmode.org/manual/Feedback.html#Feedback
>

This is cool.  There's a minor typo in the mail text - patch follows.

-Bernt

[PATCH] Fix typo in org-submit-bug-report mail text

[Bernt Hansen]

---
This patch is available at git://git.norang.ca/org-mode for-carsten

 lisp/org.el |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index c851dc1..113925f 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -15493,7 +15493,7 @@ such private information before sending the email.")
 	 list))
      nil nil
      "Remember to cover the basics, that is, what you expected to happen and
-what in fact did happen.  You don't know hoe to make a good report?  See
+what in fact did happen.  You don't know how to make a good report?  See
 
      http://orgmode.org/manual/Feedback.html#Feedback
 
-- 
1.6.4.2.363.g2d6e

Re: Release 6.30

[Andrew Hyatt]

Hi Carsten,

Thanks for the release!  The dedicated frame patch does not actually
appear to be in this release, though.

On Tue, Sep 1, 2009 at 12:20 AM, Carsten
Dominik<carsten.dominik@gmail.com> wrote:
> Hi,
>
> I am releasing Org-mode version 6.30.
>
> Enjoy!
>
> - Carsten
>
>             Changes in Version 6.30
>             =======================
>
> Inconsistent changes
> ~~~~~~~~~~~~~~~~~~~~~
>
> Agenda now uses `f' and `b' to move through time
> =================================================
>
> Up to now, the Org-mode agenda used the cursor keys `left' and
> `right' to switch the agenda view forward an backward through
> time.  However, many people found this confusing, and others
> wanted to be able to do cursor motion in the agenda, for example
> to select text.  Therefore, after an extensive discussion on
> `emacs-orgmode@gnu.org', it was decided to use the `b' and
> `f' keys instead, and to let the cursor keys do cursor motion
> again.
>
> Agenda follow mode is now on the `F' key
> =========================================
>
> This was necessary to free up the `f' key, see above.
>
> Details
> ~~~~~~~~
>
> Maintenance
> ============
>
> New command to submit a bug report
> -----------------------------------
>
> There is now a special command `M-x org-submit-bug-report'.  This
> command will create a mail buffer with lots of useful details.
> In particular, it contains complete version information for Emacs
> and Org-mode.  It will also (if you agree to it) contain all
> non-standard settings of org-mode and outline-mode related
> variables.  Even if you do not sent your emails from within
> Emacs, please still use this command to generate the information
> and then copy it into your mail program.
>
> The command will not generate and include a `*Backtrace*' buffer,
> please do this yourself if you have hit an error.  For more
> information, see the [feedback section] of the manual.
>
> [feedback section]: http://orgmode.org/manual/Feedback.html#Feedback
>
> New contributed package org-track.el
> -------------------------------------
>
> This package allows to keep up-to-date with current Org
> development, using only Emacs on-board means.  So if you don't
> want or cannot use `git', but still want to run the latest and
> hottest Org-mode, this is for you.
>
> Thanks to Sebastian Rose for this contribution.
>
> Agenda
> =======
>
> Agenda now uses `f' and `b' to move through time
> -------------------------------------------------
>
> Up to now, the Org-mode agenda used the cursor keys `left' and
> `right' to switch the agenda view forward an backward through
> time.  However, many people found this confusing, and others
> wanted to be able to do cursor motion in the agenda, for example
> to select text.  Therefore, after an extensive discussion on
> `emacs-orgmode@gnu.org', it was decided to use the `b' and
> `f' keys instead, and to let the cursor keys do cursor motion
> again.
>
> Agenda follow mode is now on the `F' key
> -----------------------------------------
>
> This was necessary to free up the `f' key, see above.
>
> The agenda can be put into a dedicated frame
> ---------------------------------------------
>
> When the variable `org-agenda-window-setup' has the value
> `separate-frame', then the new frame created to show the agenda
> will now have the window marked as /dedicated/.  As a
> consequence, exiting the agenda while the agenda is the only
> window on the frame will kill that frame.
>
> This was a request by Henry Atting.
>
> New mode to show some entry body text in the agenda
> ----------------------------------------------------
>
> There is now a new agenda sub-mode called
> `org-agenda-entry-text-mode'.  It is toggled with the `E' key.
> When active, all entries in the agenda will be accompanied by a
> few lines from the outline entry.  The amount of text can be
> customized with the variable `org-agenda-entry-text-maxlines'.
>
> This was a request by Anthony Fairchild, Manish, and others.
>
> Improve following links from the agenda
> ----------------------------------------
>
> `C-c C-o' in the agenda will now offer all links in the headline
> and text of an entry.  If there is only a single link, it will be
> followed immediately.
>
> Avoid some duplicate entries
> -----------------------------
>
> There is a new variable that can be used to avoid some duplicate
> agenda entries: `org-agenda-skip-scheduled-if-deadline-is-shown'
> If that is set, it avoids that an entry shows up in the agenda for
> today for both a scheduling and a deadline entry.  See the
> docstring of the variables for more details.
>
> This partially addresses a request by Samuel Wales.
>
> Mark the running clock in the agenda.
> --------------------------------------
>
> If the entry currently being clocked is present in the agenda, it
> will be highlighted with the face `org-agenda-clocking'.
>
> This was a request by Rainer Stengele.
>
>
> Export
> =======
>
> Allow LaTeX export to use the listings package
> -----------------------------------------------
>
> The LaTeX `listings' package can now be used for formatting
> fontified source code in many programming languages.  For more
> information, see
> http://thread.gmane.org/gmane.emacs.orgmode/16269
> http://orgmode.org/worg/org-faq.php#fontified_source_code_w_latex
>
> Thanks to Eric Schulte for this patch.
>
> Remove table rows that only contain width and alignment markers
> ----------------------------------------------------------------
>
> The width and alignment in table columns can be set with a cookie
> like "<10>" or "<r>" or "<r10>".  In order to keep Org from
> exporting such lines, the first column of a line should contain
> only "/".  However, for convenience, there is now a special case:
> If the entire row contains only such markers, the line will
> automatically be discarded during export, even is the first
> column is not "/".
>
> Allow Macro calls to span several lines.
> -----------------------------------------
>
> Macro calls may now span several lines, to write several
> arguments in a cleaner way.  The result of a macro call can also
> span several lines, by inserting the string "\n" (backslash
> followed by n) into the value in the macro definition.
>
> These were requests by Stefan Vollmar.
>
> Misc
> =====
>
> Quick access to all links in an entry
> --------------------------------------
>
> If `C-c C-o' is called while the cursor is in a headline, but not
> directly on a link, then all links in the entry will be offered
> in a small menu.  If there is only a single link, it will be
> followed without a prompt.
>
> Visibility Cycling: Allow to show all empty lines after a headline
> -------------------------------------------------------------------
>
> `org-cycle-separator-lines' can now be set to a negative value,
> to indicate that, if the number of empty lines before a visible
> entry is greater than the specified number, then *all* empty
> lines should be shown.
>
> This was a request by "PT" whatever this means.
>
> Allow language names to replace some strange major mode names
> --------------------------------------------------------------
>
> Sometimes a language uses a major mode which can't be guessed
> from it's name.  There is now a new variable `org-src-lang-modes'
> which can be used to map language names to major modes when this
> is the case.  This is used when editing a source-code
> block, or when exporting fontified source-code with htmlize.
>
> Thanks to Eric Schulte for a patch to this effect.
>
> iswitchb support for many completion prompts
> ---------------------------------------------
>
> This is enabled using `org-completion-use-iswitchb', and follows
> the same model of usage as for ido users.
>
> Thanks to John Wiegley for a patch to this effect.
>
> New commands to set the effort property of an entry
> ----------------------------------------------------
>
> There is now a special command, `C-c C-x e' to set the `Effort'
> property of an entry.  From the agenda you can even use `e'.
> If you have set up allowed values for the `Effort' property, then
> using a prefix argument will directly select the nth allowed
> value.  For example, in the agenda, `5 e' will select the 5th
> allowed value.
>
> This was a request by Michael Gilbert
>
> Edit src works now better with killing buffers and exiting Emacs
> ----------------------------------------------------------------
>
> Thanks to Dan Davison for a patch to this effect.
>
> Bug fixes
> ---------
>
> Thanks to Bastien for a umber of bug fixes.
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

Re: Release 6.30

[Carsten Dominik]

Hi Andrew,

it is this commit:

bbc27c011ab5d44d37dca662d1a393d429dbe4b3

and it is part of the 6.30 release.  Maybe it only does not work?

Killing the frame does not work if the the agenda window is not
the only window on the frame.  So you could press "o", then "q".
Hmm, I guess I could check for the dedicated flag and
delete other windows before exiting the agenda.  OK, I am
doing this now.  Let me know if this fixes the issue.

- Carsten


On Sep 1, 2009, at 9:00 PM, Andrew Hyatt wrote:

> Hi Carsten,
>
> Thanks for the release!  The dedicated frame patch does not actually
> appear to be in this release, though.
>
> On Tue, Sep 1, 2009 at 12:20 AM, Carsten
> Dominik<carsten.dominik@gmail.com> wrote:
>> Hi,
>>
>> I am releasing Org-mode version 6.30.
>>
>> Enjoy!
>>
>> - Carsten
>>
>>             Changes in Version 6.30
>>             =======================
>>
>> Inconsistent changes
>> ~~~~~~~~~~~~~~~~~~~~~
>>
>> Agenda now uses `f' and `b' to move through time
>> =================================================
>>
>> Up to now, the Org-mode agenda used the cursor keys `left' and
>> `right' to switch the agenda view forward an backward through
>> time.  However, many people found this confusing, and others
>> wanted to be able to do cursor motion in the agenda, for example
>> to select text.  Therefore, after an extensive discussion on
>> `emacs-orgmode@gnu.org', it was decided to use the `b' and
>> `f' keys instead, and to let the cursor keys do cursor motion
>> again.
>>
>> Agenda follow mode is now on the `F' key
>> =========================================
>>
>> This was necessary to free up the `f' key, see above.
>>
>> Details
>> ~~~~~~~~
>>
>> Maintenance
>> ============
>>
>> New command to submit a bug report
>> -----------------------------------
>>
>> There is now a special command `M-x org-submit-bug-report'.  This
>> command will create a mail buffer with lots of useful details.
>> In particular, it contains complete version information for Emacs
>> and Org-mode.  It will also (if you agree to it) contain all
>> non-standard settings of org-mode and outline-mode related
>> variables.  Even if you do not sent your emails from within
>> Emacs, please still use this command to generate the information
>> and then copy it into your mail program.
>>
>> The command will not generate and include a `*Backtrace*' buffer,
>> please do this yourself if you have hit an error.  For more
>> information, see the [feedback section] of the manual.
>>
>> [feedback section]: http://orgmode.org/manual/Feedback.html#Feedback
>>
>> New contributed package org-track.el
>> -------------------------------------
>>
>> This package allows to keep up-to-date with current Org
>> development, using only Emacs on-board means.  So if you don't
>> want or cannot use `git', but still want to run the latest and
>> hottest Org-mode, this is for you.
>>
>> Thanks to Sebastian Rose for this contribution.
>>
>> Agenda
>> =======
>>
>> Agenda now uses `f' and `b' to move through time
>> -------------------------------------------------
>>
>> Up to now, the Org-mode agenda used the cursor keys `left' and
>> `right' to switch the agenda view forward an backward through
>> time.  However, many people found this confusing, and others
>> wanted to be able to do cursor motion in the agenda, for example
>> to select text.  Therefore, after an extensive discussion on
>> `emacs-orgmode@gnu.org', it was decided to use the `b' and
>> `f' keys instead, and to let the cursor keys do cursor motion
>> again.
>>
>> Agenda follow mode is now on the `F' key
>> -----------------------------------------
>>
>> This was necessary to free up the `f' key, see above.
>>
>> The agenda can be put into a dedicated frame
>> ---------------------------------------------
>>
>> When the variable `org-agenda-window-setup' has the value
>> `separate-frame', then the new frame created to show the agenda
>> will now have the window marked as /dedicated/.  As a
>> consequence, exiting the agenda while the agenda is the only
>> window on the frame will kill that frame.
>>
>> This was a request by Henry Atting.
>>
>> New mode to show some entry body text in the agenda
>> ----------------------------------------------------
>>
>> There is now a new agenda sub-mode called
>> `org-agenda-entry-text-mode'.  It is toggled with the `E' key.
>> When active, all entries in the agenda will be accompanied by a
>> few lines from the outline entry.  The amount of text can be
>> customized with the variable `org-agenda-entry-text-maxlines'.
>>
>> This was a request by Anthony Fairchild, Manish, and others.
>>
>> Improve following links from the agenda
>> ----------------------------------------
>>
>> `C-c C-o' in the agenda will now offer all links in the headline
>> and text of an entry.  If there is only a single link, it will be
>> followed immediately.
>>
>> Avoid some duplicate entries
>> -----------------------------
>>
>> There is a new variable that can be used to avoid some duplicate
>> agenda entries: `org-agenda-skip-scheduled-if-deadline-is-shown'
>> If that is set, it avoids that an entry shows up in the agenda for
>> today for both a scheduling and a deadline entry.  See the
>> docstring of the variables for more details.
>>
>> This partially addresses a request by Samuel Wales.
>>
>> Mark the running clock in the agenda.
>> --------------------------------------
>>
>> If the entry currently being clocked is present in the agenda, it
>> will be highlighted with the face `org-agenda-clocking'.
>>
>> This was a request by Rainer Stengele.
>>
>>
>> Export
>> =======
>>
>> Allow LaTeX export to use the listings package
>> -----------------------------------------------
>>
>> The LaTeX `listings' package can now be used for formatting
>> fontified source code in many programming languages.  For more
>> information, see
>> http://thread.gmane.org/gmane.emacs.orgmode/16269
>> http://orgmode.org/worg/org-faq.php#fontified_source_code_w_latex
>>
>> Thanks to Eric Schulte for this patch.
>>
>> Remove table rows that only contain width and alignment markers
>> ----------------------------------------------------------------
>>
>> The width and alignment in table columns can be set with a cookie
>> like "<10>" or "<r>" or "<r10>".  In order to keep Org from
>> exporting such lines, the first column of a line should contain
>> only "/".  However, for convenience, there is now a special case:
>> If the entire row contains only such markers, the line will
>> automatically be discarded during export, even is the first
>> column is not "/".
>>
>> Allow Macro calls to span several lines.
>> -----------------------------------------
>>
>> Macro calls may now span several lines, to write several
>> arguments in a cleaner way.  The result of a macro call can also
>> span several lines, by inserting the string "\n" (backslash
>> followed by n) into the value in the macro definition.
>>
>> These were requests by Stefan Vollmar.
>>
>> Misc
>> =====
>>
>> Quick access to all links in an entry
>> --------------------------------------
>>
>> If `C-c C-o' is called while the cursor is in a headline, but not
>> directly on a link, then all links in the entry will be offered
>> in a small menu.  If there is only a single link, it will be
>> followed without a prompt.
>>
>> Visibility Cycling: Allow to show all empty lines after a headline
>> -------------------------------------------------------------------
>>
>> `org-cycle-separator-lines' can now be set to a negative value,
>> to indicate that, if the number of empty lines before a visible
>> entry is greater than the specified number, then *all* empty
>> lines should be shown.
>>
>> This was a request by "PT" whatever this means.
>>
>> Allow language names to replace some strange major mode names
>> --------------------------------------------------------------
>>
>> Sometimes a language uses a major mode which can't be guessed
>> from it's name.  There is now a new variable `org-src-lang-modes'
>> which can be used to map language names to major modes when this
>> is the case.  This is used when editing a source-code
>> block, or when exporting fontified source-code with htmlize.
>>
>> Thanks to Eric Schulte for a patch to this effect.
>>
>> iswitchb support for many completion prompts
>> ---------------------------------------------
>>
>> This is enabled using `org-completion-use-iswitchb', and follows
>> the same model of usage as for ido users.
>>
>> Thanks to John Wiegley for a patch to this effect.
>>
>> New commands to set the effort property of an entry
>> ----------------------------------------------------
>>
>> There is now a special command, `C-c C-x e' to set the `Effort'
>> property of an entry.  From the agenda you can even use `e'.
>> If you have set up allowed values for the `Effort' property, then
>> using a prefix argument will directly select the nth allowed
>> value.  For example, in the agenda, `5 e' will select the 5th
>> allowed value.
>>
>> This was a request by Michael Gilbert
>>
>> Edit src works now better with killing buffers and exiting Emacs
>> ----------------------------------------------------------------
>>
>> Thanks to Dan Davison for a patch to this effect.
>>
>> Bug fixes
>> ---------
>>
>> Thanks to Bastien for a umber of bug fixes.
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>

Re: Release 6.30

[Tassilo Horn]

Carsten Dominik <carsten.dominik@gmail.com> writes:

> it is this commit:
>
> bbc27c011ab5d44d37dca662d1a393d429dbe4b3

That commit is in, but grepping for separate-frame in all *.el files
gives no result and the docs don't mention it, too.

,----[ C-h v org-agenda-window-setup RET ]
| org-agenda-window-setup is a variable defined in `org-agenda.el'.
| Its value is reorganize-frame
| 
| Documentation:
| How the agenda buffer should be displayed.
| Possible values for this option are:
| 
| current-window    Show agenda in the current window, keeping all other windows.
| other-frame       Use `switch-to-buffer-other-frame' to display agenda.
| other-window      Use `switch-to-buffer-other-window' to display agenda.
| reorganize-frame  Show only two windows on the current frame, the current
|                   window and the agenda.
| See also the variable `org-agenda-restore-windows-after-quit'.
`----

Looking at "git show bbc27c011ab5d44d37dca662d1a393d429dbe4b3" it seems
to me, that there's no new value, but that other-frame now uses a
dedicated window.

Bye,
Tassilo

Re: Re: Release 6.30

[Carsten Dominik]

On Sep 2, 2009, at 10:11 AM, Tassilo Horn wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> it is this commit:
>>
>> bbc27c011ab5d44d37dca662d1a393d429dbe4b3
>
> That commit is in, but grepping for separate-frame in all *.el files
> gives no result and the docs don't mention it, too.
>
> ,----[ C-h v org-agenda-window-setup RET ]
> | org-agenda-window-setup is a variable defined in `org-agenda.el'.
> | Its value is reorganize-frame
> |
> | Documentation:
> | How the agenda buffer should be displayed.
> | Possible values for this option are:
> |
> | current-window    Show agenda in the current window, keeping all  
> other windows.
> | other-frame       Use `switch-to-buffer-other-frame' to display  
> agenda.
> | other-window      Use `switch-to-buffer-other-window' to display  
> agenda.
> | reorganize-frame  Show only two windows on the current frame, the  
> current
> |                   window and the agenda.
> | See also the variable `org-agenda-restore-windows-after-quit'.
> `----
>
> Looking at "git show bbc27c011ab5d44d37dca662d1a393d429dbe4b3" it  
> seems
> to me, that there's no new value, but that other-frame now uses a
> dedicated window.

Yes, this seems to have been a typo in the release notes.  You need to  
use the value `other-frame'.

- Carsten

>
> Bye,
> Tassilo
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Release 6.30

[Andrew Hyatt]

Yep, that was my confusion.  Thanks!

On Wed, Sep 2, 2009 at 5:30 AM, Carsten
Dominik<carsten.dominik@gmail.com> wrote:
>
> On Sep 2, 2009, at 10:11 AM, Tassilo Horn wrote:
>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> it is this commit:
>>>
>>> bbc27c011ab5d44d37dca662d1a393d429dbe4b3
>>
>> That commit is in, but grepping for separate-frame in all *.el files
>> gives no result and the docs don't mention it, too.
>>
>> ,----[ C-h v org-agenda-window-setup RET ]
>> | org-agenda-window-setup is a variable defined in `org-agenda.el'.
>> | Its value is reorganize-frame
>> |
>> | Documentation:
>> | How the agenda buffer should be displayed.
>> | Possible values for this option are:
>> |
>> | current-window    Show agenda in the current window, keeping all other
>> windows.
>> | other-frame       Use `switch-to-buffer-other-frame' to display agenda.
>> | other-window      Use `switch-to-buffer-other-window' to display agenda.
>> | reorganize-frame  Show only two windows on the current frame, the
>> current
>> |                   window and the agenda.
>> | See also the variable `org-agenda-restore-windows-after-quit'.
>> `----
>>
>> Looking at "git show bbc27c011ab5d44d37dca662d1a393d429dbe4b3" it seems
>> to me, that there's no new value, but that other-frame now uses a
>> dedicated window.
>
> Yes, this seems to have been a typo in the release notes.  You need to use
> the value `other-frame'.
>
> - Carsten
>
>>
>> Bye,
>> Tassilo
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

Re: Release 6.30

[Rainer Stengele]

Hi Carsten,

Thanks for releasing all the new features!
It is amazing to see new features - which mostly make a lot of sense for 
me - coming up all the time.


Carsten Dominik schrieb:
> Hi,
> 
> I am releasing Org-mode version 6.30.
> 
> Enjoy!
> 
> - Carsten
> 
>              Changes in Version 6.30
>              =======================
> 
...
> 
> New mode to show some entry body text in the agenda
> ----------------------------------------------------
> 
> There is now a new agenda sub-mode called
> `org-agenda-entry-text-mode'.  It is toggled with the `E' key.
> When active, all entries in the agenda will be accompanied by a
> few lines from the outline entry.  The amount of text can be
> customized with the variable `org-agenda-entry-text-maxlines'.


this already avoids displaying drawer lines.
I also see lines like:

      - State "DONE"       from "WARTEN"     [2009-08-04 Di 16:19]
      - State "DONE"       from "WARTEN"     [2009-07-02 Do 09:43]
...

and in my remeber templates I always create lines like:

       created: [2009-08-03 Mo 11:46]

with the creation date of the entry.
Would it be possible and make sense to set up a variable for a regexp to 
exclude lines like the ones above from showing?

rainer

Re: Release 6.30

[Carsten Dominik]

Hi Rainer,

On Sep 4, 2009, at 12:03 PM, Rainer Stengele wrote:

> Hi Carsten,
>
> Thanks for releasing all the new features!
> It is amazing to see new features - which mostly make a lot of sense  
> for me - coming up all the time.
>
>
> Carsten Dominik schrieb:
>> Hi,
>> I am releasing Org-mode version 6.30.
>> Enjoy!
>> - Carsten
>>             Changes in Version 6.30
>>             =======================
> ...
>> New mode to show some entry body text in the agenda
>> ----------------------------------------------------
>> There is now a new agenda sub-mode called
>> `org-agenda-entry-text-mode'.  It is toggled with the `E' key.
>> When active, all entries in the agenda will be accompanied by a
>> few lines from the outline entry.  The amount of text can be
>> customized with the variable `org-agenda-entry-text-maxlines'.
>
>
> this already avoids displaying drawer lines.
> I also see lines like:
>
>     - State "DONE"       from "WARTEN"     [2009-08-04 Di 16:19]
>     - State "DONE"       from "WARTEN"     [2009-07-02 Do 09:43]
> ...
>
> and in my remeber templates I always create lines like:
>
>      created: [2009-08-03 Mo 11:46]
>
> with the creation date of the entry.
> Would it be possible and make sense to set up a variable for a  
> regexp to exclude lines like the ones above from showing?

Yes, I agree this would make sense.

There is now a variable and a hook for this purpose:

org-agenda-entry-text-exclude-regexps

org-agenda-entry-text-cleanup-hook


HTH

- Carsten


>
> rainer

Re: Release 6.30

[Rainer Stengele]

Hi Carsten,

excellent, thanks a lot!

I now have have started with this regexp:

...
  '(org-agenda-entry-text-exclude-regexps (quote ("^.*- State 
\"DONE\".*\n" "^.*erzeugt:.*\n")))
...


which works except in cases like these:

...
      - State "DONE"       [2008-02-24 So 20:52]
      - State "DONE"       [2008-02-24 So 20:52]
      erzeugt: [2008-01-12 Sa 21:40]
...

or

...
      - State "DONE"       [2008-02-24 So 20:51]
      - State "DONE"       [2008-02-24 So 20:51]
      - State "DONE"       [2008-02-24 So 20:51]
      - State "DONE"       [2008-02-24 So 20:51]
      - State "DONE"       [2008-02-24 So 20:50]
      - State "DONE"       [2008-02-24 So 20:50]
      erzeugt: [2008-01-12 Sa 21:40]
...


The agenda weeds out alle lines except the last line "erzeugt ...".


Rainer


Carsten Dominik schrieb:
> Hi Rainer,
> 
> On Sep 4, 2009, at 12:03 PM, Rainer Stengele wrote:
> 
>> Hi Carsten,
>>
>> Thanks for releasing all the new features!
>> It is amazing to see new features - which mostly make a lot of sense 
>> for me - coming up all the time.
>>
>>
>> Carsten Dominik schrieb:
>>> Hi,
>>> I am releasing Org-mode version 6.30.
>>> Enjoy!
>>> - Carsten
>>>             Changes in Version 6.30
>>>             =======================
>> ...
>>> New mode to show some entry body text in the agenda
>>> ----------------------------------------------------
>>> There is now a new agenda sub-mode called
>>> `org-agenda-entry-text-mode'.  It is toggled with the `E' key.
>>> When active, all entries in the agenda will be accompanied by a
>>> few lines from the outline entry.  The amount of text can be
>>> customized with the variable `org-agenda-entry-text-maxlines'.
>>
>>
>> this already avoids displaying drawer lines.
>> I also see lines like:
>>
>>     - State "DONE"       from "WARTEN"     [2009-08-04 Di 16:19]
>>     - State "DONE"       from "WARTEN"     [2009-07-02 Do 09:43]
>> ...
>>
>> and in my remeber templates I always create lines like:
>>
>>      created: [2009-08-03 Mo 11:46]
>>
>> with the creation date of the entry.
>> Would it be possible and make sense to set up a variable for a regexp 
>> to exclude lines like the ones above from showing?
> 
> Yes, I agree this would make sense.
> 
> There is now a variable and a hook for this purpose:
> 
> org-agenda-entry-text-exclude-regexps
> 
> org-agenda-entry-text-cleanup-hook
> 
> 
> HTH
> 
> - Carsten
> 
> 
>>
>> rainer
> 
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 

Re: Release 6.30

[Carsten Dominik]

Hi Rainer,

On Sep 5, 2009, at 4:08 PM, Rainer Stengele wrote:

> Hi Carsten,
>
> excellent, thanks a lot!
>
> I now have have started with this regexp:
>
> ...
> '(org-agenda-entry-text-exclude-regexps (quote ("^.*- State \"DONE 
> \".*\n" "^.*erzeugt:.*\n")))
> ...
>
>
> which works except in cases like these:
>
> ...
>     - State "DONE"       [2008-02-24 So 20:52]
>     - State "DONE"       [2008-02-24 So 20:52]
>     erzeugt: [2008-01-12 Sa 21:40]
> ...
>
> or
>
> ...
>     - State "DONE"       [2008-02-24 So 20:51]
>     - State "DONE"       [2008-02-24 So 20:51]
>     - State "DONE"       [2008-02-24 So 20:51]
>     - State "DONE"       [2008-02-24 So 20:51]
>     - State "DONE"       [2008-02-24 So 20:50]
>     - State "DONE"       [2008-02-24 So 20:50]
>     erzeugt: [2008-01-12 Sa 21:40]
> ...
>
>
> The agenda weeds out alle lines except the last line "erzeugt ...".

The reason for this was that the last line did not have a newline  
after it,
because that is being removed before the regular expressions are
applied.  I have changed this now, so that the \n is still present.
Another fix would have been to make the final newline optional by
adding "?" to the regexp.

- Carsten


>
>
> Rainer
>
>
> Carsten Dominik schrieb:
>> Hi Rainer,
>> On Sep 4, 2009, at 12:03 PM, Rainer Stengele wrote:
>>> Hi Carsten,
>>>
>>> Thanks for releasing all the new features!
>>> It is amazing to see new features - which mostly make a lot of  
>>> sense for me - coming up all the time.
>>>
>>>
>>> Carsten Dominik schrieb:
>>>> Hi,
>>>> I am releasing Org-mode version 6.30.
>>>> Enjoy!
>>>> - Carsten
>>>>            Changes in Version 6.30
>>>>            =======================
>>> ...
>>>> New mode to show some entry body text in the agenda
>>>> ----------------------------------------------------
>>>> There is now a new agenda sub-mode called
>>>> `org-agenda-entry-text-mode'.  It is toggled with the `E' key.
>>>> When active, all entries in the agenda will be accompanied by a
>>>> few lines from the outline entry.  The amount of text can be
>>>> customized with the variable `org-agenda-entry-text-maxlines'.
>>>
>>>
>>> this already avoids displaying drawer lines.
>>> I also see lines like:
>>>
>>>    - State "DONE"       from "WARTEN"     [2009-08-04 Di 16:19]
>>>    - State "DONE"       from "WARTEN"     [2009-07-02 Do 09:43]
>>> ...
>>>
>>> and in my remeber templates I always create lines like:
>>>
>>>     created: [2009-08-03 Mo 11:46]
>>>
>>> with the creation date of the entry.
>>> Would it be possible and make sense to set up a variable for a  
>>> regexp to exclude lines like the ones above from showing?
>> Yes, I agree this would make sense.
>> There is now a variable and a hook for this purpose:
>> org-agenda-entry-text-exclude-regexps
>> org-agenda-entry-text-cleanup-hook
>> HTH
>> - Carsten
>>>
>>> rainer
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

Re: Release 6.30

[Rainer Stengele]

Carsten Dominik schrieb:
> Hi Rainer,
> 
> On Sep 5, 2009, at 4:08 PM, Rainer Stengele wrote:
> 
>> Hi Carsten,
>>
>> excellent, thanks a lot!
>>
>> I now have have started with this regexp:
>>
>> ...
>> '(org-agenda-entry-text-exclude-regexps (quote ("^.*- State 
>> \"DONE\".*\n" "^.*erzeugt:.*\n")))
>> ...
>>
>>
>> which works except in cases like these:
>>
>> ...
>>     - State "DONE"       [2008-02-24 So 20:52]
>>     - State "DONE"       [2008-02-24 So 20:52]
>>     erzeugt: [2008-01-12 Sa 21:40]
>> ...
>>
>> or
>>
>> ...
>>     - State "DONE"       [2008-02-24 So 20:51]
>>     - State "DONE"       [2008-02-24 So 20:51]
>>     - State "DONE"       [2008-02-24 So 20:51]
>>     - State "DONE"       [2008-02-24 So 20:51]
>>     - State "DONE"       [2008-02-24 So 20:50]
>>     - State "DONE"       [2008-02-24 So 20:50]
>>     erzeugt: [2008-01-12 Sa 21:40]
>> ...
>>
>>
>> The agenda weeds out alle lines except the last line "erzeugt ...".
> 
> The reason for this was that the last line did not have a newline after it,
> because that is being removed before the regular expressions are
> applied.  I have changed this now, so that the \n is still present.
> Another fix would have been to make the final newline optional by
> adding "?" to the regexp.
> 
> - Carsten


Carsten, it works now!
Thanx for being the fastest maintainer I know at all!
It's plain fun to continue to see org getting "better" all the time.


- Rainer

Re: Release 6.30

[Rainer Stengele]

Carsten Dominik schrieb:

...

> 
> The reason for this was that the last line did not have a newline after it,
> because that is being removed before the regular expressions are
> applied.  I have changed this now, so that the \n is still present.
> Another fix would have been to make the final newline optional by
> adding "?" to the regexp.
> 
> - Carsten
> 
> 
>>

Hi Carsten,

sorry to come up again with this. I have lines in my org file like these 
(headlines only, no content):

******** TODO [#B] Heizungskeller: Abluftrohr einbauen
******** TODO [#B] Briefkasten abdichten mit transparentem Silikon
******** TODO [#B] Badewanne OG1 abdichten

Showing these in my agenda with the new "E" option results in:

******** TODO [#B] Heizungskeller: Abluftrohr einbauen
   > ******** TODO [#B] Briefkasten abdichten mit transparentem Silikon
******** TODO [#B] Briefkasten abdichten mit transparentem Silikon
   > ******** TODO [#B] Badewanne OG1 abdichten
******** TODO [#B] Badewanne OG1 abdichten

it looks like if there is no body line at all the next line appearing 
will be taken even if it is a headline.


- Rainer

Re: Release 6.30

[Carsten Dominik]

Fixed, thanks.

- Carsten

On Sep 6, 2009, at 8:58 PM, Rainer Stengele wrote:

> Carsten Dominik schrieb:
>
> ...
>
>> The reason for this was that the last line did not have a newline  
>> after it,
>> because that is being removed before the regular expressions are
>> applied.  I have changed this now, so that the \n is still present.
>> Another fix would have been to make the final newline optional by
>> adding "?" to the regexp.
>> - Carsten
>>>
>
> Hi Carsten,
>
> sorry to come up again with this. I have lines in my org file like  
> these (headlines only, no content):
>
> ******** TODO [#B] Heizungskeller: Abluftrohr einbauen
> ******** TODO [#B] Briefkasten abdichten mit transparentem Silikon
> ******** TODO [#B] Badewanne OG1 abdichten
>
> Showing these in my agenda with the new "E" option results in:
>
> ******** TODO [#B] Heizungskeller: Abluftrohr einbauen
>  > ******** TODO [#B] Briefkasten abdichten mit transparentem Silikon
> ******** TODO [#B] Briefkasten abdichten mit transparentem Silikon
>  > ******** TODO [#B] Badewanne OG1 abdichten
> ******** TODO [#B] Badewanne OG1 abdichten
>
> it looks like if there is no body line at all the next line  
> appearing will be taken even if it is a headline.
>
>
> - Rainer