Re: [O] agenda: past due deadlines *also* showing up under today's date

[Sébastien Delafond]

On 2017-03-07, Nicolas Goaziou  wrote:
>> On 2017-03-05, Nicolas Goaziou  wrote:
>>> I don't think so. Maybe we need to implement an equivalent to
>>> `org-scheduled-past-days' for deadlines.
>> [...]
>
> Done in master as `org-deadline-past-days'. Feedback welcome.

Hi Nicolas,

many thanks for the feature, it works exactly as needed. Kudos for the
impressive turnaround time on your end :)

Cheers,

--Seb

Re: [O] agenda: past due deadlines *also* showing up under today's date

[Sébastien Delafond]

On 2017-03-05, Nicolas Goaziou  wrote:
> I don't think so. Maybe we need to implement an equivalent to
> `org-scheduled-past-days' for deadlines.

That'd be awesome :) In the meantime, I'll try and see if migrating from
"deadline" to "scheduled" can sort of achieve the "cleaner" agenda I'm
looking for.

> AFAICT, the current behaviour looks correct.

No problem, I understand. Thanks for taking the time to look into my
report !

Cheers,

--Seb

[O] agenda: past due deadlines *also* showing up under today's date

[Sébastien Delafond]

Hello,

with 9.0.3, when using the timeline view of the agenda, I get a bunch of
"998 d. ago TODO [...]", "181 d. ago TODO [...]", etc entries under
today's date. 
They correspond to past DEADLINE'd tasks, that also each show up under
their respective deadline dates in that same timeline view. Note: this
is *not* where you tell me to complete these tasks in order to eliminate
the problem ;)

Is there any way at all to not have these entries clutter today's date
in the timeline, but instead *only* show up under their own date ? I've
experimented with a lot of the org-agenda-skip-* variables, but to no
avail so far.

I've also confirmed this didn't happen with 9.0, and in both cases I
started emacs with -q to make sure it wasn't my personal config
interfering.

Cheers,

--Seb

Re: [O] [PATCH] (fixed) ox-confluence.el: Do not generate filled paragraphs

[Sébastien Delafond]

On 2016-03-04, M. P. Ashton  wrote:
> I could make it unfill paragraphs, but I thought it might be useful
> to preserve line breaks.
>
> [...]
>
> Thanks for looking this over. Let me know what would be an acceptable
> change if any.

I've switched to exporting my Org documents to markdown before
including that in Confluence, so I'm not exactly maintaining
ox-confluence much, but anything that brings added functionality is of
course most welcome.

Cheers,

--Seb

[O] org-mime spurious alternative

[Sébastien Delafond]

Hello,

from Debian bug #751014 (http://bugs.debian.org/751014):

  When org-mime-library is set to semi, org-mime generates a spurious
  alternative section around the HTML part.  This is due to two bugs in
  the function org-mime-multipart:

  1. it attempts to put a multipart/alternative section around the HTML,
 where it should be putting a multipart/related part;

  2. it tests for the presence of images by doing (when images ...),
 which triggers when images is the empty string (somebody has been
 programming in Python or Javascript?).

  To repeat:

M-x load-library org-mime RET
M-: (setq org-mime-library 'semi) RET
M-x wl RET
w

  Then insert some text below the separator line, and do

M-x org-mime-htmlize

  and see the breakage.

Cheers,

--Seb

[O] Bug ? Normal lines interpreted as list items

[Sébastien Delafond]

Hi all,

a Debian user, reports[0] the following problem :

  When using Org within GNU Emacs, integers starting lines and followed
  by a period are interpreted as the first items of ordered lists, even
  when they are not.  Take, for instance, the following text in Org
  syntax and the corresponding part in a LaTeX export:

  Org text:
Bla bla bla, bla bl, bla bla bla, bla bla, bla bla bla,
1998.  Bla, bla bla bla bla, bla bla.  Bla bla bla bla bla bla, bla
bla bla, bla bla bla bla, bla bla.

  LaTeX export:
Bla bla bla, bla bl, bla bla bla, bla bla, bla bla bla,
\begin{enumerate}
\item Bla, bla bla bla bla, bla bla.  Bla bla bla bla bla bla, bla
\end{enumerate}
bla bla, bla bla bla bla, bla bla.

I see the same thing here with 8.2.1, and was wondering if this was
indeed a bug ?

Cheers,

--Seb

[0] https://bugs.debian.org/644238

[O] TODOs with repeat are not sorted correctly(?) in the agenda view

[Sébastien Delafond]

Hi fellows,

got the following bug report[1] from a Debian user:

  We have the 2012-12-23 Sun.  I have in my TODO.org file the entries

  * TODO reference entry
SCHEDULED: 2012-12-22 Sat
  * TODO test entry +
SCHEDULED: 2012-12-19 Wed +2d
  * TODO test entry ++
SCHEDULED: 2012-12-19 Wed ++2d
  * TODO test entry .+
SCHEDULED: 2012-12-19 Wed .+2d

  When I type 'Ctrl-c a a' the agenda view gets created (with the
  default sorting settings) as follows:

TODO:   Sched. 2x:  TODO reference entry
TODO:   Scheduled:  TODO test entry +
TODO:   Scheduled:  TODO test entry ++
TODO:   Scheduled:  TODO test entry .+

  This is not the result I expect.  The test entries are scheduled 3
  days more in the past than the reference entry.  Thus, I would expect
  them to come first with 'Sched. 5x:' in front.  I understand that due
  to the repeats, the test entries virtually appear also on the 21st and
  23rd, and that's why it is sorted that way.  The sorting takes the
  last virtual appearance rather than the one real appearance.  But that
  means, that entries that I should work on every second day never makes
  it to the top of the priority list, which renders the priority list in
  the agenda view useless, I think.  When I work on one of the test
  entries and cycle through TODO-DONE-TODO, the SCHEDULED date is
  automatically incremented and only then should the entry appear later
  in the list.  This is the most reasonable behavior, I think.  However,
  since there seem different oppinions on that issue possible, it would
  be great to have at least an option that would allow to pick the one
  or the other behavior.

(Please note that he is still using version 7.01g). I'll point the user
to this thread so he can tell us more if need be.

Cheers,

--Seb

[O] Export to Confluence wiki format

[Sébastien Delafond]

Hello,

I've put together a somewhat crude confluence exporter that's based on
the new exporter (as of 7.9.2). For now it's hosted on github[1].

I'm interested in feature requests (as it's only handling basic elements
for now), code style, and pretty much all feedback.

Cheers,

--Seb

[1] https://github.com/sdelafond/org-confluence

Re: [O] [bug] Export and tangle

[Sébastien Delafond]

On 2012-10-29, Myles English mylesengl...@gmail.com wrote:
 I just tried this with the git head and get the two files.  Of
 course, it doesn't rule out a problem with the version your user is
 using though.

Hello Myles,

thanks a lot for taking the time to test that out. I will package
7.9.2 to start with (hadn't noticed it was out), test against that,
and take it from there.

Cheers,

--Seb

[O] [bug] Export and tangle

[Sébastien Delafond]

Hi fellows,

just got the following bug report[0] from a Debian user:

  Typing C-c C-v t on the following file creates only bar.txt but not
  foo.txt as expected.  Does it matter whether BEGIN_SRC and END_SRC are
  written in small letters or not?

  The .. lines are not part of foo.org

  File foo.org
  #+BEGIN_SRC text :tangle foo.txt
  foo
  #+END_SRC

  #+begin_src text :tangle bar.txt
  bar
  #+end_src
  End of foo.org 

From my own experience BEGIN_SRC/END_SRC do not care whether they're
capitalized or not, but in this particular case it seems it's making a
difference. Any idea ?

Cheers,

--Seb

[0] http://bugs.debian.org/691505

Re: [O] Bug ? LaTeX exporter does not export subsections from included files

[Sébastien Delafond]

On 2012-10-08, Sébastien Delafond sdelaf...@gmail.com wrote:
 Since the update to org-mode 7.9.1-1, the LaTeX export does not work
 completely anymore with included files.

No idea at all on this one ? :)

Cheers,

--Seb

Re: [O] [wish] also provide documentation for contrib

[Sébastien Delafond]

On 2012-10-27, Bastien b...@altern.org wrote:
 I agree.  Let's start by patching README_contribute with a new
 section containing short documentation for contributions.

Hi Bastien,

I unfortunately have very little time these days to take on this task
:\ Hopefully this will change in the not-too-distant future...

Cordialement,

--SD

Re: [O] [wish] also provide documentation for contrib

[Sébastien Delafond]

On 2012-10-12, Thomas Koch tho...@koch.ro wrote:
 I know that org-drill has its own webpage with good
 documentation. The point is, that the Debian maintainer (or Fedora,
 Gentoo, ...) just takes the org- mode tarball and packages
 everything found in there. It would be an extra burden for the
 maintainer to go out to every single contrib site and somehow add
 the documentation in the package.

 It would be much easier IMHO, if the org-mode developers would not
 only distribute the code of contribs but also their documentation. I
 would even say that distributing code without documentation is kind
 of a bug.

 It would even be an extra advantage, if you could encourage the
 contrib developers to provide documentation in info format.

As the Debian maintainer for org-mode, I cannot agree more with
Thomas: since contrib is *distributed* in the regular org-mode
tarball, its documentation should be found in there as well.

Cheers,

--SD

[O] Bug ? LaTeX exporter does not export subsections from included files

[Sébastien Delafond]

Hi all,

a Debian user, on 7.9.1, reports[0] the following problem :

  Since the update to org-mode 7.9.1-1, the LaTeX export does not work
  completely anymore with included files. Please try exporting the
  attached testmain.org (for example to PDF via LaTeX with C-c C-e d).
  The included file testbar.org is included at the begining, but the
  subsections (**) are not exported.

  I've tried ODF and HTML export, which work as expected.

Here is his testmain.org:

  * Foo
  Here is foo!

  * Bar
  #+INCLUDE: testbar.org

  ** Bar 3
  This appears.

  * Conclusion 

And the corresponding testbar.org:

  This is Bar.

  ** Bar 1
  This is Bar's first part.

  ** Bar 2
  And here is the second one.

Cheers

--Seb

[0] http://bugs.debian.org/689428

Re: [O] Wrong indentation with auto-fill within lists ?

[Sébastien Delafond]

On 2012-08-20, Bastien b...@altern.org wrote:
 If you use a separate Org distribution (as a package or cloned from 
 the git repository), don't forget to create autoloads.

 ~$ make autoloads

 then

 (require 'org-install)

 in your .emacs.el should do.

(require 'org-install) is part of the packaging of org-mode in
Debian, and is loaded via a site-start snippet (in this case it's
/etc/emacs/site-start.d/50org-mode.el), so the problem shouldn't come
from that I think.

Cheers,

--Seb

[O] Wrong indentation with auto-fill within lists ?

[Sébastien Delafond]

Hi fellows,

do you feel this is an actual org-mode bug (reported in Debian,
#685348) ?

  When I start a list like
* List
   1. a very long item 1, so long that it reaches into the right margin
   2. item 2
  and I have auto-fill-mode turned on, the first item is split into two or more
  lines as
* List
   1. a very long item 1, so long that
it reaches into the right margin
   2. item 2
  The problem is that the second line of the first item is no longer part of the
  list! I expected the line to be split with additional spaces as
   * List
   1. a very long item 1, so long that
   it reaches into the right margin
   2. item 2
  so that item 1 is an ordinary item with two lines. This is annoying, as it is
  not easy (or I haven't found yet) a simple way to indent correctly that second
  line. A simple TAB doesn't work, so I have to move to the beginning of the
  line and add a couple of spaces. Furthermore, this used to work with emacs-23
  and its support for org-mode until I installed the package org-mode. (I
  installed the package to get the info documentation).

  Sorry if this is not a bug and this odd behavior can be configured away, but I
  couldn't find how.

Cheers,

--Seb

Re: [O] Bug: org-export-with-priority: t broken [7.8.11]

[Sébastien Delafond]

On 2012-08-18, Bastien b...@altern.org wrote:
 Fixed, thanks for the detailed report.

 Can someone in Debian close this bug?

I'll do that as soon as I package the next release to come.

Cheers,

--Seb

[O] icalendar export skips todos with a scheduled time-range

[Sébastien Delafond]

Hello,

From Debian bug #668496[0]:

  If I have an org-file containing a todo with a scheduled date range, like
  this:

  ,[ foo.org ]
*** TODO Weekend with the lads
SCHEDULED: 2012-05-04 Fr--2012-05-08 Di
  `

  and try to export it via org-export-icalendar-this-file, the resulting
  foo.ics will look like this

  ,[ foo.ics ]
BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:foo
PRODID:-//Friedrich Delgado//Emacs with Org-mode//EN
X-WR-TIMEZONE:Europe/Berlin
X-WR-CALDESC:nil
CALSCALE:GREGORIAN
END:VCALENDAR
  `

  (i.e.: contain no appointments at all)

  I think the responsible section of code may reside in
  /usr/share/emacs23/site-lisp/org-mode/org-icalendar.el, line 360:

  ,
(if (looking-at re2)
(progn
  (goto-char (match-end 0))
  (setq ts2 (match-string 1)
inc (not (string-match [0-9]\\{1,2\\}:[0-9][0-9] ts2
  (setq tmp (buffer-substring (max (point-min)
   (- pos org-ds-keyword-length))
  pos)
ts2 (if (string-match 
[0-9]\\{1,2\\}:[0-9][0-9]-\\([0-9]\\{1,2\\}:[0-9][0-9]\\) ts)
(progn
  (setq inc nil)
  (replace-match \\1 t nil ts))
  ts)
deadlinep (string-match org-deadline-regexp tmp)
scheduledp (string-match org-scheduled-regexp tmp)
todo (org-get-todo-state)
;; donep (org-entry-is-done-p)
))
  `

  From my basic understanding of the code-flow it looks like re2 ==
  (concat --?-?\\( org-ts-regexp \\)) is meant to match date-ranges,
  but the code in the t branch of the if doesn't set deadlinep,
  schedulep and todo, preventing all further processing of the entry.
  But I may be wrong about the intentions of that function.


