Re: [O] Org table with long lines visibility

[Johnny]

Michael Brand michael.ch.br...@gmail.com writes:
 As I understand, the issue tracker on Worg
 http://orgmode.org/worg/org-issues.html
 is thought also as a wish-list and you may add this with the keyword
 WISH there. But I wouldn't expect too much from doing only this. The
 best in many cases is to try to implement by oneself and ask for help
 here where necessary. And it's fun too. To start to understand I would
 single step with Edebug firstly TAB in a table, then C-c ` with
 C-c C-q and maybe also S-right on a reference after C-c ' on
 #+TBLFM.
Thanks for the pointers. I will keep this on my todo-list, but starting
from minimal experience with lisp and none in debugging in emacs, I
wouldn't hold my breath. At least, now I know where to start though,
which is quite a step in the right direction.

Regards,
-- 
Johnny

Re: [O] Firefox 4 in Ubuntu 11.04 and org-protocol

[Erik Hetzner]

At Sat, 07 May 2011 09:16:38 -0700,
Erik Hetzner wrote:
 Apparently they changed the way this works. You need to add a
 org-protocol.desktop file to ~/.local/share/applications
 
   [Desktop Entry]
   Name=org-protocol
   Exec=emacsclient %u
   Type=Application
   Terminal=false
   Categories=System;
   MimeType=x-scheme-handler/org-protocol;
 
 Then run:
 
   $ update-desktop-database .local/share/applications/
 
 For some reason I cannot get the bookmarklets to work, however. But
 opening an org-protocol:/ URL directly works.

Hi,

org-protocol bookmarks simply do not work for me in Firefox 4 on
Ubuntu 11.04 (they give an error message). Anybody have any luck
getting them to work? I can post more info if necessary.

best, Erik
Sent from my free software system http://fsf.org/.

[O] Orgmode and flyspell

[Marcelo de Moraes Serpa]

Hi guys,

I have activated flyspell-mode (using aspell under the hood) and while
the detection of spelling errors work OK, I can't get the mouse-2
functionality on org buffers. The org context menu comes instead. Does
anyone know how to deal with it?

Thanks,

Marcelo.

Re: [O] Orgmode and flyspell

[Nick Dokos]

Marcelo de Moraes Serpa celose...@gmail.com wrote:


 I have activated flyspell-mode (using aspell under the hood) and while
 the detection of spelling errors work OK, I can't get the mouse-2
 functionality on org buffers. The org context menu comes instead. Does
 anyone know how to deal with it?
 

Maybe you are binding mouse-2 explicitly somewhere? In my case,
down-mouse-2 is bound to mouse-yank-primary normally, except when
flyspell has detected an error, in which case it is bound to
flyspell-correct-word when on the incorrect word overlay (and C-h c
down-mouse-2 at that point says so.)

Nick

Re: [O] Orgmode and flyspell

[Marcelo de Moraes Serpa]

How can I bind contextually like you did (Only when flyspell finds an error)  ?

Thanks!



On Mon, May 9, 2011 at 3:19 PM, Nick Dokos nicholas.do...@hp.com wrote:
 Marcelo de Moraes Serpa celose...@gmail.com wrote:


 I have activated flyspell-mode (using aspell under the hood) and while
 the detection of spelling errors work OK, I can't get the mouse-2
 functionality on org buffers. The org context menu comes instead. Does
 anyone know how to deal with it?


 Maybe you are binding mouse-2 explicitly somewhere? In my case,
 down-mouse-2 is bound to mouse-yank-primary normally, except when
 flyspell has detected an error, in which case it is bound to
 flyspell-correct-word when on the incorrect word overlay (and C-h c
 down-mouse-2 at that point says so.)

 Nick

Re: [O] Orgmode and flyspell

[Michael Markert]

Hi,

On 9 May 2011, Marcelo de Moraes Serpa wrote:
 How can I bind contextually like you did (Only when flyspell finds an error) ?

flyspell does that on its own. Try hovering the mouse above a misspelled
word. In the lower right should appear a message like mouse-2: correct
word at point.

If that does not work: What flyspell/Emacs version do you use?

Michael

pgpnrH7wwJh40.pgp
Description: PGP signature

Re: [O] Orgmode and flyspell

[Marcelo de Moraes Serpa]

On Mon, May 9, 2011 at 3:37 PM, Michael Markert
markert.mich...@googlemail.com wrote:
 Hi,

 On 9 May 2011, Marcelo de Moraes Serpa wrote:
 How can I bind contextually like you did (Only when flyspell finds an error) 
 ?

 flyspell does that on its own. Try hovering the mouse above a misspelled
 word. In the lower right should appear a message like mouse-2: correct
 word at point.

 If that does not work: What flyspell/Emacs version do you use?

 Michael

Re: [O] Org table with long lines visibility

[Michael Brand]

Hi Johnny

On Mon, May 9, 2011 at 20:34, Johnny yggdra...@gmx.co.uk wrote:
 Thanks for the pointers. I will keep this on my todo-list, but starting
 from minimal experience with lisp and none in debugging in emacs

Ok, in this case one more pointer: For the first Edebug session I can
recommend the first and short chapter Using Edebug from
http://www.gnu.org/s/emacs/manual/html_node/elisp/Edebug.html
Then keep the other chapters for later reference.

Michael

Re: [O] Orgmode and flyspell

[Nick Dokos]

Michael Markert markert.mich...@googlemail.com wrote:

 Hi,
 
 On 9 May 2011, Marcelo de Moraes Serpa wrote:
  How can I bind contextually like you did (Only when flyspell finds an 
  error) ?
 
 flyspell does that on its own. Try hovering the mouse above a misspelled
 word. In the lower right should appear a message like mouse-2: correct
 word at point.
 
 If that does not work: What flyspell/Emacs version do you use?
 

What Michael said - if you want to see it, the binding is done in
make-flyspell-overlay.

Nick

[O] Date tree capture regexp for headline matching has changed.

[Charles Cave]

I use date-trees extensively for capturing Todo list items 
and appointments.

I noticed a change of behaviour between 7.4 and 7.5

In the date tree, I annotate the Monday date with a week number so
I can see the beginning of a week at a glance. for example:

*** 2011-05-09 Sunday
*** 2011-05-09 Monday  Week 19
 Note one
 Note two

Since version 7.5, if I add the Week 19 text, the next time
I do a capture, a new day heading is made. In version 7.4 and earlier
the headline matched from the beginning, but now it seems the entire
line is matched.

Why has this behaviour changed?

I consider this an unnecessary change / annoyance.  Can this
behaviour be changed back to the old way?  

Thank you
Charles 

Re: [O] Date tree capture regexp for headline matching has changed.

[Charles Cave]

I compared org-datetre.el from 7.4 to 7.5 and got the following
diff output (edited)

I can see that the regular expression has become more restricted
with the addition of  \\w+$  at the end.

At least I know what to manually change to make orgmode work the
way I want it.


105c105   (this is the org-datetree-find-day-create function 
7.4: (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\)[ \t\n] year 
month))
---
7.5: (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\) \\w+$ year month))

Re: [O] Date tree capture regexp for headline matching has changed.

[Bernt Hansen]

Charles Cave charles.c...@gmail.com writes:

 I compared org-datetre.el from 7.4 to 7.5 and got the following
 diff output (edited)

 I can see that the regular expression has become more restricted
 with the addition of  \\w+$  at the end.

 At least I know what to manually change to make orgmode work the
 way I want it.


 105c105   (this is the org-datetree-find-day-create function 
 7.4: (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\)[ \t\n] year 
 month))
 ---
 7.5: (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\) \\w+$ year 
 month))

Hi Charles,

According to git blame, this change was done in

,
| commit d9eeb15ab9d55316f08cd7efe818119bb7e5fc56
| Author: Bastien Guerry b...@altern.org
| Date:   Tue Feb 15 06:07:53 2011 +0100
| 
| Fix bug when jumping to a datetree from the agenda.
| 
| Datetree entries have a fixed form now:
| 
| * 2011
| ** 2011-02 monthname
| *** 2011-02-13 dayname
| 
| These headings will not be recognized as datetrees:
| 
| * 2011 A task for 2011
| ** 2011-02 several words
| *** 2011-02-13 several words
| 
| Thanks to Detlef Steuer for reporting this.
`

