Re: [Orgmode] Org-mode version 5.13

2007-12-30 Thread Adam Spiers
On Fri, Oct 19, 2007 at 08:25:18AM +0200, Carsten Dominik wrote:
> Changes in Version 5.13
> 
> 
> - `org-agenda-fontify-priorities' may now also be an
>   association list of priorities and faces, to specify the
>   faces of priorities in the agenda individually.

I finally got around to trying this, and I can't get the variable to
have any effect at all, whether it's set to t or to something like

  ((65 (:bold t :weight bold)))

Any ideas?


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


Re: [Orgmode] Org-mode version 5.13

2007-10-26 Thread Mike Newman
On Thu, 25 Oct 2007 16:12:36 +0500
"Dmitri Minaev" <[EMAIL PROTECTED]> wrote:


> Wouldn't classes make formatting more flexible? If I understand
> correctly, Mike Newman's proposal will require all formatting to be
> hardcoded into org.el? I'd rather keep it in a separate .css file, one
> for the whole site...
> 
> 
That is certainly not my intention.  I think keeping style information
in a separate file is a good idea.

-- 
Mike


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


Re: [Orgmode] Org-mode version 5.13

2007-10-25 Thread Dmitri Minaev
On 10/24/07, Carsten Dominik <[EMAIL PROTECTED]> wrote:
> So, does everybody agree that I should remove the class from the divs
> again?
>


Wouldn't classes make formatting more flexible? If I understand
correctly, Mike Newman's proposal will require all formatting to be
hardcoded into org.el? I'd rather keep it in a separate .css file, one
for the whole site...


-- 
With best regards,
Dmitri Minaev

Russian history blog: http://minaev.blogspot.com


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


Re: [Orgmode] Org-mode version 5.13

2007-10-24 Thread Carsten Dominik
So, does everybody agree that I should remove the class from the divs  
again?


- Carsten

On Oct 22, 2007, at 11:38 PM, Mike Newman wrote:


On Sat, 20 Oct 2007 11:30:29 +0100
Bastien <[EMAIL PROTECTED]> wrote:


Hello all,

Carsten Dominik <[EMAIL PROTECTED]> writes:


- The table of context is wrapped into a div with a class
  "table-of-contents".


This should be "id", not "class", since there is only one instance of
the table of contents - fixed in the proposed patch.


I think that class is the right thing here.  We are saying that  
this is

a "table-of-contents" rather than this is the "table-of-contents".  I
believe at present there is no mechanism to give more than one  
table of

contents, but someone, sometime might want tables of contents for
individual sections of a document.




- The outline structure is embedded in  elements with
  classes "outline-1", "outline-2" etc.


Classes are ok here.



This appears to be logical, but is in fact (I think) redundant.  We  
can

specify the style to applied at different levels without using
class attributes.  For example:

   div { background-color: lightgray}
   div > div { background-color: peachpuff}
   div > div > div { background-color: green}

shows how different styling can be applied to level 1, level 2 and
level 3 (and above).

I think this has advantages (e.g. inheritance of unspecified
characteristics from higher levels) and leaves the class attribute  
free

to represent styling that is independent of the structure.

--
Mike


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




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


Re: [Orgmode] Org-mode version 5.13

2007-10-23 Thread Carsten Dominik


On Oct 24, 2007, at 2:14 AM, Bastien wrote:


"Scott Jaderholm" <[EMAIL PROTECTED]> writes:


 - New variable `org-agenda-window-frame-fractions' to
   customize the size limits of the agenda window in the case
   that you display the agenda window by reorganizing the
   frame.

In org 5.12 when I do C-c a the Agenda Commands window that comes up
is only as tall as it needs to be. In 5.13 it is half the frame
height. I'm not sure exactly which change caused this.


`org-agenda-window-setup' or `org-agenda-window-frame-fractions' don't
change the way the Agenda Commands window is displayed.

I guess Carsten wanted the default size of windows to be the same for
the Agenda Commands window and for any agenda view.  But I think the
Agenda Commands window should be as small as possible since it's not
likely to change very often.


No, the reason was that due to the ability to have multiple keys  
leading to