Cheers,

--Seb

[0] http://bugs.debian.org/668496

[O] org-list-indent-offset only works partially

[Sébastien Delafond]

Hello,

from Debian bug #645214 (http://bugs.debian.org/645214):

  org-mode doesn't seems to honour correctly the org-list-indent-offset
  variable (a recent addition). See the following steps:

  1- Run emacs -q
  2- M-x org-mode 
  3- M-x set-variable org-list-indent-offset 8
  4- open /tmp/t.org
  5- Write the following
  - item 1
  [TAB]- item 2

  When you press [TAB], - item 2 is indented only two spaces right,
  not 8 as org-list-indent-offset describes, thats seems to be a
  bug. But now, if over the item 2 line you do

  6- M-left 
  7- M-right

  The - item 2 will be correctly indented 8 spaces to the right. So
  org-list-indent-offset is correctly working in this case.

There wasn't any patch provided by the submitter.

Cheers,

--Seb

[O] outline-demote incorrectly demotes leaf nodes

[Sébastien Delafond]

Hello,

from Debian bug #645360 (http://bugs.debian.org/645360):

  Here's my test file, call it c.org:

  * a
  ** aa
  *** aaa

  I put the cursor at the beginning of the file (at the * in the first
  line).  Then I type C-c C- (i.e. outline-demote).  The result is

  ** a
  *** aa
  ***  aaa

  I expected that the last line (the leaf node aaa) would become a
  fourth-level heading, i.e.  aaa.  Instead, the fourth * that I
  was hoping for looks like it became a space.