Regards,
Bernt

Re: [O] Date tree capture regexp for headline matching has changed.

[Nick Dokos]

Charles Cave charles.c...@gmail.com wrote:

 I compared org-datetre.el from 7.4 to 7.5 and got the following
 diff output (edited)
 
 I can see that the regular expression has become more restricted
 with the addition of  \\w+$  at the end.
 
 At least I know what to manually change to make orgmode work the
 way I want it.
 
 
 105c105   (this is the org-datetree-find-day-create function 
 7.4: (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\)[ \t\n] year 
 month))
 ---
 7.5: (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\) \\w+$ year 
 month))
 
 
 
 

Yes, but: there are two commits to org-datetree.el in the relevant time frame.

One was a fix in response to a bug report by you, so presumably
you want that fix - note that it touches the same regexp that you
identified above, but also note that there are similar regexps
that got modified in two other functions:


--8---cut here---start-8---
commit a6554b2fdf40e8e76abf08f9a0364f0de75fa78b
Author: Bastien Guerry b...@altern.org
Date:   Thu Feb 10 15:54:48 2011 +0100

Fix bug when creating datetree heading.

When a heading like

* 2011 Do this

existed, the creation of a datetree for the year 2011 didn't work,
as the 2011 Do this heading was mistaken for such a datetree.