a command, the window is displayed several times, and it is annoying
when it changes during a single command selection.  But I forgot
to get it small on the first key.  Fixed, thanks.

- Carsten





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


Re: [Orgmode] Org-mode version 5.13

2007-10-23 Thread Bastien
"Scott Jaderholm" <[EMAIL PROTECTED]> writes:

>  - New variable `org-agenda-window-frame-fractions' to
>customize the size limits of the agenda window in the case
>that you display the agenda window by reorganizing the
>frame.
>
> In org 5.12 when I do C-c a the Agenda Commands window that comes up
> is only as tall as it needs to be. In 5.13 it is half the frame
> height. I'm not sure exactly which change caused this.

`org-agenda-window-setup' or `org-agenda-window-frame-fractions' don't
change the way the Agenda Commands window is displayed.

I guess Carsten wanted the default size of windows to be the same for
the Agenda Commands window and for any agenda view.  But I think the
Agenda Commands window should be as small as possible since it's not
likely to change very often.

Here is a patch for this.

diff -u /home/guerry/elisp/testing/org/org.el /home/guerry/elisp/testing/bzg/org.el
--- /home/guerry/elisp/testing/org/org.el	2007-10-22 15:04:16.0 +0100
+++ /home/guerry/elisp/testing/bzg/org.el	2007-10-24 01:04:27.0 +0100
@@ -18339,9 +18339,7 @@
    "Prefix key"
 		prefixes))
 	  (goto-char (point-min))