There wasn't any patch provided by the submitter.

Cheers,

--Seb 

Re: [O] outline-demote incorrectly demotes leaf nodes

[Sébastien Delafond]

On 2011-10-18, Bernt Hansen be...@norang.ca wrote:
 I agree that's not a valid bug and should be closed.

gotcha, will do. Christian  Bernt, thanks a lot for your input !

Cheers,

--Seb

[O] Exporting org-babel to HTML fails (uses copy-seq instead of copy-sequence in ob.el)

[Sébastien Delafond]

Hello,

From Debian bug #634695[0]:

  the babel part of org-mode uses copy-seq on line 758, where in fact, I
  think, it should be using copy-sequence. Or is there a valid reason for
  this? At least, it makes exporting org-mode documents to HTML impossible
  if they use babel features. That bug seems to be also present upstream
  (I checked commit ce2a33104b0e724b5227445cf5d5ceb240783870).

The following patch, contributed by the bug submitter, seems to fix it.

Cheers,

--Seb

--- org-mode-7.6.orig/lisp/ob.el
+++ org-mode-7.6/lisp/ob.el
@@ -755,7 +755,7 @@ the current subtree.
 lst)
 (norm (arg)
   (let ((v (if (listp (cdr arg))
-   (copy-seq (cdr arg))
+   (copy-sequence (cdr arg))
  (cdr arg
 (when (and v (not (and (sequencep v)
(not (consp v))

Re: [O] Exporting org-babel to HTML fails (uses copy-seq instead of copy-sequence in ob.el)

[Sébastien Delafond]

On 2011-07-22, Bastien b...@altern.org wrote:
 Eric already fixed this (although differently) in this commit:
   
 http://orgmode.org/w/?p=org-mode.git;a=commit;h=4b6bfab81741552697c4666488bcad00e33bc881

Ah sorry, I missed that ; thanks for following up :)

Cheers,

--Seb

[O] [export] Problem with '-{}-' export ?

[Sébastien Delafond]

Hello,

in both the PDF and HTML versions of the manual, in section 8.2.1, you
can read:

  You can specify a time range by giving start and end times or by
   giving a start time and a duration (in HH:MM format). Use `-' or
   `-{}-' as the separator

The correct output should instead mention:

  Use `-' or '--' as the separator

Maybe an export problem ?

For the record, this is Debian bug #632158[0].

Cheers,

--Seb

[0] http://bugs.debian.org/632158

Re: [O] [export] Problem with '-{}-' export ?

[Sébastien Delafond]

On 2011-07-05, Bastien b...@altern.org wrote:
 Thanks for reporting this -- I've just pushed a fix which
 doesn't use the dashes themselves as they are in the examples
 below the text.

Thank you !

 Can you close this bug report on Debian side?

I'll do so as soon as I upload to Debian the next release of org-mode
that will include this fix :)

--Seb

Re: [O] [patch] Do not run flyspell checks on org keywords

[Sébastien Delafond]

No one interested in this one ? :)

Cheers,

--Seb

On 2011-05-24, Sébastien Delafond sdelaf...@gmail.com wrote:

 Here is a small patch that prevents flyspelle from checking all the Org
 keywords. This is especially useful when using a dictionary other than
 english.

 Cheers,

 --Seb

 From 0a6493331f1d84a4c44533bdea1c3c9b41c997eb Mon Sep 17 00:00:00 2001
 From: =?UTF-8?q?S=C3=A9bastien=20Delafond?= sdelaf...@gmail.com
 Date: Mon, 23 May 2011 18:16:57 +0200
 Subject: [PATCH] [flyspell] Do not run flyspell-checks on 
 {todo,all-time,additional-option-like}-keywords

   * this is useful when using flyspell with a non-English dictionary,
 or if some of your keywords are in another language
 ---
  lisp/org.el |   12 +---
  1 files changed, 9 insertions(+), 3 deletions(-)

 diff --git a/lisp/org.el b/lisp/org.el
 index 9f8fa92..676f08f 100644
 --- a/lisp/org.el
 +++ b/lisp/org.el
 @@ -20135,9 +20135,15 @@ To get rid of the restriction, use 
 \\[org-agenda-remove-restriction-lock].
  
  ;; Make flyspell not check words in links, to not mess up our keymap
  (defun org-mode-flyspell-verify ()
 -  Don't let flyspell put overlays at active buttons.
 -  (and (not (get-text-property (max (1- (point)) (point-min)) 'keymap))
 -   (not (get-text-property (max (1- (point)) (point-min)) 
 'org-no-flyspell
 +  Don't let flyspell put overlays at active buttons, or on
 +   {todo,all-time,additional-option-like}-keywords.
 +  (let ((pos (max (1- (point)) (point-min)))
 + (word (thing-at-point 'word)))
 +(and (not (get-text-property pos 'keymap))
 +  (not (get-text-property pos 'org-no-flyspell))
 +  (not (member word org-todo-keywords-1))
 +  (not (member word org-all-time-keywords))
 +  (not (member word org-additional-option-like-keywords)
  
  (defun org-remove-flyspell-overlays-in (beg end)
Remove flyspell overlays in region.