This has been reported by Charles Cave.

diff --git a/lisp/org-datetree.el b/lisp/org-datetree.el
index 8014f8f..702b3a9 100644
--- a/lisp/org-datetree.el
+++ b/lisp/org-datetree.el
@@ -64,7 +64,7 @@ tree can be found.
   (goto-char (prog1 (point) (widen))
 
 (defun org-datetree-find-year-create (year)
-  (let ((re ^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t\n])
+  (let ((re ^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t]*$)
match)
 (goto-char (point-min))
 (while (and (setq match (re-search-forward re nil t))
@@ -83,7 +83,7 @@ tree can be found.
 
 (defun org-datetree-find-month-create (year month)
   (org-narrow-to-subtree)
-  (let ((re (format ^\\*+[ \t]+%d-\\([01][0-9]\\)[ \t\n] year))
+  (let ((re (format ^\\*+[ \t]+%d-\\([01][0-9]\\)[ \t]*$ year))
match)
 (goto-char (point-min))
 (while (and (setq match (re-search-forward re nil t))
@@ -102,7 +102,7 @@ tree can be found.
 
 (defun org-datetree-find-day-create (year month day)
   (org-narrow-to-subtree)
-  (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\)[ \t\n] year month))
+  (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\)[ \t]*$ year month))
match)
 (goto-char (point-min))
 (while (and (setq match (re-search-forward re nil t))
--8---cut here---end---8---


The second commit is probably the one that broke your setup - note
that it too touches all three regexps, so if you fix one and not the
others, you are probably going to end up with an inconsistent code
base. If you use git to keep up to date, you'd be better off reverting
this commit in a private branch (see

  
http://orgmode.org/worg/org-faq.html#keeping-local-changes-current-with-Org-mode-development

for information on how to keep current but still carry local changes):

--8---cut here---start-8---
commit d9eeb15ab9d55316f08cd7efe818119bb7e5fc56
Author: Bastien Guerry b...@altern.org
Date:   Tue Feb 15 06:07:53 2011 +0100

Fix bug when jumping to a datetree from the agenda.

Datetree entries have a fixed form now:

* 2011
** 2011-02 monthname
*** 2011-02-13 dayname

These headings will not be recognized as datetrees:

* 2011 A task for 2011
** 2011-02 several words
*** 2011-02-13 several words

Thanks to Detlef Steuer for reporting this.

diff --git a/lisp/org-datetree.el b/lisp/org-datetree.el
index 702b3a9..f0f1b90 100644
--- a/lisp/org-datetree.el
+++ b/lisp/org-datetree.el
@@ -64,7 +64,7 @@ tree can be found.
   (goto-char (prog1 (point) (widen))
 
 (defun org-datetree-find-year-create (year)
-  (let ((re ^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t]*$)
+  (let ((re ^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)$)
match)
 (goto-char (point-min))
 (while (and (setq match (re-search-forward re nil t))
@@ -83,7 +83,7 @@ tree can be found.
 
 (defun org-datetree-find-month-create (year month)
   (org-narrow-to-subtree)
-  (let ((re (format ^\\*+[ \t]+%d-\\([01][0-9]\\)[ \t]*$ year))
+  (let ((re (format ^\\*+[ \t]+%d-\\([01][0-9]\\) \\w+$ year))
match)
 (goto-char (point-min))
 (while (and (setq match (re-search-forward re nil t))
@@ -102,7 +102,7 @@ tree can be found.
 
 (defun org-datetree-find-day-create (year month day)
   (org-narrow-to-subtree)
-  (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\)[ \t]*$ year month))
+  (let ((re (format ^\\*+[ \t]+%d-%02d-\\([0123][0-9]\\) \\w+$ year month))
match)
 (goto-char (point-min))
 (while (and (setq match (re-search-forward re nil t))
--8---cut here---end---8---


Nick

Re: [O] Agenda clock report - show currently clocked task?

[Nathan Neff]

Thanks!

On Tue, Apr 26, 2011 at 2:56 PM, Bernt Hansen be...@norang.ca wrote:
 Nathan Neff nathan.n...@gmail.com writes:

 Does the clock report in the agenda exclude time spent in the
 currently clocked task?

 Is there a way to turn this on?

 org-clock-report-include-clocking-task

 -Bernt


 For example, I have 3 hours clocked in Task1, and I'm clocked into Task2
 for 1 hour:  My clock report in the agenda only shows the 3 hours in Task1.

 If I clock-out and refresh the agenda, then the clock report shows
 Task1 and Task2.

 Thanks,
 --Nate

Re: [O] Show current task in taskbar

[Nathan Neff]

Matt, this is most excellent.

I just have to run server-start from Emacs, and then I have a cron
job that runs every 30 seconds that updates the status bar.

Very cool.

Eric, I might use your method if I have trouble with emacs server or
something similar.

Thanks for both feedbacks -- this is really cool.

--Nate

On Mon, Apr 18, 2011 at 11:19 AM, Matt Lundin m...@imapmail.org wrote:
 Nathan Neff nathan.n...@gmail.com writes:

 Hello,

 I use wmii which is a minimalist tiling window manager.
 It has a taskbar that can show text/icons, etc.

 I'd like to see my currently logged in task on the taskbar.

 The way I see it, I could either 1) poll emacs for the current task

 Provided you have the emacs server running, you can access the task with
 the following:

 emacsclient -e org-clock-current-task

 Best,
 Matt

Re: [O] Date tree capture regexp for headline matching has changed.

[Nick Dokos]

Nick Dokos nicholas.do...@hp.com wrote:

 ... If you use git to keep up to date, you'd be better off reverting
 this commit in a private branch

Of course, that will expose you to the problem that Detlef ran into
which is discussed in the following thread[fn:1]:

  http://thread.gmane.org/gmane.emacs.orgmode/37663

Nick


Footnotes:

[fn:1]  Detlef mentions using the key sequence C-c a a i j
which I couldn't make work because I had the default setting
of org-agenda-diary-file. You need to set the latter to some
org file in order to make it work.

[O] Bug in latex export tutorial on worg ?

[Robert Goldman]

There is the following code block there:

#+begin_src emacs-lisp :results silent
  (add-to-list 'org-export-latex-classes
  '(per-file-class
 \\documentclass{scrartcl}
 [NO-DEFAULT-PACKAGES]
 [EXTRA]
 (\\section{%s} . \\section*{%s})
 (\\subsection{%s} . \\subsection*{%s})
 (\\subsubsection{%s} . \\subsubsection*{%s})
 (\\paragraph{%s} . \\paragraph*{%s})
 (\\subparagraph{%s} . \\subparagraph*{%s})))
#+end_src

Is this still correct?  Or should this be :exports none instead of
:results silent?

Cheers,
r

Re: [O] Bug in latex export tutorial on worg ?

[Nick Dokos]

Robert Goldman rpgold...@sift.info wrote:

 There is the following code block there:
 
 #+begin_src emacs-lisp :results silent
   (add-to-list 'org-export-latex-classes
   '(per-file-class
  \\documentclass{scrartcl}
  [NO-DEFAULT-PACKAGES]
  [EXTRA]
  (\\section{%s} . \\section*{%s})
  (\\subsection{%s} . \\subsection*{%s})
  (\\subsubsection{%s} . \\subsubsection*{%s})
  (\\paragraph{%s} . \\paragraph*{%s})
  (\\subparagraph{%s} . \\subparagraph*{%s})))
 #+end_src
 
 Is this still correct?  Or should this be :exports none instead of
 :results silent?
 

``:results silent'' works for me and keeps the result from appearing in
the org buffer. I don't think :exports can do that - it can only affect
what's exported.

Nick

Re: [O] Bug in latex export tutorial on worg ?

[Robert Goldman]

On 5/9/11 May 9 -11:22 PM, Nick Dokos wrote:
 Robert Goldman rpgold...@sift.info wrote:
 
 On 5/9/11 May 9 -9:54 PM, Nick Dokos wrote:
 Robert Goldman rpgold...@sift.info wrote:

 There is the following code block there:

 #+begin_src emacs-lisp :results silent
   (add-to-list 'org-export-latex-classes
   '(per-file-class
  \\documentclass{scrartcl}
  [NO-DEFAULT-PACKAGES]
  [EXTRA]
  (\\section{%s} . \\section*{%s})
  (\\subsection{%s} . \\subsection*{%s})
  (\\subsubsection{%s} . \\subsubsection*{%s})
  (\\paragraph{%s} . \\paragraph*{%s})
  (\\subparagraph{%s} . \\subparagraph*{%s})))
 #+end_src

 Is this still correct?  Or should this be :exports none instead of
 :results silent?


 ``:results silent'' works for me and keeps the result from appearing in
 the org buffer. I don't think :exports can do that - it can only affect
 what's exported.

 Nick

 I must be doing something wrong then --- I had the :results silent and
 found the source block in verbatim in my latex export file  Changing
 to :exports none made that go away for me.  Maybe that was a
 coincidence.  I will have to investigate further, I guess.

 
 No, you are not doing anything wrong: the default :exports value is
 code, so the code ends up in your export. ``:exports none'' keeps it
 (and any results) from being exported.
 
 OTOH, try evaluating (C-c C-c) the code block, with and without
 ``:results silent''. There is a behavior difference and *that* difference
 is not affected by how you set :exports.
 
 Nick

Ah.  I get it now.  But then surely the above IS a bug -- presumably
it's not usual for a person to wish their latex export configuration to
appear, in verbatim block, in their org-generated latex document!

Best,
Robert

Re: [O] Bug in latex export tutorial on worg ?

[Nick Dokos]

Robert Goldman rpgold...@sift.info wrote:

 Ah.  I get it now.  But then surely the above IS a bug -- presumably
 it's not usual for a person to wish their latex export configuration to
 appear, in verbatim block, in their org-generated latex document!
 

Perhaps not in most cases, but a tutorial has to do exactly that: how
else is it going to show the reader what needs to be done? Certainly
not by omitting the code that the reader is supposed to use.

Nick

Re: [O] Bug in latex export tutorial on worg ?

[Thomas S. Dye]

Robert Goldman rpgold...@sift.info writes:

 On 5/9/11 May 9 -11:22 PM, Nick Dokos wrote:
 Robert Goldman rpgold...@sift.info wrote:
 
 On 5/9/11 May 9 -9:54 PM, Nick Dokos wrote:
 Robert Goldman rpgold...@sift.info wrote:

 There is the following code block there:

 #+begin_src emacs-lisp :results silent
   (add-to-list 'org-export-latex-classes
   '(per-file-class
  \\documentclass{scrartcl}
  [NO-DEFAULT-PACKAGES]
  [EXTRA]
  (\\section{%s} . \\section*{%s})
  (\\subsection{%s} . \\subsection*{%s})
  (\\subsubsection{%s} . \\subsubsection*{%s})
  (\\paragraph{%s} . \\paragraph*{%s})
  (\\subparagraph{%s} . \\subparagraph*{%s})))
 #+end_src

 Is this still correct?  Or should this be :exports none instead of
 :results silent?


 ``:results silent'' works for me and keeps the result from appearing in
 the org buffer. I don't think :exports can do that - it can only affect
 what's exported.

 Nick

 I must be doing something wrong then --- I had the :results silent and
 found the source block in verbatim in my latex export file  Changing
 to :exports none made that go away for me.  Maybe that was a
 coincidence.  I will have to investigate further, I guess.

 
 No, you are not doing anything wrong: the default :exports value is
 code, so the code ends up in your export. ``:exports none'' keeps it
 (and any results) from being exported.
 
 OTOH, try evaluating (C-c C-c) the code block, with and without
 ``:results silent''. There is a behavior difference and *that* difference
 is not affected by how you set :exports.
 
 Nick

 Ah.  I get it now.  But then surely the above IS a bug -- presumably
 it's not usual for a person to wish their latex export configuration to
 appear, in verbatim block, in their org-generated latex document!

 Best,
 Robert




Aloha Robert,

I've added :exports none to the example, which came from a document
about how to export LaTeX documents from Org-mode.  Thanks for pointing
out that it could be used in a way that yields unexpected results.

In my usual setup I put this kind of configuration in a heading of its
own that is protected by a :noexport: tag.  This works for me because I
often have notes about why things are in there and what I think they
might be doing.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] Bug in latex export tutorial on worg ?

[Nick Dokos]

Nick Dokos nicholas.do...@hp.com wrote:

 Robert Goldman rpgold...@sift.info wrote:
 
  Ah.  I get it now.  But then surely the above IS a bug -- presumably
  it's not usual for a person to wish their latex export configuration to
  appear, in verbatim block, in their org-generated latex document!
  
 
 Perhaps not in most cases, but a tutorial has to do exactly that: how
 else is it going to show the reader what needs to be done? Certainly
 not by omitting the code that the reader is supposed to use.
 

After Tom's reply, I went and looked at the example and now I get it
too :-) Sorry for being dense before.

Nick