-	  (if (and (fboundp 'fit-window-to-buffer)
-		   (not (pos-visible-in-window-p (point-max
-	  (fit-window-to-buffer))
+	  (if (fboundp 'fit-window-to-buffer) (fit-window-to-buffer))
 	  (message "Press key for agenda command%s:"
 		   (if restrict-ok
 		   (if restriction

Diff finished.  Wed Oct 24 01:04:41 2007

-- 
Bastien
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Org-mode version 5.13

2007-10-23 Thread Scott Jaderholm
On 10/19/07, Carsten Dominik <[EMAIL PROTECTED]> wrote:
>
>
> Changes in Version 5.13
> 
>
>  - New variable `org-agenda-window-frame-fractions' to
>customize the size limits of the agenda window in the case
>that you display the agenda window by reorganizing the
>frame.
>

In org 5.12 when I do C-c a the Agenda Commands window that comes up is only
as tall as it needs to be. In 5.13 it is half the frame height. I'm not sure
exactly which change caused this. Setting org-agenda-window-frame-fractions
to have a minimum of 0.1 doesn't make the agenda commands window any
smaller, as I think it only affects the Org Agenda window.

Thanks for another great release!

--Scott
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Org-mode version 5.13

2007-10-22 Thread Bastien
Mike Newman <[EMAIL PROTECTED]> writes:

> I think that class is the right thing here.  We are saying that this is
> a "table-of-contents" rather than this is the "table-of-contents".  I
> believe at present there is no mechanism to give more than one table of
> contents, but someone, sometime might want tables of contents for
> individual sections of a document.

Fair enough.  Let's say that "id" is okay for now (since the HTML
exporter doesn't know how to export multiple tables of contents), 
but this might become "class" when needed.

> This appears to be logical, but is in fact (I think) redundant.  We can
> specify the style to applied at different levels without using
> class attributes.  For example:
>
>div { background-color: lightgray}
>div > div { background-color: peachpuff}
>div > div > div { background-color: green}
>
> shows how different styling can be applied to level 1, level 2 and
> level 3 (and above).

So you suggest keeping the  tags, but stripping them out of their
"class" attributes? 

> I think this has advantages (e.g. inheritance of unspecified
> characteristics from higher levels) and leaves the class attribute
> free to represent styling that is independent of the structure.

Yes, I feel quite the same.

-- 
Bastien


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


Re: [Orgmode] Org-mode version 5.13

2007-10-22 Thread Mike Newman
On Sat, 20 Oct 2007 11:30:29 +0100
Bastien <[EMAIL PROTECTED]> wrote:

> Hello all,
> 
> Carsten Dominik <[EMAIL PROTECTED]> writes:
> 
> > - The table of context is wrapped into a div with a class
> >   "table-of-contents".
> 
> This should be "id", not "class", since there is only one instance of
> the table of contents - fixed in the proposed patch.

I think that class is the right thing here.  We are saying that this is
a "table-of-contents" rather than this is the "table-of-contents".  I
believe at present there is no mechanism to give more than one table of
contents, but someone, sometime might want tables of contents for
individual sections of a document.

> 
> > - The outline structure is embedded in  elements with
> >   classes "outline-1", "outline-2" etc.
> 
> Classes are ok here.
> 

This appears to be logical, but is in fact (I think) redundant.  We can
specify the style to applied at different levels without using
class attributes.  For example:

   div { background-color: lightgray}
   div > div { background-color: peachpuff}
   div > div > div { background-color: green}
   
shows how different styling can be applied to level 1, level 2 and
level 3 (and above).

I think this has advantages (e.g. inheritance of unspecified
characteristics from higher levels) and leaves the class attribute free
to represent styling that is independent of the structure.

-- 
Mike


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


Re: [Orgmode] Org-mode version 5.13

2007-10-20 Thread Bastien
Hello all,

Carsten Dominik <[EMAIL PROTECTED]> writes:

> - The table of context is wrapped into a div with a class
>   "table-of-contents".

This should be "id", not "class", since there is only one instance of
the table of contents - fixed in the proposed patch.

> - The outline structure is embedded in  elements with
>   classes "outline-1", "outline-2" etc.

Classes are ok here.

> - The postamble, containing the author information and the
>   date is wrapped into a div with class "postamble".

There was a small typo for the  of the postamble, this patch also
fixes it.

diff -u /home/guerry/elisp/testing/org/org.el /home/guerry/elisp/testing/bzg/org.el
--- /home/guerry/elisp/testing/org/org.el	2007-10-19 15:44:15.0 +0100
+++ /home/guerry/elisp/testing/bzg/org.el	2007-10-20 11:26:28.0 +0100
@@ -23830,7 +23830,7 @@
 
   (unless body-only
 	(when (plist-get opt-plist :auto-postamble)
-	  (insert "")
+	  (insert "")
 	  (when (and org-export-author-info author)
 	(insert " "
 		(nth 1 lang-words) ": " author "\n")
@@ -23866,7 +23866,7 @@
 	  (when (looking-at "\\s-*")
 	(goto-char (match-end 0))
 	(insert "\n")))
-	(insert "\n")
+	(insert "\n")
 	(mapc 'insert thetoc)
 	(insert "\n"))
   ;; remove empty paragraphs and lists

Diff finished.  Sat Oct 20 11:29:17 2007

-- 
Bastien
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode


Re: [Orgmode] Org-mode version 5.13

2007-10-19 Thread Eddward DeVilla
On 10/19/07, Adam Spiers <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 19, 2007 at 08:25:18AM +0200, Carsten Dominik wrote:
> > Hi everyone,
> >
> > I am releasing Org-mode version 5.13 at http://orgmode.org
> >- The agenda dispatcher
> >  + `<' cycles through restriction states.
> >  + Multi-character access codes to commands (= sub-keymaps).
>
> I can't believe you implemented this already; I'm struggling to think
> of superlatives to describe this quality of maintainership!

Ya.  Carsten is pretty good like that.

Edd


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


Re: [Orgmode] Org-mode version 5.13

2007-10-19 Thread Adam Spiers
On Fri, Oct 19, 2007 at 08:25:18AM +0200, Carsten Dominik wrote:
> Hi everyone,
> 
> I am releasing Org-mode version 5.13 at http://orgmode.org
>- The agenda dispatcher
>  + `<' cycles through restriction states.
>  + Multi-character access codes to commands (= sub-keymaps).

I can't believe you implemented this already; I'm struggling to think
of superlatives to describe this quality of maintainership!  Really
looking forward to testing it out, thanks a lot :-D


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


[Orgmode] Org-mode version 5.13

2007-10-18 Thread Carsten Dominik

Hi everyone,

I am releasing Org-mode version 5.13 at http://orgmode.org

This is a big release.  Except for severe bug fixes, the next
release will probably not be before the end of November.

Enjoy

- Carsten


Changes in Version 5.13


Overview


   - Bug fixes and improvements in column view
 + All known bugs fixed.
 + A Column view can be captured into a dynamic block.
 + The ITEM column is formatted core compactly.
 + Also ITEM can be edited with `e'

   - The agenda dispatcher
 + `<' cycles through restriction states.
 + Multi-character access codes to commands (= sub-keymaps).

   - Sorting improvements
 + User-defined sorting keys.
 + Sorting by properties.
 + Sorting of plain lists.

   - HTML  structure

   - Other stuff
 + New variables, several of them.
 + Drawers can be set on a per-file basis.
 + Better control over priority fontification in agenda.
 + M-up and M-down now move the current line up and down.
 + Abort remember template selection with C-g.

Details
===

Bug fixes and improvements in column view
-

- All the bugs described by Scott Jaderholm have been fixed
  (at least I hope so...).

- You can now capture a column view into a dynamic block, for
  exporting or printing it.  The column view can be

  + global, i.e. for the entire file
  + local, i.e. for the subtree where the dynamic block is
  + from an entry with a specific :ID: property.

  You can identify the entry whose column view you want to
  capture by assigning an :ID: property, and use that property
  in the dynamic block definition.  For example:

   * Planning
 :PROPERTIES:
   :ID: planning-overview
 :END:

   [...]

   * The column view
   #+BEGIN: columnview :hlines 1 :id "planning-overview"

   #+END:

  Use `C-c C-x r' to insert such a dynamic block, and you will
  be prompted for the ID.

- When the current column format displays the TODO keyword,
  priority or tags, these parts are stripped from the content
  of the ITEM column, making for more compact and readable
  entries.  When any of these "properties" are not listed in
  the current column format, they are instead retained in the
  ITEM column.

- You can now also edit the ITEM column with `e'.

The agenda dispatcher
-

- Instead of pressing `1' to restrict an agenda command to
  the current buffer, or `0' to restrict it to the current
  subtree or region, you can now also press `<' once or
  twice, respectively.  This frees up `1' and `0' for user
  commands, a request by Bastien.  In fact, "<" cycles
  through different restriction states.  "1" and "0" are
  still available for backward compatibility, until you bind
  them to custom commands.

- The access code to custom agenda commands can now contain
  several characters, effectively allowing to bundle several
  similar commands into a sub-keymap.  This follows an
  excellent proposal by Adam Spiers.  For example:

   (setq org-agenda-custom-commands
 '(("h" . "HOME + Name tag searches") ; describe prefix "h"
   ("hl" tags "+HOME+Lisa")
   ("hp" tags "+HOME+Peter")
   ("hk" tags "+HOME+Kim")))

- The user function option in org-agenda-custom-commands may
  now also be a lambda expression, following a request by
  Adam Spiers.

Sorting improvements


We are using a new routine for sorting entries, courtesy of
John Wiegley.  Many thanks to John.

- You can define your own function to extract a sorting key
  and in this way sort entries by anything you like.

- Entries can now be sorted according to the value of a
  property.

- Plain lists can be sorted.

HTML  structure


There is now a -based structure in exported HTML.

- The table of context is wrapped into a div with a class
  "table-of-contents".

- The outline structure is embedded in  elements with
  classes "outline-1", "outline-2" etc.

- The postamble, containing the author information and the
  date is wrapped into a div with class "postamble".

I am not sure if the class names are the best choice, let me
know if there are more "canonical" names we should use instead.

Thanks to Mike Newman and Cezar for input, and in particular
to Mike for his clearly formulated specification.

Other stuff
---

- New variable `org-agenda-window-frame-fractions' to
  customize the size limits of the agenda window in the case
  that you display the agenda window by reorganizing the
  frame.

- Drawers can be set on a per-file basis using

   #+DRAWERS: HIDDEN STATE PROPERTIES

  This will define the drawers :HIDDEN: and :STATE:.
  The :PROPERTY: dr