[O] org-agenda-show-log, org-timeline bugs
I tried running org-timeline on an Org file with lots of timestamped TODO -> DONE state changes, and didn't see the matches I was expecting. While poking around, I found two problems. 1. `org-timeline' isn't setting the text properties necessary to refresh the timeline buffer. This means that none of the special keys to update the display actually work. Here's the `org-timeline' version: (add-text-properties (point-min) (point-max) '(org-agenda-type timeline)) Here's the same chunk in `org-agenda-list' for comparison: (add-text-properties (point-min) (point-max) `(org-agenda-type agenda org-last-args (,arg ,start-day ,span) org-redo-cmd ,org-agenda-redo-command org-series-cmd ,org-cmd)) 2. Even when the `org-timeline' function has refresh set up properly, `org-agenda-log-mode' (via the `l' hotkey) doesn't work. It looks like the function changes the buffer-local copy of the `org-agenda-show-log' variable, but the refresh code looks at the global version of the variable (possibly because the refresh is happening through eval?). In order to see the log entries, you need to set `org-agenda-show-log' outside of the timeline buffer (using `setq'). Can someone take a look at these? This is all with the latest sources from the repo. Thanks. Derek -- Derek Upham s...@blarg.net
Re: [O] New exporter, beamer confusion
Suvayu Ali gmail.com> writes: > On Mon, Feb 04, 2013 at 12:00:08PM +0800, James Harkins wrote: > > #+OPTIONS: H:10 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t > > The H:10 is your problem. Since you want 2nd level headlines to be > frames, it should be H:2. Ah. OK, that's an improvement. Still a problem, though. The old exporter preserves the outline structure under the frame level, as nested bullet lists. The new exporter flattens them. * In: * Section A ** Slide 1 *** Third-level Fourth-level * Old exporter: Slide 1 --- - Third-level -- Fourth-level * New exporter: Slide 1 --- Third-level Fourth-level Should the new exporter change the appearance of my presentations so much? I'm hoping there's an option for this (as redoing the markup for 20 or more sets of class slides is... painful to contemplate). Thanks, hjh
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Nicolas! Great news and I'm really looking forward using the new exporter, but: > > 3. Export section from Org manual is now obsolete. It is being > rewritten, but until this task is completed, your best source of > information will still be the ML or the source files. > > I rely on orgmode for my homepage at work. If that stops just working without helping documentation that's "no good", at least for me ... Is there already a draft of docs available? One point to pull me over from vim to emacs was the fantastic documentation of orgmode. Now I'm sitting here a bit fearful of losing the great tool for an undetermined period of time. If there are no docs at all I, as a simple user, would suggest to postpone the release till after some usage notes are available. Alternatively keep the old exporter alive , please, till the new one has documentation. (or the migration path has documentation) Anyway thanks for all your work! Just 2c Detlef
[O] I have a problem about "Multi-state workflows "
I read the orgguide.pdf when I read page 11,I have a problem. I set some TODO keywords such as (setq org-todo-keywords '((sequence "TODO(t)" "|" "DONE(d)") (sequence "REPORT(r)" "BUG(b)" "KNOWNCAUSE(k)" "|" "FIXED(f)") (sequence "|" "CANCELED(c)"))) and it works,but I am confused about the following: To define TODO keywords that are valid only in a single file, use the following text anywhere in the file. #+TODO: TODO(t) | DONE(d) #+TODO: REPORT(r) BUG(b) KNOWNCAUSE(k) | FIXED(f) #+TODO: | CANCELED(c) but it does not work,can someone help me?
[O] beamer export - options vs. arguments
All,
I would like to have a literature list in my beamer presentation. As it is
longer than one slide, I would like to see something like something like
this
\begin[allowframebreaks]{frame}
\frametitle{Literature}
\bibliographystyle{plain}
\bibliography{References}
\end{frame}
in the exported tex file.
However, using envargs in org does not help, the frame option
"allowframebreaks" is neglected.
** Literature:B_frame:
:PROPERTIES:
:BEAMER_env: frame
:BEAMER_envargs: allowframebreaks
:END:
#+BEGIN_LaTeX
\bibliographystyle{plain}
\bibliography{References}
#+END_LaTeX
I found some discussion on the :beamer_envargs property, I understood that
the org structure does not entirely reflect the latex structure and this
may cause the problem.
So, I have two questions now:
1. Would it make sense to distinguish "arguments" (args) vs. "options" (as
they appear as [options] in latex?
2. How to overcome my problem with avoiding to have a frame environment as
source block in org mode?
Thanks
Jan-Mark
--
Jan-Mark Batke bad...@gmx.net
FON +49 511 33 64 800
FAX +49 511 22 09 521
Re: [O] LaTeX-export: letters after $..$ turn off math-mode
hi. this was on the list a year ago (see below).
i'd like to plead the case of allowing the user to suppress dollar-sign
behavior (or, force dollar-signs to mean math-mode).
the main reason is convenience: when trying to quickly write up
thoughts, typing "$ a = b^2 $" is just that much more convenient/easier
than typing "\( a = b^2 \)". (maybe because the former uses half the
number of "off-home-row" keys? maybe just because my fingers are
programmed to do this?)
second, (this is rhetoric) why privilege the dollar currency? third
(more rhetoric), there are certainly many communities that believe that
$..$ is equivalent to \(..\), so new users will continually show up thus
programmed.
so, if there were a way of disabling the current dollar sign processing,
that would be great!
cheers, Greg
http://lists.gnu.org/archive/html/emacs-orgmode/2012-02/msg00269.html
> Daniel Schoepe writes:
>> I have the following issue: If I write something like `$n$th' in an
>> org file and then export it to LaTeX, it will produce `\$n\$th',
>> whereas I would like it to export this as `$n$th'. Is there some way
>> I can disable escaping of dollar signs entirely (Leaving it to me to
>> escape them, when I don't use them as math-mode delimiters)?
> Using proper LaTeX math delimiters instead of that TeXism works
> nicely: \(n\)th (the other TeXism, $n${}th also doesn't work). In an
> UTF-8 document, a zero-width space would probably work too, but that's
> devious.
> HTH,
> Achim.
[O] [PATCH] Correctly align clock information in default time grid
Hello,
Here a tiny patch to correctly align clock info in the default time grid.
For example:
--8<---cut here---start->8---
Day-agenda (W06):
2013-02-04 Mon __
8:00..
Clk (1:05)9:03-10:08 TODO Organize work
10:00..
Clk (0:59) 10:08-11:07 DONE Do work for client A
Clk (1:24) 11:06-12:30 TODO Do other work for client B
12:00..
Clk (-) 13:34.. TODO Send patch to org-mode ML
13:49.. now
14:00..
--8<---cut here---end--->8---
Best regards,
Seb
>From ee8632ac6d68aebe1613bf3e190ee5616bfb19ee Mon Sep 17 00:00:00 2001
From: Sebastien Vauban
Date: Mon, 4 Feb 2013 13:47:54 +0100
Subject: [PATCH] Respect the 11-char default convention for %s info
* org-agenda.el (org-agenda-get-progress): By respecting the default
11-char convention for "Scheduling/Deadline information" (`%s' in
`org-agenda-prefix-format'), the clocked lines are perfectly aligned
in the time grid.
---
lisp/org-agenda.el |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index 2ce9f20..355a477 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -5813,7 +5813,7 @@ please use `org-class' instead."
(cond
(closedp "Closed:")
(statep (concat "State: (" state ")"))
- (t (concat "Clocked: (" clocked ")")))
+ (t (concat "Clk (" clocked ") ")))
txt level category tags timestr)))
(setq priority 10)
(org-add-props txt props
@@ -5853,7 +5853,7 @@ See also the user option
`org-agenda-clock-consistency-checks'."
'((:background "DarkRed") (:foreground "white"
issue face m te ts dt ov)
(goto-char (point-min))
-(while (re-search-forward " Clocked: +(-\\|\\([0-9]+:[0-9]+\\))" nil t)
+(while (re-search-forward " Clk (-\\|\\([0-9]+:[0-9]+\\)) " nil t)
(setq issue nil face def-face)
(catch 'next
(setq m (org-get-at-bol 'org-marker)
--
1.7.9
--
Sebastien Vauban
Re: [O] [ANN] Merge of new export framework on Wednesday
Nicolas Goaziou writes: > ━ > ANNOUNCING THE NEW EXPORT FRAMEWORK > ━ Thanks Nicolas, this is much appreciated. I have been looking forward to this for a long time. Perhaps we should set up a Worg TODO page for documentation? To make it easier to contribute bits. Thanks, Rasmus -- Vote for proprietary math!
Re: [O] [ANN] Merge of new export framework on Wednesday
Detlef Steuer writes: > Hi Nicolas! > > Great news and I'm really looking forward using the new exporter, but: > > >> >> 3. Export section from Org manual is now obsolete. It is being >> rewritten, but until this task is completed, your best source of >> information will still be the ML or the source files. >> >> > > I rely on orgmode for my homepage at work. If that stops just working > without helping documentation that's "no good", at least for me ... > > Is there already a draft of docs available? > > One point to pull me over from vim to emacs was the fantastic documentation of > orgmode. Now I'm sitting here a bit fearful of losing the great tool > for an undetermined period of time. > > If there are no docs at all I, as a simple user, would suggest to > postpone the release till after some usage notes are available. > > Alternatively keep the old exporter alive , please, till the new one > has documentation. (or the migration path has documentation) > > Anyway thanks for all your work! > > Just 2c > Detlef Hi Detlef, If you rely on org-mode for some production-level things, wouldn't it be most prudent to wait until the new exporter was shipped and fully tested before migrating your work setup? You'll still have all the documentation for the older version in the mean time, and once the new documentation is written, you'll be able to migrate with fewer problems. This is the whole principle that drives Debian, Debian-testing, and Debian-unstable. Dave
Re: [O] I have a problem about "Multi-state workflows "
Helong Feng writes: > I read the orgguide.pdf when I read page 11,I have a problem. > I set some TODO keywords such as > (setq org-todo-keywords > '((sequence "TODO(t)" "|" "DONE(d)") > (sequence "REPORT(r)" "BUG(b)" "KNOWNCAUSE(k)" "|" "FIXED(f)") > (sequence "|" "CANCELED(c)"))) > > and it works,but I am confused about the following: > To define TODO keywords that are valid only in a single file, use the > following text > anywhere in the file. > #+TODO: TODO(t) | DONE(d) > #+TODO: REPORT(r) BUG(b) KNOWNCAUSE(k) | FIXED(f) > #+TODO: | CANCELED(c) > but it does not work,can someone help me? If you've just typed this in, then you need to C-c C-c to refresh your setup. If you open a file with these lines, then Org should find them and set the keywords appropriately. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Macro question with new texinfo exporter
Nicolas Goaziou writes:
> Bastien writes:
>
>> Now back to the issue at hand, what about simply allowing to escape
>> the , and " characters? This was Thomas first try, and a natural one
>> I'd say.
>
> I have pushed a fix in maint for that. It should now be possible to use
> {{{kbd(C-\,)}}} to get "C-," as argument.
I need a bit more help with this. I created a tracking branch for
maint:
git branch --track maint origin/maint
Then, I checkout maint:
git checkout maint
Reloading Org yields these messages:
The following features were found in load-path, please check if that's correct:
(org-e-texinfo org-export)
Some error occured while reloading Org features
(ob-core ob-tcl)
Please check *Messages*!
Org-mode version 7.9.3e (7.9.3e @ /Users/dk/.emacs.d/src/org-mode/lisp/)
cond: Symbol's function definition is void: org-e-latex-export-to-latex
I'm stymied here. I'd like to be able to use the new macro code with
the new exporter. How is that possible?
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
Re: [O] Macro question with new texinfo exporter
Hi Thomas, t...@tsdye.com (Thomas S. Dye) writes: > I'm stymied here. I'd like to be able to use the new macro code with > the new exporter. How is that possible? You need to reload uncompiled files with C-u M-x org-reload RET BTW, I think it should be the defaut behavior of org-reload. Achim, any objection of making it the default, while C-u M-x org-reload RET would reload compiled files if any? -- Bastien
Re: [O] Macro question with new texinfo exporter
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>> Bastien writes:
>>
>>> Now back to the issue at hand, what about simply allowing to escape
>>> the , and " characters? This was Thomas first try, and a natural one
>>> I'd say.
>>
>> I have pushed a fix in maint for that. It should now be possible to use
>> {{{kbd(C-\,)}}} to get "C-," as argument.
>
> I need a bit more help with this. I created a tracking branch for
> maint:
>
> git branch --track maint origin/maint
>
> Then, I checkout maint:
>
> git checkout maint
>
> Reloading Org yields these messages:
>
> The following features were found in load-path, please check if that's
> correct:
> (org-e-texinfo org-export)
> Some error occured while reloading Org features
> (ob-core ob-tcl)
> Please check *Messages*!
> Org-mode version 7.9.3e (7.9.3e @ /Users/dk/.emacs.d/src/org-mode/lisp/)
> cond: Symbol's function definition is void: org-e-latex-export-to-latex
>
> I'm stymied here. I'd like to be able to use the new macro code with
> the new exporter. How is that possible?
The experimental exporter can be found in master branch. The maint
branch has a very old version which is unusable.
I pushed the fix to maint because it was about Elements, not directly
the exporter.
Regards,
--
Nicolas Goaziou
Re: [O] Macro question with new texinfo exporter
Thomas S. Dye writes: > Then, I checkout maint: > > git checkout maint I'm not sure what your starting point is, but you'd almost certainly will want to create the correct autoloads. In fact, you'd have a much better chance of this working correctly if you took the time (just once) to set up an install location and then just do a "make up2" or something similar whenever you want to update. > Reloading Org yields these messages: > > The following features were found in load-path, please check if that's > correct: > (org-e-texinfo org-export) So did you check that those features were found in the right place? > Some error occured while reloading Org features > (ob-core ob-tcl) > Please check *Messages*! What were those messages? And since the presence of both features indicates that you were previously on master, why did you switch to maint at all (everything on maint should have been merged into master)? > Org-mode version 7.9.3e (7.9.3e @ /Users/dk/.emacs.d/src/org-mode/lisp/) > cond: Symbol's function definition is void: org-e-latex-export-to-latex > > I'm stymied here. I'd like to be able to use the new macro code with > the new exporter. How is that possible? Just update master. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] Macro question with new texinfo exporter
Nicolas Goaziou writes: > > I pushed the fix to maint because it was about Elements, not directly > the exporter. Oh, I see now. You pushed the fix to maint, then merged branch 'maint' with master, so the fix is there as well. I didn't understand the workflow, so the reference to maint confused me. All the best, Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] Macro question with new texinfo exporter
Bastien writes: > You need to reload uncompiled files with C-u M-x org-reload RET I don't see the relation to the original problem, which is caused by a switch from master to maint. This will not work without at least unloading Org or better, restarting Emacs. > BTW, I think it should be the defaut behavior of org-reload. > > Achim, any objection of making it the default, while > C-u M-x org-reload RET would reload compiled files if any? I think that the current default, which has been in place for years, is just fine. Reloading uncompiled is only useful for when you want to create backtraces. If you always want to run uncompiled, then you can opt to never compile Org and org-reload will follow suit, if you clean up load-path to not contain older (compiled) Org distributions: --8<---cut here---start->8--- (setq load-path (delq nil (mapcar (lambda (p) (when (not (string-match "lisp/org$" p)) p)) load-path))) (add-to-list 'load-path "/path/to/uncompiled/org") (load "org-loaddefs.el" nil nil 'nosuffix) --8<---cut here---end--->8--- Of course you should not do this after Org has already been loaded. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] org-caldav issue: Search failed: ";\\([A-Za-z0-9-]+\\)="
David Engster writes: > Just FYI: Giles send me the offending calendar entry off-list and this > issue is fixed. Leaving me as a very happy bunny as I can now further reduce my excursions outside Emacs. And my thanks to David for a very rapid turn around. -- Giles Chamberlin
Re: [O] Macro question with new texinfo exporter
Aloha Achim, Achim Gratz writes: > > What were those messages? And since the presence of both features > indicates that you were previously on master, why did you switch to > maint at all (everything on maint should have been merged into master)? > >> Org-mode version 7.9.3e (7.9.3e @ /Users/dk/.emacs.d/src/org-mode/lisp/) >> cond: Symbol's function definition is void: org-e-latex-export-to-latex >> >> I'm stymied here. I'd like to be able to use the new macro code with >> the new exporter. How is that possible? > > Just update master. Thanks for looking into this. Yes, this was my confusion. I didn't understand that maint was merged with master. I thought Nicolas' reference to maint was an indication that I had to use the new code there. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] New exporter, beamer confusion
Hello, James Harkins writes: > Suvayu Ali gmail.com> writes: > >> On Mon, Feb 04, 2013 at 12:00:08PM +0800, James Harkins wrote: >> > #+OPTIONS: H:10 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t >> >> The H:10 is your problem. Since you want 2nd level headlines to be >> frames, it should be H:2. > > Ah. OK, that's an improvement. > > Still a problem, though. The old exporter preserves the outline structure > under > the frame level, as nested bullet lists. The new exporter flattens them. > > * In: > > * Section A > ** Slide 1 > *** Third-level > Fourth-level > > * Old exporter: > > Slide 1 > --- > - Third-level > -- Fourth-level > > * New exporter: > > Slide 1 > --- > Third-level > Fourth-level > > Should the new exporter change the appearance of my presentations so much? > I'm > hoping there's an option for this (as redoing the markup for 20 or more sets > of > class slides is... painful to contemplate). Here's an excerpt from ox-beamer.el documentation: ;; - Headlines become frames when their level is equal to ;; `org-beamer-frame-level' (or "H" value in the OPTIONS line). ;; Though, if an headline in the current tree has a "BEAMER_env" ;; (see below) property set to either "frame" or "fullframe", its ;; level overrides the variable. A "fullframe" is a frame with an ;; empty (ignored) title. ;; ;; - All frames' children become block environments. Special block ;; types can be enforced by setting headline's "BEAMER_env" property ;; to an appropriate value (see `org-beamer-environments-default' ;; for supported value and `org-beamer-environments-extra' for ;; adding more). In particular, "All frames children become block environments". So in your example Third-level is a block environment and Fourth-level is a block within it. There's no flattening going on (look at the tex file to convince yourself). Regards, -- Nicolas Goaziou
Re: [O] [ANN] Merge of new export framework on Wednesday
On Mon, Feb 04, 2013 at 08:49:28AM -0500, David Bjergaard wrote: > > Detlef Steuer writes: [...] > > If there are no docs at all I, as a simple user, would suggest to > > postpone the release till after some usage notes are available. > > > > Alternatively keep the old exporter alive , please, till the new one > > has documentation. (or the migration path has documentation) [...] > If you rely on org-mode for some production-level things, wouldn't it be > most prudent to wait until the new exporter was shipped and fully tested > before migrating your work setup? You'll still have all the > documentation for the older version in the mean time, and once the new > documentation is written, you'll be able to migrate with fewer > problems. > I would echo this sentiment. Org mode from master has no business in a production environment, just like any other software project. You can still keep using the latest stable release of Org (or even the tip of the maint branch) in production. And once everything is ready (including docs) for the new exporter, it will be released and possibly shipped with Emacs. You can easily switch then. Is there any particular reason for you to use master in production? Cheers, -- Suvayu Open source is the future. It sets us free.
[O] [PATCH] Add a different prefix for past deadlines in the agenda view
Hello,
Here's a patch to allow for a different prefix for deadline entries which are
in the past: for example, "3 d ago" instead of "In -3 d"...
Example:
--8<---cut here---start->8---
Day-agenda (W06):
2013-02-04 Mon __
8:00..
10:00..
12:00..
14:00..
16:00..
20:00..
22:42.. now
In 9 d.: TODO [#A] Do this
39 d. ago: STRT Should have done this for long already
--8<---cut here---end--->8---
Best regards,
Seb
>From 1eaf4433dd8800126dce4209045bb524553aae2a Mon Sep 17 00:00:00 2001
From: Sebastien Vauban
Date: Mon, 4 Feb 2013 22:49:47 +0100
Subject: [PATCH 2/2] Add a 3rd string for past deadlines
* org-agenda.el (org-agenda-get-deadlines): Add a 3rd string as the
preceding text when the deadline is already in the past.
---
lisp/org-agenda.el | 33 +
1 files changed, 21 insertions(+), 12 deletions(-)
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index 355a477..dd320c3 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -1626,12 +1626,13 @@ These entries are added to the agenda when pressing
\"[\"."
(string :tag "Scheduled today ")
(string :tag "Scheduled previously")))
-(defcustom org-agenda-deadline-leaders '("Deadline: " "In %3d d.: ")
+(defcustom org-agenda-deadline-leaders '("Deadline: " "In %3d d.: "
+"%-2d d. ago:")
"Text preceding deadline items in the agenda view.
-This is a list with two strings. The first applies when the item has its
-deadline on the current day. The second applies when it is in the past or
-in the future, it may contain %d to capture how many days away the deadline
-is (was)."
+This is a list with three strings. The first applies when the item has its
+deadline on the current day. The second and third apply when it is in the
+future or in the past, it may contain %d to capture how many days away the
+deadline is (was)."
:group 'org-agenda-line-format
:type '(list
(string :tag "Deadline today ")
@@ -6046,13 +6047,21 @@ See also the user option
`org-agenda-clock-consistency-checks'."
(setq txt (org-agenda-format-item
(if (= diff 0)
(car org-agenda-deadline-leaders)
- (if (functionp
- (nth 1 org-agenda-deadline-leaders))
- (funcall
- (nth 1 org-agenda-deadline-leaders)
- diff date)
-(format (nth 1 org-agenda-deadline-leaders)
-diff)))
+ (if (> diff 0)
+ (if (functionp
+ (nth 1 org-agenda-deadline-leaders))
+ (funcall
+ (nth 1 org-agenda-deadline-leaders)
+ diff date)
+(format (nth 1 org-agenda-deadline-leaders)
+diff))
+(if (functionp
+ (nth 2 org-agenda-deadline-leaders))
+(funcall
+ (nth 2 org-agenda-deadline-leaders)
+ (abs diff) date)
+ (format (nth 2 org-agenda-deadline-leaders)
+ (abs diff)
head level category tags
(if (not (= diff 0)) nil timestr)
(when txt
--
1.7.9
--
Sebastien Vauban
[O] tagging text, not headlines
I want to avoid over-headlining data. So in my playlist, I will list the songs as text, rather than as headlines. The problem is, I'd like to tag, in the following example, "(8) Beata Viscera" as my favorite composition in the Hilliard Ensemble performance. ** Classical *** Pérotin Description Pérotin (fl. c. 1200), also called Perotin the Great, was a European composer, believed to be French, who lived around the end of the 12th and beginning of the 13th century. He was the most famous member of the Notre Dame school of polyphony and the ars antiqua style. Performances * The Hilliard Ensemble (1) Viderunt Omnes (2) Veni Creator Spiritus (3) Alleluia Posui Adiutorium (4) O Maria Virginei (5) Dum Sigillum (6) Isalas Cecinit (7) Alleluia Nativitas (8) Beata Viscera (9) Sederunt Principes
Re: [O] Prefix arguments, checklists, and lists
Hello,
Robert Horn writes:
> Nicolas Goaziou writes:
>>
>> As a rule of thumb, C-c C-c on a list will operate on every top level
>> items and C-c C-c on a item will operate on the item. You are considered
>> to be on a list when calling C-c C-c from affiliated keywords or from
>> the very beginning of the first line in the first item. Note that
>> element-wise navigation (like M-{ and M-}) behaves the same.
>>
>
> This is different than your initial response, and still needs to be
> documented.
Certainly. Help is welcome, too.
> I still think it's poor user interface design. The impact when you go
> through the documentation for each command and add "... except when on
> the first character of the first item of the list, in which case the
> behavior is " may make this clear.
There's no point in adding it for each command. The list and item
boundaries just need to be defined once. Then, each command that behaves
differently on a list and on an item will have a documentation along the
lines of: "When at a list, do this. When at an item, do that."
> The user has to add that into their thought processes when using
> lists. This constant side nag of "where am I on this line? which item
> am I on?" is an indication of a user interface problem.
>
> The other times that emacs and org-mode care about where you are on the
> line are situations where you are directly editing and changing the
> contents of the line. It feels natural to pay attention to the location
> on the line when editing the text. And, even then, the change is
> restricted to that location on the line. It is only when using a
> prefixed commands that the changes affect other locations.
I think you are wrong. Org is all about context.
Think about speed commands: you have to be on the first character of
a headline to trigger them. Think about "M-RET": it will add a headline
before the current one if the point is at its very beginning. Think
about "C-c C-c". You hardly control it with prefixes: it acts according
to the location of point in the buffer.
I don't know if it's a user interface problem. I do like it, though. You
just have to _look_ for context, while you have to _think_ about the
right prefix to use. I must be faster at looking than at thinking,
I guess.
Anyway, to put it clearly, the syntax introduced in this situation
didn't come out of nowhere. It followed the same logic as the rest of
Org, really.
> That's why I prefer using a different prefix to mean "whole list". That
> leaves all of the list related commands that affect the current item to
> be C-u prefixed. If you have a different prefix that means "whole
> list", you eliminate the "where is the point?" mental effort. It adds
> the ability to have that different prefix enable "whole list" when on
> any item in any location in the list.
To really understand where it comes from, you have to forget about lists
for a while. You even have to forget about C-c C-c. Let's talk about
`org-forward-element' ("M-}") instead.
In the following example `org-forward-element' on the first paragraph
will move point on the second paragraph. All good and logical.
--8<---cut here---start->8---
This is the first paragraph
This is the second paragraph
--8<---cut here---end--->8---
If we add attributes to the first paragraph, as in the next example,
`org-forward-element' on the first paragraph (even on its attribute)
will unsurprisingly move point on the other one.
--8<---cut here---start->8---
#+NAME: para1
This is the first paragraph
This is the second paragraph
--8<---cut here---end--->8---
Now, we replace the first paragraph with a two-row table. If we stay
consistent, `org-forward-element' on the attribute line of the table
should move point on the paragraph, and so it does.
--8<---cut here---start->8---
#+NAME: table1
| a | b |
| c | d |
This is the second paragraph
--8<---cut here---end--->8---
But what if we remove that attribute line? Assuming point is on the
table's first row, should `org-forward-element' move it onto the next
paragraph or the second row?
--8<---cut here---start->8---
| a | b |
| c | d |
This is the second paragraph
--8<---cut here---end--->8---
We can move to the next row and add a prefix to "M-{", in order to skip
the whole table, much like what you suggest for lists. But what about
the table with the attribute line? There, an un-prefixed command will
still skip a table, or it won't be compliant with the example before it.
So what we really get is a prefixed command that behaves differently
according to context. In my book, it means we lose on both sides.
Now, let's look again at the same example, with point on the paragraph
this time.
--8<---
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Detlef and all, Detlef Steuer writes: > If there are no docs at all I, as a simple user, would suggest to > postpone the release till after some usage notes are available. > > Alternatively keep the old exporter alive , please, till the new one > has documentation. (or the migration path has documentation) To be clear (and I think Nicolas assumed it was clear), Org 8.0 will not be release until the documentation is fully updated. We will also make sure that Worg contains some useful tips to help with the migration, especially when it comes to use filters instead of hooks -- and on how to use old exporters that will live in contribs. For those tasks, any help on Worg will be more than welcome! -- Bastien
Re: [O] Quick comment on the website
Hi Dieter, Dieter Wilhelm writes: > For an uninitiated as me I felt the worg wiki a bit hidden, too humbly > placed in this nice and otherwise practical layout. Agreed, refreshing the Worg layout and promotion on orgmode.org is on my (big) TODO list. -- Bastien
Re: [O] [PATCH] Fix error handling deadline lead time specified in hours
Hi John, "John K. Luebs" writes: > From: "John K. Luebs" > > * lisp/org.el (org-get-wdays): Handle matching a lead time specified in > hours, which is matched by the current regexp but will erroneously > return nil. Applied, thanks. -- Bastien
Re: [O] Off for the next four days
Hi Christopher, Christopher Schmidt writes: > Would it be possible to set an announce-only mailing list up? Unless there is a high pressure for this, I will not make a separate list of announcements. But I will try to use [ANN] as a topic for the next release announcements, so that people can use filters if they want. -- Bastien
Re: [O] org-export-as-html-and-open problem
Hi Zhenjiang, zhenjiang xu writes: > when I type the keys `C-c C-e b', the html is generated but it is > opened in emacs instead of an internet browser. Does anyone know > why? Check the value of `org-file-apps'. C-h v org-file-apps RET Hope this helps, -- Bastien
Re: [O] org-export-as-html-and-open problem
Thanks, Bastien. It's the default value - I've not changed it:
org-file-apps is a variable defined in `org.el'.
Its value is ((auto-mode . emacs)
("\\.mm\\'" . default)
("\\.x?html?\\'" . default)
("\\.pdf\\'" . default))
On Mon, Feb 4, 2013 at 4:20 PM, Bastien wrote:
> Hi Zhenjiang,
>
> zhenjiang xu writes:
>
> > when I type the keys `C-c C-e b', the html is generated but it is
> > opened in emacs instead of an internet browser. Does anyone know
> > why?
>
> Check the value of `org-file-apps'.
>
> C-h v org-file-apps RET
>
> Hope this helps,
>
> --
> Bastien
>
Re: [O] org-export-as-html-and-open problem
zhenjiang xu writes:
> Thanks, Bastien. It's the default value - I've not changed it:
>
> org-file-apps is a variable defined in `org.el'.
> Its value is ((auto-mode . emacs)
> ("\\.mm\\'" . default)
> ("\\.x?html?\\'" . default)
> ("\\.pdf\\'" . default))
So you need to check the relevant variable:
org-file-apps-defaults-gnu
org-file-apps-defaults-macosx
org-file-apps-defaults-windowsnt
If the relevant variable uses the defaults (as I guess),
you need to configure the mailcap file for your system
See http://en.wikipedia.org/wiki/Mailcap
HTH,
--
Bastien
Re: [O] tagging text, not headlines
42 147 writes: > I want to avoid over-headlining data. > > So in my playlist, I will list the songs as text, rather than as > headlines. > The problem is, I'd like to tag, in the following example, "(8) Beata > Viscera" > as my favorite composition in the Hilliard Ensemble performance. > > ** Classical > *** Pérotin > Description > > Pérotin (fl. c. 1200), also called Perotin the Great, was a European > composer, believed to be French, who lived around the end of the 12th > and > beginning of the 13th century. He was the most famous member of the > Notre > Dame school of polyphony and the ars antiqua style. > Performances > * The Hilliard Ensemble > > (1) Viderunt Omnes > (2) Veni Creator Spiritus > (3) Alleluia Posui Adiutorium > (4) O Maria Virginei > (5) Dum Sigillum > (6) Isalas Cecinit > (7) Alleluia Nativitas > (8) Beata Viscera > (9) Sederunt Principes Tagging outside headlines doesn't really make sense in Org, as all tagging-related features need the tag to be on the headline. But you can still use... plain text + emacs power: (8) Beata Viscera <- My favorite song! M-x occur RET favorite RET HTH, -- Bastien
[O] viewing number of nested headlines
Is there a way to see how many nested headlines there are within a higher-level headline (not necessarily top-level)?
Re: [O] tagging text, not headlines
Sometimes I forget what org-mode is built on... It would be nice to keep things in the org-style (e.g., :favorite song: is preferable to "<--- favorite song," just on rudimentary aesthetic grounds. But what you suggested will do. 2013/2/4 Bastien > 42 147 writes: > > > I want to avoid over-headlining data. > > > > So in my playlist, I will list the songs as text, rather than as > > headlines. > > The problem is, I'd like to tag, in the following example, "(8) Beata > > Viscera" > > as my favorite composition in the Hilliard Ensemble performance. > > > > ** Classical > > *** Pérotin > > Description > > > > Pérotin (fl. c. 1200), also called Perotin the Great, was a European > > composer, believed to be French, who lived around the end of the 12th > > and > > beginning of the 13th century. He was the most famous member of the > > Notre > > Dame school of polyphony and the ars antiqua style. > > Performances > > * The Hilliard Ensemble > > > > (1) Viderunt Omnes > > (2) Veni Creator Spiritus > > (3) Alleluia Posui Adiutorium > > (4) O Maria Virginei > > (5) Dum Sigillum > > (6) Isalas Cecinit > > (7) Alleluia Nativitas > > (8) Beata Viscera > > (9) Sederunt Principes > > Tagging outside headlines doesn't really make sense in Org, > as all tagging-related features need the tag to be on the headline. > > But you can still use... plain text + emacs power: > > > (8) Beata Viscera <- My favorite song! > > M-x occur RET favorite RET > > HTH, > > -- > Bastien >
Re: [O] New exporter, beamer confusion
On Feb 5, 2013 3:51 AM, "Nicolas Goaziou" wrote: > In particular, "All frames children become block environments". So in > your example Third-level is a block environment and Fourth-level is > a block within it. There's no flattening going on (look at the tex file > to convince yourself). Thanks for pointing me to the comments in the .el source file. So here's my situation. I have a year's worth of lecture slides that render nicely using the old exporter. In the new exporter, the clear hierarchies of "enumerate" environments disappear, replaced by flat blocks. This new behavior is not useful to me. The comments in the source don't say anything about how I can modify the default "block" behavior. As a result, if the new exporter is fundamentally incompatible with the old and the only way is to insert properties by hand under every headline (across all of my files, I'd guess the count is in the high hundreds, if not >1000)... then the new beamer exporter is not useful to me. Is there an existing feature request for this? If not, would it help if I logged one? (Even if I didn't have existing files -- I like bullet points on slides, not flat text. I don't understand why I shouldn't be able to set that as a global or per-file preference.) I don't mean to be harsh. I'm glad for the new exporter and I'll use it for the next article I write. For beamer, though, currently it sounds like a lot of work to get a result that used to be easy. hjh
Re: [O] [ANN] Merge of new export framework on Wednesday
Suvayu Ali writes: [...] > I would echo this sentiment. Org mode from master has no business in a > production environment, just like any other software project. Although I agree, in principle, with this statement, life is not always so straightforward. I track org for my day to day use because I find some of the new features that appear quite useful. However, I do also rely on some form of stability for certain tasks. These are conflicting desires and I realise that this is *my* problem! However, I also am concerned at the move to the new exporter without documentation. This move appears premature if the documentation is not yet ready, not even in a draft form. I have been using the new exporter for many tasks but have not completely moved over for two: generation of beamer presentations and publishing of web pages. The latter is probably not a major issue for me but the former is. I simply have no idea how to convert my old org beamer files to the new exporter as there is no documentation at all. The source code (org-e-beamer.el) is of some help but not enough for me to know how to convert, in particular, slides with blocks and columns. Maybe it will be trivial to convert. However, I have been unsuccessful in finding anything on the mailing list that describes how to. This could be my fault in not searching properly, of course, so I would welcome any pointers to relevant emails. My solution will be to not update org until that documentation is available. Not a major problem but frustrating nonetheless. By the way, in case this email is taken the wrong way, I am in no way upset or angry! And I really appreciate all the work that has gone into the new exporter: it works brilliantly for those aspects that I have figured out and is a great step forward for org overall. Thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-897-g787a07
Re: [O] [PATCH] Correctly align clock information in default time grid
"Sebastien Vauban" writes: > Hello, > > Here a tiny patch to correctly align clock info in the default time grid. > > For example: > > Day-agenda (W06): > 2013-02-04 Mon __ >8:00.. > Clk (1:05)9:03-10:08 TODO Organize work > 10:00.. > Clk (0:59) 10:08-11:07 DONE Do work for client A > Clk (1:24) 11:06-12:30 TODO Do other work for client B > 12:00.. > Clk (-) 13:34.. TODO Send patch to org-mode ML > 13:49.. now > 14:00.. > > Best regards, > Seb Hi Seb, I'm not sure 'Clk' is more readable than 'Clocked' but it does align clock entries better. However state change logs suffer from a similar misalignment. I think a complete fix should correct the alignment for all of the items. Personally I don't mind the clock line misalignment - I think it's easier to read Clocked vs Clk. I think everything should be aligned or leave it as is. Regards, Bernt
Re: [O] [PATCH] Add a different prefix for past deadlines in the agenda view
Hi Sébastien, "Sebastien Vauban" writes: > Here's a patch to allow for a different prefix for deadline entries which are > in the past: for example, "3 d ago" instead of "In -3 d"... Please make sure the change is backward compatible so that users don't have to change the value of their `org-agenda-deadline-leaders' (i.e. simply fall back on (nth 1 ...) when (nth 2 ...) returns nil. Thanks, -- Bastien
Re: [O] [PATCH] Correctly align clock information in default time grid
Hi Sébastien, "Sebastien Vauban" writes: > Here a tiny patch to correctly align clock info in the default time > grid. For me the clock is shown like this: Week-agenda (W06): Monday 4 February 2013 W06 8:00.. 10:00.. General:10:20-11:00 Clocked: (0:40) DONE Test 1 12:00.. General:13:20-14:00 Clocked: (0:40) DONE Test 2 14:00.. 16:00.. General:16:20-16:40 Clocked: (0:20) DONE Test 2 18:00.. 20:00.. 23:46.. now - - - - - - - - - - - - - - - - - - - - - - - - - Did you configure any variable to get the clock at the beginning of the agenda entry? Thanks, -- Bastien
Re: [O] Opendocument problem
"Steve Prud'Homme" writes: > Hello, > I have emacs for cygwin and when I try to export I have a message that > emacs is unable to export a opendocument with the number 8 code(8). > Zip is intalled. > What is the problem ? Look at *Messages* buffer for the error string that zip or unzip prints. Make sure you have unzip as well, just in case... If you are unable to figure out yourself, just post what all gets spewed in to the messages buffer right from start of export to the end of export. I believe it is some simple setup issue. --
Re: [O] block quotes in prose?
I think an easy workaround would be to define block quotes as code blocks instead. putting the ":" as a prefix before a paragraph automatically fontifies it and places it in another color. This allows me to work in org-mode with visual highlighting of block quotes as desired. Now the question is: How do I make org-mode recognize the ">" prefix as a demarcator of a code block, so that my document remains readable as Markdown? Thanks! On Wed, Jan 23, 2013 at 12:03 AM, John Hendy wrote: > On Tue, Jan 22, 2013 at 6:13 PM, Peter Salazar > wrote: > > 1. What's the best way to demarcate block quotes in org-mode? I'd like a > way > > to demarcate them that makes it visually clear at a glance that it's a > block > > quote and not regular text. > > > > I would prefer not to have to put them inside #+BEGIN_QUOTE and > #+END_QUOTE > > references, because I'd rather not have any content in my buffer that > > distracts me from my actual writing. > > > > In Markdown-Mode, for instance, I just prefix a block quote with a > and > the > > line automatically changes color: > > > > http://i.imgur.com/AUsYJ.png > > > > Org-mode is infinitely more powerful than Markdown-Mode, so I'd just > like a > > way to work with lots of prose and block quotes in org-mode that will be > > easy and visually pleasing. I'm primarily concerned about how it appears > in > > the org-mode editor, not in export. > > > > Looking around, at least some of this appears defined in > /path/to/org-src/lisp/org-faces.el. > > I don't know enough elisp to tell you how to make Org treat "> > text..." the same as #+begin_quote. > > Perhaps you could figure out where the face change is for lines like > #+latex: and #+begin_src, as they both change the face of the text > immediately after (no need for an #+end_ command to tell Org to go > back to the default face). You might be able to add "^> text" to the > list of face-sensitive regexps to look for (using ^ as symbol for > beginning of line). > > ETA: after some more grepping, it looks like you could add something > in two places: > > 1) org-faces.el > > Search the file for "defface" and make a new face. I've not done this, > but you can definitely copy/yank some existing definitions and tweak > to your liking. > > 2) org.el > > Find a matching fontify function to see how the fontification is done. > They look pretty complicated... but perhaps it's possible to tweak one > to fontify "^> text...". > > Perhaps the easiest would be to find a face you like and just add "^> > text..." to the existing list of things org already fontifies with > that style. In other words, add "^> text" regexp to the existing hunt > for lines that start with #+ in order to get src code fontification > applied. > > > 2. It would also be cool to find a way to make bulleted lists appear in a > > different color if possible, or a workaround to simulate this. > > As in? > - item 1 > - item 2 > > I'm sure that's possible, too. Can't imagine this will become global, > but you could surely create your own git branch if you figure out how > or someone tells you how. > > > Good luck! > John > > > > > > Thanks! > > > > >
Re: [O] New exporter, beamer confusion
James Harkins wrote:
> On Feb 5, 2013 3:51 AM, "Nicolas Goaziou" wrote:
> > In particular, "All frames children become block environments". So in
> > your example Third-level is a block environment and Fourth-level is
> > a block within it. There's no flattening going on (look at the tex file
> > to convince yourself).
>
> Thanks for pointing me to the comments in the .el source file.
>
> So here's my situation. I have a year's worth of lecture slides that render
> nicely using the old
> exporter. In the new exporter, the clear hierarchies of "enumerate"
> environments disappear, replaced
> by flat blocks. This new behavior is not useful to me.
>
> The comments in the source don't say anything about how I can modify the
> default "block" behavior.
> As a result, if the new exporter is fundamentally incompatible with the old
> and the only way is to
> insert properties by hand under every headline (across all of my files, I'd
> guess the count is in
> the high hundreds, if not >1000)... then the new beamer exporter is not
> useful to me.
>
Customizing org-e-beamer-environments-extra should do the trick. I was
experimenting using the *scratch* buffer, so the following are temporary
settings, cribbed from those experiments: restart emacs and they
disappear.
Something like the following perhaps (very lightly tested - nb: I really
haven't played with the new exporter very much at all):
--8<---cut here---start->8---
(setq blockenv '("block" "b" "\\begin{itemize}\\item %h" "\\end{itemize}"))
(add-to-list 'org-e-beamer-environments-extra blockenv t)
--8<---cut here---end--->8---
I added a beamer entry to org-e-latex-classes as indicated in
http://thread.gmane.org/gmane.emacs.orgmode/61497/focus=61536
by just copying the article entry and modifying it slightly (again, I
have no idea if the sectioning stuff matters or not, and whether it leads
to problems - improvements/corrections would be welcome):
--8<---cut here---start->8---
(setq beamerclass '("beamer" "\\documentclass[11pt]{beamer}"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
(add-to-list 'org-e-latex-classes beamerclass t)
--8<---cut here---end--->8---
That's enough to export your ECM I think - no guarantees for
anything more complicated.
Nick
> Is there an existing feature request for this? If not, would it help if I
> logged one? (Even if I
> didn't have existing files -- I like bullet points on slides, not flat text.
> I don't understand why
> I shouldn't be able to set that as a global or per-file preference.)
>
> I don't mean to be harsh. I'm glad for the new exporter and I'll use it for
> the next article I
> write. For beamer, though, currently it sounds like a lot of work to get a
> result that used to be
> easy.
>
> hjh
>
>
>
> Alternatives:
>
>
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Eric, On Tue, Feb 05, 2013 at 11:37:35AM +1030, Eric S Fraga wrote: > > I have been using the new exporter for many tasks but have not > completely moved over for two: generation of beamer presentations and > publishing of web pages. The latter is probably not a major issue for > me but the former is. I simply have no idea how to convert my old org > beamer files to the new exporter as there is no documentation at > all. The source code (org-e-beamer.el) is of some help but not enough > for me to know how to convert, in particular, slides with blocks and > columns. > I have used the beamer export quite a few times with the new exporter, and I'm very pleased with it. I believe there is one backwards incompatible change, apart from that I think it's mostly feature enhancements. I have been trying to write some of the things down as a Worg article as preliminary documentation, but lately I have been incredibly busy to make any significant progress. I started from the old beamer tutorial as a template on how to structure it. Usually I also keep an eye out on the mailing list for questions related to the beamer export with the new exporter (although lately I have been much less active for the same reasons). Maybe I should put whatever I have on Worg so that others can work on it. I'll try to find some time in the coming two weeks. Hopefully this is a little reassuring. -- Suvayu Open source is the future. It sets us free.
