Re: [O] (no subject)

[Matt Price]

I'm replying a year late to this thread, post-merge, because I've
discovered it breaks interaction with the highlight.js library(
https://highlightjs.org/) and therefore my workflow, which depends on
highlightjs via reveal.js.

My difficulty is with the current version of ~org-html-do-format-code~,
which currently surrounds each loc with a ~~ tag and potentially some
classes:

(format "%s"
  (if num-start
  (format " data-ox-html-linenr=\"%s\"" line-num)
"")
  loc)



On Mon, Oct 15, 2018 at 4:07 AM Nik Clayton  wrote:

> Hi,
>
> I'd like to propose a couple of changes / enhancements to how org-export
> exports some data in to HTML files to make it slightly easier to style
> those files.
>
> The first is re line-numbers.
>
> At the moment those get exported as content in the HTML, although they're
> really additional metadata. Amongst other things, this means that if you
> copy/paste from the output you get the line numbers included in the text
> that's copied.
>
> CSS supports arbitrary counters that can be associated with content,
> starting from an arbitrary value. My current hack that sort of works is the
> following CSS:
>  .
> and a change to org-html-do-format-code to wrap each line in its own
> ... element:
>
> ...
>   ;; Transcoded src line.
>   (format "%s" loc)
> ...
>
> a) Does that sound reasonable?
> b) Should this replace the current approach, or be an option that can be
> toggled by a customisation?
>
> I agree that thisseems to make sense for many applications. But
highlight.js is a very widely-used highlighting library that expects
exactly one ~~ tag inside a given ~~ block. The additional
~~ tags  that org now generates on html export break highlight in
ways I don't believe can easily be fixed. I wonder if we could revisit the
idea of adding a user option that would allow this feature to be switched
off?  If this would be of general use I can prepare a patch.

Thanks,
Matt

Re: [O] (no subject)

[Nicolas Goaziou]

Hello,

Nik Clayton  writes:

> I'd like to propose a couple of changes / enhancements to how org-export
> exports some data in to HTML files to make it slightly easier to style
> those files.
>
> The first is re line-numbers.

[...]

> Couple of questions before I write a patch:
>
> a) Does that sound reasonable?
> b) Should this replace the current approach, or be an option that can be
> toggled by a customisation?

My HTML/CSS knowledge is feeble. But it does sound reasonable, if
there's no loss of feature and compatibility.

A patch would be nice for users exporting to HTML who want to test the
behaviour.

> And the second is re languages associated with exported SRC blocks.

[...]

> I see there's already some code that tries to show language badges on hover
> (which doesn't work for me for some reason, I haven't dug in to why).
>
> Does this change sound reasonable?

Ditto.

Regards,

-- 
Nicolas Goaziou

Re: [O] (no subject)

[Nicolas Goaziou]

Hello,

"Arne Babenhauserheide"  writes:

> Dear Org Hackers,
>
> When I use org-capture to capture a new task, the next headline
> sometimes ends up being prefixed by the last line of the new task.
>
> Example:
>
> Begin:
>
> * Foo
> ** old task
>
> * Bar
>
> After capture:
>
> * Foo
> ** old task
> ** ❢ new task
>:LOGBOOK:
>CLOCK: [2018-05-03 Do 14:05]--[2018-05-03 Do 15:24] =>  1:19
>:END:
>
> https://some.url/foo* Bar
>
>
> Best wishes,
> Arne Babenhauserheide
>
>
>
> Emacs  : GNU Emacs 25.2.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.21)
>  of 2017-09-22, modified by Debian
> Package: Org mode version 9.1.7 (9.1.7-12-g74f6ed-elpa @
>  /home/babenhauserheide/.emacs.d/elpa/org-20180305/)

Could you update Org mode and see if problem persists?

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] (no subject)

[Michael Welle]

Hello,

Bastien  writes:

> Dear Arne,
>
> there was a temporary glitch in earlier version of Org about this,
> please upgrade Org to 9.1.12 through the package system and let us
> know if you still have this issue.
oh, i thought that is a feature of some kind. Let me upgrade... Hm, the
feature|issue still exist in 9.1.12.

The issue occurs if the capture buffer isn't finished with a newline. My
workaround:

;;
;; Since some time Org does not prepend a \n after inserting
;; a capture template. We fix this ;).
;;
(defun hmw/org-insert-newline-after-template ()
  (goto-char (point-max))
  (if (not (re-search-backward "\\(^$\\)" (point-at-bol) t))
  (progn
(goto-char (point-max))
(insert "\n"

(setq org-capture-prepare-finalize-hook
  'hmw/org-insert-newline-after-template)

Regards
hmw

Re: [O] (no subject)

[steen]

FYI I am on org 9.1.4 and am still seeing this issue.

-- Steen


On Thu, May 3, 2018 at 2:26 PM Arne Babenhauserheide 
wrote:

> Dear Bastien,
>
> Thank you for your answer! I’ll check whether the update resolves this.
>
>
> (and I’m sorry for the empty subject, I copied the email from Emacs,
> since I do not have mail sending from emacs configured at work, and I
> forgot to copy the subject).
>
> Best wishes,
> Arne
>
> Bastien  writes:
>
> > Dear Arne,
> >
> > there was a temporary glitch in earlier version of Org about this,
> > please upgrade Org to 9.1.12 through the package system and let us
> > know if you still have this issue.
> >
> > Thanks!
>
>
> --
> Unpolitisch sein
> heißt politisch sein
> ohne es zu merken
>

Re: [O] (no subject)

[Arne Babenhauserheide]

Dear Bastien,

Thank you for your answer! I’ll check whether the update resolves this.


(and I’m sorry for the empty subject, I copied the email from Emacs,
since I do not have mail sending from emacs configured at work, and I
forgot to copy the subject).

Best wishes,
Arne

Bastien  writes:

> Dear Arne,
>
> there was a temporary glitch in earlier version of Org about this,
> please upgrade Org to 9.1.12 through the package system and let us
> know if you still have this issue.
>
> Thanks!


--
Unpolitisch sein
heißt politisch sein
ohne es zu merken


signature.asc
Description: PGP signature

Re: [O] (no subject)

[Bastien]

Dear Arne,

there was a temporary glitch in earlier version of Org about this,
please upgrade Org to 9.1.12 through the package system and let us
know if you still have this issue.

Thanks!

-- 
 Bastien

Re: [O] (no subject)

[Nicolas Goaziou]

Hello,

John Brodie  writes:

> I'm creating a literate program using org-babel with python. If I change
> the output of a source block to 'raw' the results are not replaced on
> each run, they are appended. This is quite annoying, because it means
> manual editing everytime I need to re-run my program.

You should use `drawer' instead of `raw' then. `raw' results cannot be
replaced, as you noticed, because there is no way to know where their
boundaries are.

Regards,

-- 
Nicolas Goaziou

Re: [O] (no subject)

[thomas]

you could revert to your working org installation (if you did not delete 
that folder)  by deleting / moving the folder with the faulty 
installation (say "org-201508XX") from your .emacs.d/elpa directory.


If this solves your problems, then I would recommend starting a "bare" 
emacs


 emacs -q

and install org from elpa again. A few days ago I ran into that same 
issue :-)


 - thomas


On 04.09.2015 16:51, Eduardo Mercovich wrote:

Hello everbody.

I'm an emacs/org-mode newbie but I'm learning, so please forgive me if
this is obvious for you.

A couple days ago I updated org from the packages-list.

Now, when I'm trying to use a simple org table (typing TAB, for
example), I get:
"org-get-limited-outline-regexp: Variable binding depth exceeds
max-specpdl-size"

Also, while trying to export a document to html, I get:
"Variable binding depth exceeds max-specpdl-size"

Looking up, I saw that this is a mechanisms to protect against infinite
recursions, so I tried to increase the limit -just to get the exporting
done- putting in my .emacs this:

(setq max-specpdl-size 15000)
(setq max-lisp-eval-depth 15000)

But, no luck.

Any pointer about what could be happening, or how to solve it?
Thanks a lot in advance... :)

Re: [O] (no subject)

[Eduardo Mercovich]

Dear Thomas. 

> you could revert to your working org installation (if you did not delete 
> that folder)  by deleting / moving the folder with the faulty 
> installation (say "org-201508XX") from your .emacs.d/elpa directory.
> If this solves your problems, then I would recommend starting a "bare" 
> emacs
>   emacs -q
> and install org from elpa again.

I did it, with some hiccups in the middle, and now I have a working
Org-mode version 8.3.1 (8.3.1-95-g1dbb25-elpaplus) 
in 
~/.emacs.d/elpa/org-20150831/

Thank you! :)

> A few days ago I ran into that same  issue :-)

Even while upgrading is not yet perfect, the packaging system is
becoming better by each version. 

As I'm not a bleeding edge developer, I may enjoy this version for a
while, but for those who may step on the same rock: 

1 . I uninstalled org from the package manager (M-x list-packages, there
mark with "D" and execute with "x")
2 . unloaded every org file (this is important, close all org buffers
before installation), 
3. . and installed again org from the package manager; 
4. . after, installed org-plus-contrib. 

Now it seems it's working fine, and I hope it may serve others too.
Don't forget to unload org buffers before install! (is upgrading the
same?).

Thanks a lot Thomas! :)

Best... 

-- 
e

Re: [O] (no subject)

[William Henney]

Hi Ryan

Convert to degrees, then multiply by 3600:

| - | - | - | 1@ 11' 37 | - | - | - | 4297 |
#+TBLFM: $8=3600 deg($4); %d

Cheers

Will



On Fri, May 2, 2014 at 8:52 PM, Ryan Moszynski ryan.moszyn...@gmail.comwrote:

 If an org table cell contains the HMS 1@ 11' 37

 is there an easy way to get the total (time)seconds?

 (1*3600 + 11*60 + 37 = 4297)


 if $4 =  1@ 11' 37

 how do I get $8 = 4297?

 thanks

 ryan

 --
 He felt that his whole life was some kind of dream and he sometimes
 wondered whose it was and whether they were enjoying it. - Douglas
 Adams




-- 

  Dr William Henney, Centro de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia

Re: [O] (no subject)

[William Henney]

Or, even better, just divide by the HMS form for 1 second (0@ 0' 1):

| - | - | - | 1@ 11' 37 | - | - | - | 4297 |
#+TBLFM: $8=$4 \ 0@ 0' 1

Note that \ is integer division, so there is no need for a format conversion

Will

P.S. I highly recommend reading the [[info:calc#Basic Arithmetic]] section
of the calc manual



On Fri, May 2, 2014 at 10:01 PM, William Henney when...@gmail.com wrote:

 Hi Ryan

 Convert to degrees, then multiply by 3600:

 | - | - | - | 1@ 11' 37 | - | - | - | 4297 |
 #+TBLFM: $8=3600 deg($4); %d

 Cheers

 Will



 On Fri, May 2, 2014 at 8:52 PM, Ryan Moszynski 
 ryan.moszyn...@gmail.comwrote:

 If an org table cell contains the HMS 1@ 11' 37

 is there an easy way to get the total (time)seconds?

 (1*3600 + 11*60 + 37 = 4297)


 if $4 =  1@ 11' 37

 how do I get $8 = 4297?

 thanks

 ryan

 --
 He felt that his whole life was some kind of dream and he sometimes
 wondered whose it was and whether they were enjoying it. - Douglas
 Adams




 --

   Dr William Henney, Centro de Radioastronomía y Astrofísica,
   Universidad Nacional Autónoma de México, Campus Morelia




-- 

  Dr William Henney, Centro de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia

Re: [O] (no subject)

[Marcin Borkowski]

Dnia 2014-01-31, o godz. 02:11:21
Nick Dokos ndo...@gmail.com napisał(a):

 John Hendy jw.he...@gmail.com writes:
 
  I'm having a tough time finding info on LaTeX with what makes a
  table left or right aligned (not the columns, but the table
  itself). Most of the hits are on how to *center* the table, which
  seems to suggest they will be left aligned by default.
 
 
 Does something like this help?

What about simply putting your tabular into \begin{flushright} ...
\end{flushright} (or -left, or center)?  You don't need floats for
that.  And if you /do/ need floats, just say \centering or \raggedright
or \raggedleft before your tabular.

Left aligned by default is connected with the boxes-and-glue model of
TeX page, and the way paragraph and page formatters work.  It is
described in detail in The TeXbook (in case you are curious).

HTH,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

Re: [O] (no subject)

[John Hendy]

On Thu, Jan 30, 2014 at 1:17 AM, Ken Okada keno.s...@gmail.com wrote:
 John,

 Thanks for advising.

 On Org 7.8.11, placement=[l] and placement={l} parameter does not make
 sense for tables as I tried.

 I tried to install the current version. (There was a compile error
 arising from the fact that BSD make is not GNU make, but it's no matter.)
 A simple example for :center nil works well. For main org file I have to
 do more work... not about centering.

If you're still running into the make issue, this is how I manage
Org-git on Windows since I don't want to futz with cygwin or other
stuff:
- http://orgmode.org/worg/org-hacks.html#compiling-org-without-make

 However there seems not to be a parameter for flush right. At present
 this is not a serious problem because :center nil works well, so we can
 control directory with #+LATEX: \begin ... and \end . But it's tiresome.

I was hunting around for the LaTeX parameter directly to specify the
table alignment and honestly wasn't finding anything specifically
related to tabular. My best hunting suggests that you need to put the
table inside of some sort of float environment and then specify the
placement that way, but I'm not sure if this plays nicely with any of
Org's built in table environments or not.

For example, I see there's a way to specify right alignment when
trying to wrap text around a figure:
- 
http://en.wikibooks.org/wiki/LaTeX/Floats,_Figures_and_Captions#Wrapping_text_around_figures

I was able to do this successfully with tabular instead of the example
they showed, but if you have no text to wrap, the table will just be
left-aligned.

\begin{wrapfigure}{r}{0.5\textwidth}
\begin{tabular}{lll}
a  b  c \\
\hline
word  word  word \\
word  word  word \\
\end{tabular}
\end{wrapfigure}

I also don't know how to next multiple environments with Org's
#+attr_latex options. I was able to place it inside wrap figure like
so:

#+attr_latex: :environment wrapfigure
| a| b| c|
|--+--+--|
| word | word | word |
| word | word | word |

But one still needs a \begin/end{tabular} wrapped around the table. I
tried the obvious =:environment wrapfigure tabular=, but this creates
the literal set of words inside \begin{} vs. separate environments.

That's the best I can do for now...


Good luck!
John


 I also feel something about the difference between the way to designate
 centering and flush left/right. For HTML export we use :align parameter;
 for LaTeX, :center parameter, which only allows us to control centering
 or not. :align parameter is used for alignment of contents of table.
 I'm confused. I guess there's a problem about backward compatibility or
 something.

 As you wrote there's a way to change default behaviour, but I feel
 centering is confortable in the most typesetting *with Org*.
 I think such searching result is due to the default behaviour of LaTeX.
 File local option switching the behaviour would be useful, I think.

 Best regards,
 Ken Okada


 At Wed, 29 Jan 2014 18:22:38 -0600,
 John Hendy wrote:

 On Wed, Jan 29, 2014 at 6:15 PM, Bastien b...@gnu.org wrote:
 
  Hi Ken,
 
  Ken Okada keno.s...@gmail.com writes:
 
   I have a question. By default tables are centered in LaTeX export.
   Sometimes I prefere to make it flush left or right. I thought this was
   done with, for example,
  
   #+ATTR_LATEX: :center nil
   | a | b |
   | 1 | 2 |
 
  The use of the :center parameter suggests you consulted a recent
  version of the documentation, for Org =8.0.
 
  This is how it works for Org 8.0 and above:
 
  #+ATTR_LATEX: :environment longtable :align l|lp{3cm}r|l
  | a | b | c |
  | 1 | 2 | 3 |
 
  If you can, please upgrade.  Otherwise, someone needs to check the
  documentation for Org 7.8.11...

 Bastien beat me to it. Yes, the example syntax is for Org  8.0.
 Here's a version of the manual for v7.9:
 - 
 http://www.gnu.org/software/emacs/manual/html_mono/org.html#Tables-in-LaTeX-export

 I'm not sure what the proper argument is and can't test since I'm on
 the current version of Org from git. You might take a look at the
 placement= argument?

 I'm having a tough time finding info on LaTeX with what makes a table
 left or right aligned (not the columns, but the table itself). Most of
 the hits are on how to *center* the table, which seems to suggest they
 will be left aligned by default.

 Sorry not to be of better help -- I think Bastien's suggestion to
 upgrade to 8.0 is the right move. A lot of the mailing list has likely
 made the move and thus it's hard to troubleshoot versions with the old
 exporter syntax.


 Best regards,
 John

 
  HTH,
 
  --
   Bastien
 

Re: [O] (no subject)

[Nick Dokos]

John Hendy jw.he...@gmail.com writes:

 I'm having a tough time finding info on LaTeX with what makes a table
 left or right aligned (not the columns, but the table itself). Most of
 the hits are on how to *center* the table, which seems to suggest they
 will be left aligned by default.


Does something like this help?

--8---cut here---start-8---
* Align tables on the page

Here is a table on the left side:

#+LATEX: \noindent
#+ATTR_LATEX: :center nil
| a | b | c |
|---+---+---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |
#+LATEX: \hfill

The noindent just gets rid of the indentation of the first line of a paragraph
which in this case is the table. The hfill adds infinite stretch after the 
table,
so it pushes the table to the left.

Here is a centered table:

| a | b | c |
|---+---+---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |

And here's a table on the right side:

#+LATEX: \hfill
#+ATTR_LATEX: :center nil
| a | b | c |
|---+---+---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |

Here the hfill adds infinite stretch before the table, so it pushes the table 
to the right.
--8---cut here---end---8---


-- 
Nick

Re: [O] (no subject)

[Bastien]

Hi Ken,

Ken Okada keno.s...@gmail.com writes:

 I have a question. By default tables are centered in LaTeX export.
 Sometimes I prefere to make it flush left or right. I thought this was
 done with, for example,

 #+ATTR_LATEX: :center nil
 | a | b |
 | 1 | 2 |

The use of the :center parameter suggests you consulted a recent
version of the documentation, for Org =8.0.

This is how it works for Org 8.0 and above:

#+ATTR_LATEX: :environment longtable :align l|lp{3cm}r|l
| a | b | c |
| 1 | 2 | 3 |

If you can, please upgrade.  Otherwise, someone needs to check the
documentation for Org 7.8.11... 

HTH,

-- 
 Bastien

Re: [O] (no subject)

[John Hendy]

On Wed, Jan 29, 2014 at 6:15 PM, Bastien b...@gnu.org wrote:

 Hi Ken,

 Ken Okada keno.s...@gmail.com writes:

  I have a question. By default tables are centered in LaTeX export.
  Sometimes I prefere to make it flush left or right. I thought this was
  done with, for example,
 
  #+ATTR_LATEX: :center nil
  | a | b |
  | 1 | 2 |

 The use of the :center parameter suggests you consulted a recent
 version of the documentation, for Org =8.0.

 This is how it works for Org 8.0 and above:

 #+ATTR_LATEX: :environment longtable :align l|lp{3cm}r|l
 | a | b | c |
 | 1 | 2 | 3 |

 If you can, please upgrade.  Otherwise, someone needs to check the
 documentation for Org 7.8.11...

Bastien beat me to it. Yes, the example syntax is for Org  8.0.
Here's a version of the manual for v7.9:
- 
http://www.gnu.org/software/emacs/manual/html_mono/org.html#Tables-in-LaTeX-export

I'm not sure what the proper argument is and can't test since I'm on
the current version of Org from git. You might take a look at the
placement= argument?

I'm having a tough time finding info on LaTeX with what makes a table
left or right aligned (not the columns, but the table itself). Most of
the hits are on how to *center* the table, which seems to suggest they
will be left aligned by default.

Sorry not to be of better help -- I think Bastien's suggestion to
upgrade to 8.0 is the right move. A lot of the mailing list has likely
made the move and thus it's hard to troubleshoot versions with the old
exporter syntax.


Best regards,
John


 HTH,

 --
  Bastien

Re: [O] (no subject)

[Ken Okada]

John,

Thanks for advising.

On Org 7.8.11, placement=[l] and placement={l} parameter does not make
sense for tables as I tried.

I tried to install the current version. (There was a compile error
arising from the fact that BSD make is not GNU make, but it's no matter.)
A simple example for :center nil works well. For main org file I have to
do more work... not about centering.

However there seems not to be a parameter for flush right. At present
this is not a serious problem because :center nil works well, so we can
control directory with #+LATEX: \begin ... and \end . But it's tiresome.

I also feel something about the difference between the way to designate
centering and flush left/right. For HTML export we use :align parameter;
for LaTeX, :center parameter, which only allows us to control centering
or not. :align parameter is used for alignment of contents of table.
I'm confused. I guess there's a problem about backward compatibility or
something.

As you wrote there's a way to change default behaviour, but I feel
centering is confortable in the most typesetting *with Org*.
I think such searching result is due to the default behaviour of LaTeX.
File local option switching the behaviour would be useful, I think.

Best regards,
Ken Okada


At Wed, 29 Jan 2014 18:22:38 -0600,
John Hendy wrote:
 
 On Wed, Jan 29, 2014 at 6:15 PM, Bastien b...@gnu.org wrote:
 
  Hi Ken,
 
  Ken Okada keno.s...@gmail.com writes:
 
   I have a question. By default tables are centered in LaTeX export.
   Sometimes I prefere to make it flush left or right. I thought this was
   done with, for example,
  
   #+ATTR_LATEX: :center nil
   | a | b |
   | 1 | 2 |
 
  The use of the :center parameter suggests you consulted a recent
  version of the documentation, for Org =8.0.
 
  This is how it works for Org 8.0 and above:
 
  #+ATTR_LATEX: :environment longtable :align l|lp{3cm}r|l
  | a | b | c |
  | 1 | 2 | 3 |
 
  If you can, please upgrade.  Otherwise, someone needs to check the
  documentation for Org 7.8.11...
 
 Bastien beat me to it. Yes, the example syntax is for Org  8.0.
 Here's a version of the manual for v7.9:
 - 
 http://www.gnu.org/software/emacs/manual/html_mono/org.html#Tables-in-LaTeX-export
 
 I'm not sure what the proper argument is and can't test since I'm on
 the current version of Org from git. You might take a look at the
 placement= argument?
 
 I'm having a tough time finding info on LaTeX with what makes a table
 left or right aligned (not the columns, but the table itself). Most of
 the hits are on how to *center* the table, which seems to suggest they
 will be left aligned by default.
 
 Sorry not to be of better help -- I think Bastien's suggestion to
 upgrade to 8.0 is the right move. A lot of the mailing list has likely
 made the move and thus it's hard to troubleshoot versions with the old
 exporter syntax.
 
 
 Best regards,
 John
 
 
  HTH,
 
  --
   Bastien
 

Re: [O] (no subject)

[Bastien]

Hi Cecil,

Cecil Westerhof cldwester...@gmail.com writes:

 Is that possible?

Well, I'd simply not use a Hours spent headline, which seems
redundant.

-- 
 Bastien

Re: [O] (no subject)

[Bastien]

Cecil Westerhof cldwester...@gmail.com writes:

 Is that possible?



-- 
 Bastien

Re: [O] (no subject)

[Cecil Westerhof]

2013/11/6 Cecil Westerhof cldwester...@gmail.com

  I would like to keep things in the three Hours Today. Is there a

  way to get something like:
  | Headline  | Time   |
  |---+|
  | *Total time*  | *6:35* |
  |---+|
  | Workshop shell scripting  |   2:12 |
  | Security Intake   |   2:39 |
  | Internal Project  |   1:44 |

 No.


 OK. I'll have to live with it, or make a workaround.


I solved it with:
#+BEGIN: clocktable :maxlevel 1 :scope nil :compact nil

And using narrow-region.

-- 
Cecil Westerhof

Re: [O] (no subject)

[Martin Beck]

Samuel Wales samologist at gmail.com writes:

 (setq org-agenda-inactive-leader Inactive:  )
 (setq org-agenda-include-inactive-timestamps t)
 
 Custom command:
 
   (ip past 7d
;; faster than tags
agenda 
((org-agenda-start-day -7d)
 (org-agenda-span 7)
 (org-agenda-repeating-timestamp-show-all nil)
 ;; %s is only for agenda views
 ;; (org-agenda-prefix-format %s)
 ;; maybe not make much difference ka
 ;; (org-agenda-use-tag-inheritance nil)
 ))
 
 ===
 
 Samuel
 

great - thanks a lot. I'll test that for some time, but it seems to do what
I need.
Just the list created is very long.

Would it be possible to limit it to inactive timestamps only?

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bastien]

Hi Martin,

Martin elwood...@web.de writes:

 I now finally installed org-mode 7.9.4 and I tried to use the new sorting
 features, but it did not work.

the new sorting features will be in 8.0, not yet released...
sorry if I was unclear about this in a previous message.

HTH,

-- 
 Bastien

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin]

Bastien bzg at altern.org writes:

 
 the new sorting features will be in 8.0, not yet released...
 sorry if I was unclear about this in a previous message.


Thanks for clarifying. So if I use the current beta version, 
I can test it already?

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin]

Bastien bzg at altern.org writes:

 
 Martin elwood151 at web.de writes:
 
  Thanks for clarifying. So if I use the current beta version, 
  I can test it already?
 
 Yes :)
 

I tried and failed. :-(
I downloaded the zip-file
http://orgmode.org/cgit.cgi/org-mode.git/snapshot/release_8.0-beta.zip, copied
all the contents of the file into my paths (where org-mode 7.9.4 was working
happily before),
launched Emacs, byte-compiled the whole path

When I execute the agenda-command, I get the error message:
org-agenda-skip: Wrong type argument: stringp, nil
Is there any documentation about changes that might break something? 

Kind regards

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bastien]

Hi Martin,

Martin elwood...@web.de writes:

 When I execute the agenda-command, I get the error message:
 org-agenda-skip: Wrong type argument: stringp, nil
 Is there any documentation about changes that might break something? 

Wild guess:

~$ make autoloads

See http://orgmode.org/org.html#Installation

If those instructions are not clear enough, please raise your voice,
we are in the process of clarifying them!

Thanks,

-- 
 Bastien

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin]

Bastien bzg at altern.org writes:

 Wild guess:
 
 ~$ make autoloads
 
 See http://orgmode.org/org.html#Installation
 
 If those instructions are not clear enough, please raise 
 your voice, we are in the process of clarifying them!

thanks a lot! Your wild guess saved me (partially)!
I never needed that up to now (and first had to install make, 
as I am working on
Windows an need to use Cygwin for that) but finally it worked.

However I still have the problem that M-x org-version produces 
an error:
Org-mode version N/A-fixup (N/A-fixup !!check installation!! @
c:/Users/mynameDocuments/sorga/org-mode/org_current/lisp/)
Is this normal in a beta?

Another problem: org-export is missing, 
the file does not exist in lisp or
contrib/lisp.
I could not find anything about that in the mailing list, 
maybe I've overlooked it?

When trying to open an agenda, I get the error:
org-entries-lessp: Wrong type argument: stringp, nil

Did I do something wrong or is the typical beta-experience?
So then I think I've go back to 7.9.4 and await version 8 with patience.
(Or is there a way to get the new sorting features already with Version 7.9?

Concerning the instructions:
from my point of view it is not clear what has to be done to use the beta
version and what risks there are.
(For a programmer this might be clear, for a normal user this is not clear 
IMHO.)

Sorry for my beginner questions and merci beaucoup!

Kind regards

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bastien]

Hi Martin,

Martin elwood...@web.de writes:

 thanks a lot! Your wild guess saved me (partially)!
 I never needed that up to now (and first had to install make, 
 as I am working on
 Windows an need to use Cygwin for that) but finally it worked.

 However I still have the problem that M-x org-version produces 
 an error:
 Org-mode version N/A-fixup (N/A-fixup !!check installation!! @
 c:/Users/mynameDocuments/sorga/org-mode/org_current/lisp/)
 Is this normal in a beta?

Nope.  Did you run ~$ make autoloads (or simply ~$ make)
and set the correct load-paths?

 Another problem: org-export is missing, 
 the file does not exist in lisp or
 contrib/lisp.
 I could not find anything about that in the mailing list, 
 maybe I've overlooked it?

 When trying to open an agenda, I get the error:
 org-entries-lessp: Wrong type argument: stringp, nil

Same problems as above.

 Did I do something wrong or is the typical beta-experience?
 So then I think I've go back to 7.9.4 and await version 8 with patience.
 (Or is there a way to get the new sorting features already with Version 7.9?

 Concerning the instructions:
 from my point of view it is not clear what has to be done to use the beta
 version and what risks there are.
 (For a programmer this might be clear, for a normal user this is not
 clear IMHO.)

The instructions for using a beta are in the Using Org's git
repository subsection and requires people to have Git installed
on their machine.  If you have Git, its better to clone the repo
than to download the .zip from the repo.

 Sorry for my beginner questions and merci beaucoup!

Pas de problème :)

-- 
 Bastien

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin]

Bastien bzg at altern.org writes:

 
 Hi Martin,
 
 Martin elwood151 at web.de writes:

  However I still have the problem that M-x org-version produces 
  an error:
  Org-mode version N/A-fixup (N/A-fixup !!check installation!! @
  c:/Users/mynameDocuments/sorga/org-mode/org_current/lisp/)
  Is this normal in a beta?
 
 Nope.  Did you run ~$ make autoloads (or simply ~$ make)
 and set the correct load-paths?
Yes, I set the load paths for lisp and contrib/lisp in my .emacs file 
and I executed make autoloads in the org-mode directory.
:-(

still the same problem:
  When trying to open an agenda, I get the error:
  org-entries-lessp: Wrong type argument: stringp, nil
 The instructions for using a beta are in the Using Org's git
 repository subsection and requires people to have Git installed
 on their machine.  If you have Git, its better to clone the repo
 than to download the .zip from the repo.
When trying the git clone command in cygwin, I get an error message connection
refused. I fear this could be blocked in my company's network.

So I will have to download the archives and install them manually, I fear.

I tried again, also modifying the local.mk (I'm using Windows 7), but no 
success.
So I think I'll have to go back to 7.9.4.
:-(

Kind regards

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Robert Eckl]

Martin elwood...@web.de writes:

 Bastien bzg at altern.org writes:

 
 Hi Martin,
 
 Martin elwood151 at web.de writes:

  However I still have the problem that M-x org-version produces 
  an error:
  Org-mode version N/A-fixup (N/A-fixup !!check installation!! @
  c:/Users/mynameDocuments/sorga/org-mode/org_current/lisp/)
  Is this normal in a beta?
 
 Nope.  Did you run ~$ make autoloads (or simply ~$ make)
 and set the correct load-paths?
 Yes, I set the load paths for lisp and contrib/lisp in my .emacs file 
 and I executed make autoloads in the org-mode directory.
 :-(

 still the same problem:
  When trying to open an agenda, I get the error:
  org-entries-lessp: Wrong type argument: stringp, nil
 The instructions for using a beta are in the Using Org's git
 repository subsection and requires people to have Git installed
 on their machine.  If you have Git, its better to clone the repo
 than to download the .zip from the repo.
 When trying the git clone command in cygwin, I get an error message
 connection refused. I fear this could be blocked in my company's
 network. 

 So I will have to download the archives and install them manually, I
 fear. 

 I tried again, also modifying the local.mk (I'm using Windows 7), but
 no success. 
 So I think I'll have to go back to 7.9.4.
 :-(

Recently i did run into the same issue. 
Reordering things in my .emacs did the trick -
first set the load-path, especially the path where org-mode lives, then
the rest. And be sure, org-mode is loaded not from an directory with an
old version or from an build-in version. 
I thought, the configuration was so, but AFAIR there was an old path, which
was ignored by versions less recent. It was a mixed configuration in
office, so yet i can not look for this.

Cu
Robert

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin]

Bastien bzg at altern.org writes:

 
 Hi Martin,
 
 Martin elwood151 at web.de writes:
 
  I'll try to install it, test it and then get back to you with 
  a feedback how it works as soon as I can.

Hi Bastien,

I now finally installed org-mode 7.9.4 and I tried to use the new sorting
features, but it did not work.

I changed my sorting strategy to:
(setq org-agenda-sorting-strategy
  (quote ((agenda deadline-up scheduled-up time-up user-defined-up)
  (todo category-up priority-down effort-up)
  (tags category-up priority-down effort-up)
  (search nil
And now when trying to display the agenda, I get the following error:
Symbol's value as variable is void: deadline-up

Did I do something wrong or install the wrong version?

Kind regards

Martin

Re: [O] (no subject)

[T.F. Torrey]

Thank you for your thoughtful reply. -- T.

Bastien b...@altern.org writes:

 Hi Terry,

 I hear you.  I completely agree that Org should not be less flexible
 than it has been so far.  At least not for very good reasons, shared
 by both the developers and the users.  IOW: ease of maintainance and
 code consistency should not let us introduce rigidity for the users.

 Let's focus on the regressions and let's try to fix the ones that we
 can fix.

 As discussions have shown so far, Nicolas holds the keys when it comes
 to honoring Org's consistency regarding its syntax -- the document he
 wrote will help us all to speak about the same syntax and rules.  But
 as you may have felt, I'm more on the user conveniency side, even if
 we need to sacrifice some consistency.  There is a balance here, and I
 hope we keep a good one.

 So as I said: let's focus on what you perceive as regressions wrt what
 Org allows.

 The subject of this thread does not fall in this category: headlines
 have always been starting with stars, there is no regression here.  On
 the contrary: a few years ago, we had no answer to this FAQ, now we
 can help users with several solution when the problem is aesthetic.

 Finally, I agree with Suvayu that the problem *is* mostly aesthetic,
 so the solutions we provide are enough (i.e., the FAQ, org-bullets.el
 in contrib/.)  The question is rather whether we should have an Org
 option in core to allow users to tweak the appearance of the stars:
 my answer here is no, because I don't see why users would stop here.
 Once we offer such an option for headlines, why not for comments and
 other characters with a syntactic role?  (I replied a question on
 stackoverflow on how to use % instead of # for comments...)

 Anyway -- Org still stands on the side of users' freedom, let's
 fix the real regressions.

 Thanks!

Re: [O] (no subject)

[Bastien]

Hi Terry,

I hear you.  I completely agree that Org should not be less flexible
than it has been so far.  At least not for very good reasons, shared
by both the developers and the users.  IOW: ease of maintainance and
code consistency should not let us introduce rigidity for the users.

Let's focus on the regressions and let's try to fix the ones that we
can fix.

As discussions have shown so far, Nicolas holds the keys when it comes
to honoring Org's consistency regarding its syntax -- the document he
wrote will help us all to speak about the same syntax and rules.  But
as you may have felt, I'm more on the user conveniency side, even if
we need to sacrifice some consistency.  There is a balance here, and I
hope we keep a good one.

So as I said: let's focus on what you perceive as regressions wrt what
Org allows.

The subject of this thread does not fall in this category: headlines
have always been starting with stars, there is no regression here.  On
the contrary: a few years ago, we had no answer to this FAQ, now we
can help users with several solution when the problem is aesthetic.

Finally, I agree with Suvayu that the problem *is* mostly aesthetic,
so the solutions we provide are enough (i.e., the FAQ, org-bullets.el
in contrib/.)  The question is rather whether we should have an Org
option in core to allow users to tweak the appearance of the stars:
my answer here is no, because I don't see why users would stop here.
Once we offer such an option for headlines, why not for comments and
other characters with a syntactic role?  (I replied a question on
stackoverflow on how to use % instead of # for comments...)

Anyway -- Org still stands on the side of users' freedom, let's
fix the real regressions.

Thanks!

-- 
 Bastien

Re: [O] (no subject)

[Bastien]

Hi Andreas,

Andreas Röhler andreas.roeh...@easy-emacs.de writes:

 BTW does that mean, stars are hard-coded in a way, they can't be
 replaced by another car?

Yes, this is the case.

 If yes, what about to keep the core more abstract?

This is a hard problem and I personally don't think it's worth
tackling it.  But I don't want to decourage anyone, of course :)

-- 
 Bastien

Re: [O] (no subject)

[Andreas Röhler]

Am 08.03.2013 11:46, schrieb Bastien:

Hi Andreas,

Andreas Röhler andreas.roeh...@easy-emacs.de writes:


BTW does that mean, stars are hard-coded in a way, they can't be
replaced by another car?


Yes, this is the case.


If yes, what about to keep the core more abstract?


This is a hard problem


Hi Bastien,

can it be more difficult than related use of comment-start?

[ ... ]

Cheers,

Andreas

Re: [O] (no subject)

[Bastien]

Hi Andreas,

Andreas Röhler andreas.roeh...@easy-emacs.de writes:

 can it be more difficult than related use of comment-start?

Yes -- check this FAQ: 
http://orgmode.org/worg/org-faq.html#sec-8-12

HTH,

-- 
 Bastien

Re: [O] (no subject)

[Andreas Röhler]

Am 08.03.2013 12:05, schrieb Bastien:

Hi Andreas,

Andreas Röhler andreas.roeh...@easy-emacs.de writes:


can it be more difficult than related use of comment-start?


Yes -- check this FAQ:
http://orgmode.org/worg/org-faq.html#sec-8-12

HTH,



Thanks, still non-believing :)

(defcustom outline-regexp [*\^L]+
  Regular expression to match the beginning of a heading.
Any line whose beginning matches this regexp is considered to start a heading.
Note that Outline mode only checks this regexp at the start of a line,
so the regexp need not (and usually does not) start with `^'.
The recommended way to set this is with a Local Variables: list
in the file it applies to.  See also `outline-heading-end-regexp'.
  :type 'regexp
  :group 'outlines)

IMHO remains to make that buffer-local and use outline-regexp from inside 
org-mode.

Andreas

Re: [O] (no subject)

[Bastien]

Andreas Röhler andreas.roeh...@easy-emacs.de writes:

 IMHO remains to make that buffer-local and use outline-regexp from
 inside org-mode.

Have a go and let us know :)

-- 
 Bastien

Re: [O] (no subject)

[Andreas Röhler]

Am 08.03.2013 12:23, schrieb Bastien:

Andreas Röhler andreas.roeh...@easy-emacs.de writes:


IMHO remains to make that buffer-local and use outline-regexp from
inside org-mode.


Have a go and let us know :)



That should work already - to start with.
commit 8cf6bc6faeb2a3b3fec0780e56a04ef0e13c3c62
Author: Andreas Roehler andreas.roeh...@online.de
Date:   Fri Mar 8 13:58:13 2013 +0100

Enable different heading chars, not just `*'

Use variable `org-heading-char', customizable later on,
instead of hard-coded `*'

TINYCHANGE

diff --git a/lisp/org.el b/lisp/org.el
index 811506a..2db63ae 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -90,13 +90,17 @@
 ;; `org-outline-regexp'.  The only function still directly relying on
 ;; `outline-regexp' is `org-overview' so that `org-cycle' can do its
 ;; job when `orgstruct-mode' is active.
+(defvar org-heading-char *)
+
 (defvar org-outline-regexp \\*+ 
   Regexp to match Org headlines.)
+(setq org-outline-regexp (concat (regexp-quote org-heading-char) + ))
 
 (defvar org-outline-regexp-bol ^\\*+ 
   Regexp to match Org headlines.
 This is similar to `org-outline-regexp' but additionally makes
 sure that we are at the beginning of the line.)
+(setq org-outline-regexp-bol (concat ^ (regexp-quote org-heading-char) + ))
 
 (defvar org-heading-regexp ^\\(\\*+\\)\\(?: +\\(.*?\\)\\)?[ \t]*$
   Matches a headline, putting stars and text into groups.

Re: [O] (no subject)

[Bastien]

Hi Andreas,

Andreas Röhler andreas.roeh...@easy-emacs.de writes:

 Am 08.03.2013 12:23, schrieb Bastien:
 Andreas Röhler andreas.roeh...@easy-emacs.de writes:

 IMHO remains to make that buffer-local and use outline-regexp from
 inside org-mode.

 Have a go and let us know :)

 That should work already - to start with.

Sorry, I should not let you go into that direction without a warning
that I won't commit anything related to this myself.

Btw, did you read the thread as the FAQ suggests?

One reason why the stars are hardcoded (like the comment characters
and other syntactic elements) is that Org files are used outside Emacs
and allowing users to use something else here is calling for trouble.

So -- just to let you know that it's fine playing with the idea and
providing proof-of-concept patches, but there are many reasons why
this cannot be considered.

Also, we are trying to focus on 8.0 right now... help welcome!

-- 
 Bastien

Re: [O] (no subject)

[Andreas Röhler]

Am 08.03.2013 14:12, schrieb Bastien:

Hi Andreas,

Andreas Röhler andreas.roeh...@easy-emacs.de writes:


Am 08.03.2013 12:23, schrieb Bastien:

Andreas Röhler andreas.roeh...@easy-emacs.de writes:


IMHO remains to make that buffer-local and use outline-regexp from
inside org-mode.


Have a go and let us know :)


That should work already - to start with.


Sorry, I should not let you go into that direction without a warning
that I won't commit anything related to this myself.



Hi Bastien,

don't worry, didn't expect that for now or soon.



Btw, did you read the thread as the FAQ suggests?


Nothing different resp. new so far. Let's stress that solution in mind also 
would be quite simple.
See the example patch.
No-one would be compelled to change the default BTW, it would just open the 
possibility.



One reason why the stars are hardcoded (like the comment characters
and other syntactic elements) is that Org files are used outside Emacs
and allowing users to use something else here is calling for trouble.



Hmm, AFAIS trouble might occur only if someone tries to load a non-default 
--i.e. not-starred--
org-file while the default is active.

But even then it's quite easy to write a guess, which might start if org-mode 
didn't encounter the
stars where expected.

[ ... ]

Re: [O] (no subject)

[Bastien]

Hi Andreas,

Andreas Röhler andreas.roeh...@easy-emacs.de writes:

 Hmm, AFAIS trouble might occur only if someone tries to load a
 non-default --i.e. not-starred-- org-file while the default is
 active.

... or if someone shares a file online using non-star character
as the prefix for headlines: this file won't be processed by
Org tools like org-ruby and the like.

 But even then it's quite easy to write a guess, which might start if
 org-mode didn't encounter the stars where expected.

Org files are not just for Emacs, that's were the problem lies...

-- 
 Bastien

Re: [O] (no subject)

[T.F. Torrey]

Hello,

Bastien b...@altern.org writes:

 Hi Andreas,

 Andreas Röhler andreas.roeh...@easy-emacs.de writes:

 Hmm, AFAIS trouble might occur only if someone tries to load a
 non-default --i.e. not-starred-- org-file while the default is
 active.

 ... or if someone shares a file online using non-star character
 as the prefix for headlines: this file won't be processed by
 Org tools like org-ruby and the like.

 But even then it's quite easy to write a guess, which might start if
 org-mode didn't encounter the stars where expected.

 Org files are not just for Emacs, that's were the problem lies...

I don't understand this heavy-handed approach.

Plain text is great because I can do whatever I want.  What I come up
with might not work correctly in other tools (or anything at all), but I
have the freedom to do interesting things, and to have my files look
just the way I want them to.

Emacs is great because it allows me the freedom of near-infinite
customization.  It has sensible defaults, but it allows me to break
things however I want.

Org, on the other hand, seems to be moving away from that in many ways.
Headlines must start with stars because I might someday post something
on the web and it wouldn't work for someone else?  Other tools might not
recognize my file correctly?  A developer of some other tool might
someday have a problem?  These are not good reasons for limiting what I
can do with my own Org files.

I don't need or want supervision in how I create my files.  I want
freedom.  If I wanted supervision, I wouldn't be using Emacs.  Have you
seen the lisp posted to the web?  Somehow, Emacs and I survive that.

Org started as a great tool that let me do cool things with my text
files.  I don't want to see it change to a rigid format for me to force
my files into, where my only options are conform or leave.

Org should err on the side of user freedom.

IMHO,
Terry
-- 
T.F. Torrey

Re: [O] (no subject)

[Nicolas Goaziou]

Hello,

tftor...@tftorrey.com (T.F. Torrey) writes:

 Hello,

 Bastien b...@altern.org writes:

 Hi Andreas,

 Andreas Röhler andreas.roeh...@easy-emacs.de writes:

 Hmm, AFAIS trouble might occur only if someone tries to load a
 non-default --i.e. not-starred-- org-file while the default is
 active.

 ... or if someone shares a file online using non-star character
 as the prefix for headlines: this file won't be processed by
 Org tools like org-ruby and the like.

 But even then it's quite easy to write a guess, which might start if
 org-mode didn't encounter the stars where expected.

 Org files are not just for Emacs, that's were the problem lies...

 I don't understand this heavy-handed approach.

 Plain text is great because I can do whatever I want.  What I come up
 with might not work correctly in other tools (or anything at all), but I
 have the freedom to do interesting things, and to have my files look
 just the way I want them to.

 Emacs is great because it allows me the freedom of near-infinite
 customization.  It has sensible defaults, but it allows me to break
 things however I want.

 Org, on the other hand, seems to be moving away from that in many ways.
 Headlines must start with stars because I might someday post something
 on the web and it wouldn't work for someone else?  Other tools might not
 recognize my file correctly?  A developer of some other tool might
 someday have a problem?  These are not good reasons for limiting what I
 can do with my own Org files.

 I don't need or want supervision in how I create my files.  I want
 freedom.  If I wanted supervision, I wouldn't be using Emacs.  Have you
 seen the lisp posted to the web?  Somehow, Emacs and I survive that.

 Org started as a great tool that let me do cool things with my text
 files.  I don't want to see it change to a rigid format for me to force
 my files into, where my only options are conform or leave.


I disagree.

Org is a plain text format. Like any format, plain-text or not, it needs
a proper definition. At least, it helps users and developers to agree on
what they are talking about. As for myself, I cannot play any game if
I don't know its rules.

My point of view is the following: Org (as a format) definition
shouldn't depend on Emacs. It should be totally parseable by any
language (which is not the case actually, since syntax relies on
variables defined in Emacs). IOW, we should work to make it a real
plain-text markup format.

 Org should err on the side of user freedom.

You still have the freedom to choose what you write down in Org format.
You have the freedom use, or to not use Org. You have the freedom to
modify Org code to bend it to your will. IMO, freedom is totally
unrelated to this subject.


Regards,

-- 
Nicolas Goaziou

Re: [O] (no subject)

[Suvayu Ali]

Hi,

On Fri, Mar 08, 2013 at 10:19:56PM +0100, Nicolas Goaziou wrote:
 tftor...@tftorrey.com (T.F. Torrey) writes:
 
  Org, on the other hand, seems to be moving away from that in many ways.
  Headlines must start with stars because I might someday post something
  on the web and it wouldn't work for someone else?  Other tools might not
  recognize my file correctly?  A developer of some other tool might
  someday have a problem?  These are not good reasons for limiting what I
  can do with my own Org files.

[...]

 My point of view is the following: Org (as a format) definition
 shouldn't depend on Emacs. It should be totally parseable by any
 language (which is not the case actually, since syntax relies on
 variables defined in Emacs). IOW, we should work to make it a real
 plain-text markup format.

This discussion comes up again and again over the years.  Every time the
conclusion has been, there are many who want to use other characters
instead of a star but the rational is always cosmetic.  And in the end
people end up agreeing it is not worth the pain.

To give you an example of breakage, after long whining github started
supporting org file formatting for READMEs via org-ruby (even source
blocks I think!).  Do you expect we can have similar support if
something as fundamental as the headline is not well defined?  Other
possible breakages could be in org-merge-driver, VimOrganizer, org-sync,
some of the collaborative editing projects that have been spawning, and
the list goes on ...

FWIW, assuming that the rational behind this feature request is
cosmetic, there was a proposal to implement this as overlays.  So the
file still uses *-s but a user can customise how they are displayed.  I
think this addresses almost all requests in this category (majority
being I want really cool UTF characters instead of boring old
asterisk).  If someone is interested in implementing this, I'm pretty
sure the maintainers would give that a serious consideration for
inclusion.  Changing the file format on the other hand is a no go
amongst many of the users (myself included) and developers alike.

Hope my 2¢ shed some light on the implications of a change like this.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bastien]

Hi Martin,

Martin elwood...@web.de writes:

 I'll try to install it, test it and then get back to you with 
 a feedback how it works as soon as I can.

Thanks in advance for testing this!  If you can help with updating
the manual wrt this change, please go ahead.

Best,

-- 
 Bastien

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin]

Bastien bzg at altern.org writes:

 
 Hi Martin and Bernt,
 
 the master branch now have new sorting strategies:
 
 timestamp-up   Sort by any timestamp, early first
 timestamp-down Sort by any timestamp, late first
 scheduled-up   Sort by scheduled timestamp, early first
 scheduled-down Sort by scheduled timestamp, late first
 deadline-upSort by deadline timestamp, early first
 deadline-down  Sort by deadline timestamp, late first
 ts-up  Sort by active timestamp, early first
 ts-downSort by active timestamp, late first
 tsia-upSort by inactive timestamp, early first
 tsia-down  Sort by inactive timestamp, late first
 
 Please have a try and let me know if this works as
 expected.
 
 Thanks both for your input on this,
 

Hi Bastien,

thanks a lot for your help and for your effort (and sorry for my late reply)!!

I would love to test this, but I first have to manage to install 
the latest version. I've found the FAQ. 
I'll try to install it, test it and then get back to you with 
a feedback how it works as soon as I can.

Kind regards

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bastien]

Hi Martin and Bernt,

the master branch now have new sorting strategies:

timestamp-up   Sort by any timestamp, early first
timestamp-down Sort by any timestamp, late first
scheduled-up   Sort by scheduled timestamp, early first
scheduled-down Sort by scheduled timestamp, late first
deadline-upSort by deadline timestamp, early first
deadline-down  Sort by deadline timestamp, late first
ts-up  Sort by active timestamp, early first
ts-downSort by active timestamp, late first
tsia-upSort by inactive timestamp, early first
tsia-down  Sort by inactive timestamp, late first

Please have a try and let me know if this works as
expected.

Thanks both for your input on this,

-- 
 Bastien

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bernt Hansen]

Martin Beck elwood...@web.de writes:

 Bernt Hansen bernt at norang.ca writes:

  I tried to create a block agenda with several blocks based 
  on the (agenda )command, but then I also have the time 
  grid several times..
 
 
 You should be able to turn the grid off.


 Hi Bernt,
 thanks a lot for your answers (also the other one:
 http://article.gmane.org/gmane.emacs.orgmode/65520).

 If it is possible to use more than one agenda block in the block agenda 
 and turn off the time grid for all but the first, this should do perfectly 
 what
 I need. 

Yes it is possible.  See Eric S Fraga's reply in this thread for the
appropriate variable.

Regards,
Bernt

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bernt Hansen]

Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:

 Bernt,

 Bernt Hansen wrote:

 The thing I couldn't get to work was automatically starting column view
 in my block agenda.  I can still manually do that with C-c C-x C-c

 What about this?

  (add-to-list 'org-agenda-custom-commands
   '(H
 tags-todo +home
 ((org-agenda-view-columns-initially t

 Sorry. It does work as standalone agenda view, but I now guess you meant not
 in a block view... Too quick!

Exactly :)

Regards,
Bernt

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bernt Hansen]

Martin Beck elwood...@web.de writes:

 Bernt Hansen bernt at norang.ca writes:

  But unfortunately, it does only display category, TODO-keyword 
  and subject, but
  NO information about Deadline or Scheduled date.
 

 I tried to create a block agenda with several blocks based 
 on the (agenda )command, but then I also have the time grid several 
 times..



You should be able to turn the grid off.

Bernt

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bernt Hansen]

Martin Beck elwood...@web.de writes:

 Hi Bernt,
 thanks for your help - so if you can not make it work, I assume that it's not
 possible yet?

I didn't spend a lot of time on this so I wouldn't give up just yet.
The thing I couldn't get to work was automatically starting column view
in my block agenda.  I can still manually do that with C-c C-x C-c

 I tried your code - it does what it promises.. however, you're right,
 it's not
 yet what I need:
 I'd need Priority A and B in one view (table),
 then sorted
 * Prio A first
 * Prio B second
 lines sorted by date descending (newest first) .. would that be possible?

I think that should be possible.


 If I understand the problem right, I can get the deadline/scheduled 
 information
 in the agenda only with the agenda commmand, not with tags-todo or anything
 else? This is a pity.

In column view you can see the data in any agenda view.  Dates are
normally only displayed in the agenda view which includes the
time grid.  This would only show past due and past scheduled items and
deadlines within deadline warning period.

 So theoretically, I'd have to use this agenda command and then tweak the 
 sorting
 function to arrange items by Prio first and then by date?
 (That's what I tried already, based on your setup, but I was not able to make 
 it
 work yet..)


Is column view in the agenda acceptable? I don't know of another way to
display the deadline and schedule information you want.

I can take another look at this over the weekend id you like.

Regards,
Bernt

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin Beck]

Bernt Hansen bernt at norang.ca writes:

  I tried to create a block agenda with several blocks based 
  on the (agenda )command, but then I also have the time 
  grid several times..
 
 
 You should be able to turn the grid off.


Hi Bernt,
thanks a lot for your answers (also the other one:
http://article.gmane.org/gmane.emacs.orgmode/65520).

If it is possible to use more than one agenda block in the block agenda 
and turn off the time grid for all but the first, this should do perfectly what
I need. 
The only problem is, that I don't get it to work, because I'm messing up
the code blocks. :-(

I'd need 
* Block 1 with time grid and deadlines (current and late) 
* Block 2 with Prio A (scheduled today or before today), 
sorted by scheduled date - newest first 
* Block 3 with Prio B (scheduled today or before today, 
sorted by scheduled date - newest first)

If you have a suggestion how to solve that, this would help me very much.

Kind regards

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Sebastien Vauban]

Hi Bernt,

Bernt Hansen wrote:
 Martin Beck elwood...@web.de writes:

 Hi Bernt,
 thanks for your help - so if you can not make it work, I assume that it's not
 possible yet?

 I didn't spend a lot of time on this so I wouldn't give up just yet.
 The thing I couldn't get to work was automatically starting column view
 in my block agenda.  I can still manually do that with C-c C-x C-c

What about this?

--8---cut here---start-8---
 (add-to-list 'org-agenda-custom-commands
  '(H
tags-todo +home
((org-agenda-view-columns-initially t
--8---cut here---end---8---

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Sebastien Vauban]

Bernt,

 Bernt Hansen wrote:
 Martin Beck elwood...@web.de writes:

 Hi Bernt,
 thanks for your help - so if you can not make it work, I assume that it's 
 not
 possible yet?

 I didn't spend a lot of time on this so I wouldn't give up just yet.
 The thing I couldn't get to work was automatically starting column view
 in my block agenda.  I can still manually do that with C-c C-x C-c

 What about this?

  (add-to-list 'org-agenda-custom-commands
   '(H
 tags-todo +home
 ((org-agenda-view-columns-initially t

Sorry. It does work as standalone agenda view, but I now guess you meant not
in a block view... Too quick!

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Eric S Fraga]

Martin Beck elwood...@web.de writes:

 If it is possible to use more than one agenda block in the block agenda 
 and turn off the time grid for all but the first, this should do perfectly 
 what
 I need. 

One of my agenda custom views looks like this:

#+begin_src emacs-lisp
(v Startup View
  (
(todo INPR (quote(org-agenda-overriding-header Currently active tasks: 
)))
(todo WAIT (quote(org-agenda-overriding-header Tasks waiting on others: 
)))
(agenda  ((org-agenda-time-grid nil)
  (org-deadline-warning-days 365)
  (org-agenda-entry-types (quote (:deadline)))
  (org-agenda-skip-entry-if (quote scheduled))
  (org-agenda-ndays 1)
  (org-agenda-overriding-header Unscheduled upcoming deadlines:)))
(agenda  ((org-agenda-ndays 1)
  (org-deadline-warning-days 1)))
(todo  (quote(org-agenda-overriding-header Unscheduled No Deadline TODO: 

#+end_src

Note the =org-agenda-time-grid nil= setting.

HTH,
eric
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-898-g005917

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin Beck]

Bernt Hansen bernt at norang.ca writes:
 
  Ho could I insert this additional column in the agenda view?
 
 I can't make it work in the block agenda but as a standalone agenda does
 this help?
 
 --8---cut here---start-8---
 (x test tags-todo PRIORITY=\A\ 
  ((org-agenda-overriding-header Critical)
   (org-agenda-entry-types '(:deadline))
   (org-columns-default-format %10CATEGORY(Category) %60ITEM(Task)
%15DEADLINE(Deadline) %15SCHEDULED(Scheduled))
   (org-agenda-view-columns-initially t)
   (org-agenda-sorting-strategy (quote (time-up category-keep)))
   (org-agenda-todo-ignore-scheduled 'future)
   (org-agenda-todo-ignore-deadlines 'future)))
 --8---cut here---end---8---
 
 This starts the agenda in column mode and shows category, task,
 deadline, scheduled dates.
 
 'q' exits column mode.
 
 In the block agenda if you turn on column mode with C-c C-x C-c you get
 the same information for all tasks in the agenda
 
 It's probably not exactly what you were looking for...
 
 Regards,
 Bernt
 
 

Hi Bernt,
thanks for your help - so if you can not make it work, I assume that it's not
possible yet? 
I tried your code - it does what it promises.. however, you're right, it's not
yet what I need:
I'd need Priority A and B in one view (table),
then sorted
* Prio A first
* Prio B second
lines sorted by date descending (newest first) .. would that be possible?

If I understand the problem right, I can get the deadline/scheduled information
in the agenda only with the agenda commmand, not with tags-todo or anything
else? This is a pity.
So theoretically, I'd have to use this agenda command and then tweak the sorting
function to arrange items by Prio first and then by date?
(That's what I tried already, based on your setup, but I was not able to make it
work yet..)

Kind regards

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin Beck]

Bernt Hansen bernt at norang.ca writes:

  But unfortunately, it does only display category, TODO-keyword 
  and subject, but
  NO information about Deadline or Scheduled date.
 

I tried to create a block agenda with several blocks based 
on the (agenda )command, but then I also have the time grid several times..

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin Beck]

Martin Beck elwood151 at web.de writes:

(sorry, I was too fast and forgot to enter a subject)

I'm trying to create a custom agenda setup for my org-mode and I 
 wonder how I can sort the agenda-items by date (Scheduled or deadline): 
 newest first.
 
 
 I only found time-up / time-down in the parameters, but that does not seem to
do what I need.
 
 
 Another
  important point would be how to handle items with no scheduled/date or 
 deadline.. they should be placed at the end of the list.
 
 
 I've been searching some time but did not find a solution. 
 
 
 Kind regards
 
 
 Martin
 
 
 
 

Re: [O] (no subject)

[Bernt Hansen]

Martin Beck elwood...@web.de writes:

 I'm trying to create a custom agenda setup for my org-mode and I wonder how I 
 can sort the agenda-items by date (Scheduled
 or deadline): newest first.

 I only found time-up / time-down in the parameters, but that does not seem to 
 do what I need.

 Another important point would be how to handle items with no scheduled/date 
 or deadline.. they should be placed at the end
 of the list.

 I've been searching some time but did not find a solution. :-(

Hi Martin,

I sort my daily agenda items specifically using a bunch of complicated
sorting functions.  They are all documented here:

http://doc.norang.ca/org-mode.html#AgendaViewTweaks

HTH,
Bernt

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Martin Beck]

Bernt Hansen bernt at norang.ca writes:

 
 Martin Beck elwood151 at web.de writes:
 
  I'm trying to create a custom agenda setup for my org-mode and I wonder how
I can sort the agenda-items by
 date (Scheduled
  or deadline): newest first.
 
  I only found time-up / time-down in the parameters, but that does not seem
to do what I need.
  ...
 
 Hi Martin,
 
 I sort my daily agenda items specifically using a bunch of complicated
 sorting functions.  They are all documented here:
 
 http://doc.norang.ca/org-mode.html#AgendaViewTweaks
 
 HTH,
 Bernt
 
 

Hi Bernt,

thanks a lot - I'm already working with your setup and currently struggling to
adapt it to my needs, but my elisp/emacs/org-mode knowledge is still too 
limited.

Is it true that time-up only sorts items which really have a time
(hours/minutes) defined, so it does not also sort everything with
date-timestamps by date?

I tried to modify your Block Agenda by inserting the following block:

(tags-todo PRIORITY=\A\ (
(org-agenda-overriding-header Critical)
(org-agenda-entry-types '(:deadline))
(org-agenda-sorting-strategy (quote (time-up category-keep)))
(org-agenda-todo-ignore-scheduled 'future)
(org-agenda-todo-ignore-deadlines 'future)
))

But unfortunately, it does only display category, TODO-keyword and subject, but
NO information about Deadline or Scheduled date.

Ho could I insert this additional column in the agenda view?

Kind regards

Martin

Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?

[Bernt Hansen]

Martin Beck elwood...@web.de writes:

 Bernt Hansen bernt at norang.ca writes:

 
 Martin Beck elwood151 at web.de writes:
 
  I'm trying to create a custom agenda setup for my org-mode and I wonder how
 I can sort the agenda-items by
 date (Scheduled
  or deadline): newest first.
 
  I only found time-up / time-down in the parameters, but that does not seem
 to do what I need.
  ...
 
 Hi Martin,
 
 I sort my daily agenda items specifically using a bunch of complicated
 sorting functions.  They are all documented here:
 
 http://doc.norang.ca/org-mode.html#AgendaViewTweaks
 
 HTH,
 Bernt
 
 

 Hi Bernt,

 thanks a lot - I'm already working with your setup and currently struggling to
 adapt it to my needs, but my elisp/emacs/org-mode knowledge is still too 
 limited.

 Is it true that time-up only sorts items which really have a time
 (hours/minutes) defined, so it does not also sort everything with
 date-timestamps by date?

Hi Martin,

From 

,[ C-h v org-agenda-sorting-strategy ]
| time-upPut entries with time-of-day indications first, early first
| time-down  Put entries with time-of-day indications first, late first
`

time-up should sort items with a date stamp and time with earlier times
first followed by later times.  time-down is the opposite.  I don't
think this has anything to do with durations.  Yes it only seems to
affect entries with a time component.  On today's daily agenda if I set
org-agenda-sorting-strategy to only be time-up then the grid is at the
to of the agenda followed by all of the other entries.  Any entries with
a time are interspersed in the grid.

With time-down the grid is in reverse at the bottom of the agenda.


 I tried to modify your Block Agenda by inserting the following block:

 (tags-todo PRIORITY=\A\ (
   (org-agenda-overriding-header Critical)
   (org-agenda-entry-types '(:deadline))
   (org-agenda-sorting-strategy (quote (time-up category-keep)))
   (org-agenda-todo-ignore-scheduled 'future)
   (org-agenda-todo-ignore-deadlines 'future)
   ))

 But unfortunately, it does only display category, TODO-keyword and subject, 
 but
 NO information about Deadline or Scheduled date.

 Ho could I insert this additional column in the agenda view?

I can't make it work in the block agenda but as a standalone agenda does
this help?

--8---cut here---start-8---
  (x test tags-todo PRIORITY=\A\ 
   ((org-agenda-overriding-header Critical)
(org-agenda-entry-types '(:deadline))
(org-columns-default-format %10CATEGORY(Category) 
%60ITEM(Task) %15DEADLINE(Deadline) %15SCHEDULED(Scheduled))
(org-agenda-view-columns-initially t)
(org-agenda-sorting-strategy (quote (time-up category-keep)))
(org-agenda-todo-ignore-scheduled 'future)
(org-agenda-todo-ignore-deadlines 'future)))
--8---cut here---end---8---

This starts the agenda in column mode and shows category, task,
deadline, scheduled dates.

'q' exits column mode.

In the block agenda if you turn on column mode with C-c C-x C-c you get
the same information for all tasks in the agenda

It's probably not exactly what you were looking for...

Regards,
Bernt

Re: [O] (no subject)

[Nicolas Goaziou]

Hello,

Fabrice Popineau fabrice.popin...@gmail.com writes:

 I just updated a few hours ago with the git current version and I now get:

 Debugger entered--Lisp error: (invalid-read-syntax #)
   eval-buffer(#buffer  *load* nil c:/Home/.org-timestamps/CQP-org.cache
 nil t)  ; Reading at buffer position 621
   load-with-code-conversion(c:/Home/.org-timestamps/CQP-org.cache
 c:/Home/.org-timestamps/CQP-org.cache nil nil)
   load(c:/Home/.org-timestamps/CQP-org.cache nil nil t)
   load-file(c:/Home/.org-timestamps/CQP-org.cache)

 Actually, the .cache file reads :

 ...
 (puthash c:/Home/Cours/CQP-ArTech/org/CQP-Artech-slides.org '(:title
 #(CQP-ArTech Slides 0 17 (:parent (#(CQP-ArTech Slides 0 17 (:parent
 #3)) org-e-publish-cache)
 ...

 I guess the #3 is the culprit. Any idea what went wrong?

To sum it up, I added :parent property to each string but org-e-publish
tries to store them in the cache, which is impossible since cache is
eventually written to a file.

I have pushed a fix for that problem. Is it correct now?

Thanks for submitting this.


Regards,

-- 
Nicolas Goaziou

Re: [O] (no subject)

[Fabrice Popineau]

Seems to be ok on my side.

I wonder if my problem could have been triggered by the fact I had a
spurious file in the way of the (new) exporter: I had a foo.org file
exported to some other directory, but also a foo.html in the source
directory that had to be copied to the target directory by another
dependency of the project.

Thanks anyway for taking care of this.

Fabrice


2012/11/12 Nicolas Goaziou n.goaz...@gmail.com

 Hello,

 Fabrice Popineau fabrice.popin...@gmail.com writes:

  I just updated a few hours ago with the git current version and I now
 get:
 
  Debugger entered--Lisp error: (invalid-read-syntax #)
eval-buffer(#buffer  *load* nil
 c:/Home/.org-timestamps/CQP-org.cache
  nil t)  ; Reading at buffer position 621
load-with-code-conversion(c:/Home/.org-timestamps/CQP-org.cache
  c:/Home/.org-timestamps/CQP-org.cache nil nil)
load(c:/Home/.org-timestamps/CQP-org.cache nil nil t)
load-file(c:/Home/.org-timestamps/CQP-org.cache)
 
  Actually, the .cache file reads :
 
  ...
  (puthash c:/Home/Cours/CQP-ArTech/org/CQP-Artech-slides.org '(:title
  #(CQP-ArTech Slides 0 17 (:parent (#(CQP-ArTech Slides 0 17 (:parent
  #3)) org-e-publish-cache)
  ...
 
  I guess the #3 is the culprit. Any idea what went wrong?

 To sum it up, I added :parent property to each string but org-e-publish
 tries to store them in the cache, which is impossible since cache is
 eventually written to a file.

 I have pushed a fix for that problem. Is it correct now?

 Thanks for submitting this.


 Regards,

 --
 Nicolas Goaziou

Re: [O] (no subject)

[Bastien]

Neuwirth Erich erich.neuwi...@univie.ac.at writes:

 1 unexpected results:
FAILED  test-ob/org-babel-remove-result--results-org

Fixed, thanks.

-- 
 Bastien

Re: [O] (no subject)

[Achim Gratz]

Bastien writes:
 1 unexpected results:
FAILED  test-ob/org-babel-remove-result--results-org

 Fixed, thanks.

There are some tests that are supposed to have whitespace errors, based
on the comments in the file, but you've removed them along with all the
others.  I've reverted that hunk of the commit.


Regards,
Achim.
-- 
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] (no subject)

[Bastien]

Achim Gratz strom...@nexgo.de writes:

 There are some tests that are supposed to have whitespace errors, based
 on the comments in the file, but you've removed them along with all the
 others.  I've reverted that hunk of the commit.

Thanks,

-- 
 Bastien

Re: [O] (no subject)

[Achim Gratz]

Neuwirth Erich writes:
 Perhaps this is useful information

It would be more useful if the Org version you are trying to make was
included, but since it's probably not installed in lispdir yet, your
installed emacs would show a different version.  So I've implemented a
new target `config-version´ to make this easy to produce with make…

org-mode make config-version
= Org version
make:  Org-mode version 7.9.1 (release_7.9.1-442-g9ab8cb = 
/usr/local/share/emacs/site-lisp/org)



Regards,
Achim.
-- 
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [O] (no subject)

[Nicolas Goaziou]

Hello,

Mark Shoulson m...@kli.org writes:

 +(defvar org-e-html-quote-replacements
 +  '((fr «   » ‘ ’ ’)
 +(en “ ” ‘ ’ ’)
 +(de „ “ ‚ ‘ ’))

A docstring will be required for this variable. It should be
a defcustom.

 +(defvar org-e-latex-quote-replacements
 +  '((fr «~ ~» ‹~ ~› /!)
 +(en (( )) .( ). /)))

Ditto.

  (defcustom org-e-latex-quotes
'((fr
   (\\(\\s-\\|[[(]\\|^\\)\ . «~)
 @@ -699,25 +703,22 @@ during latex export it will output
Alist for quotes to use when converting english double-quotes.
  
  The CAR of each item in this alist is the language code.
 -The CDR of each item in this alist is a list of three CONS:
 -- the first CONS defines the opening quote;
 -- the second CONS defines the closing quote;
 -- the last CONS defines single quotes.
 +The CDR of each item in this alist is a list of CONS:
 +- the first CONS should define the opening quote;
 +- the second CONS should define the closing quote;
 +- subsequent CONS should define any other quotes, e.g. single, etc.
  
  For each item in a CONS, the first string is a regexp
  for allowed characters before/after the quote, the second
  string defines the replacement string for this quote.
:group 'org-export-e-latex
 -  :type '(list
 -   (cons :tag Opening quote
 - (string :tag Regexp for char before)
 - (string :tag Replacement quote ))
 -   (cons :tag Closing quote
 - (string :tag Regexp for char after )
 - (string :tag Replacement quote ))
 -   (cons :tag Single quote
 - (string :tag Regexp for char before)
 - (string :tag Replacement quote 
 +  :type '(repeat
 +   (cons
 +(string :tag language code)
 +(repeat
 + (cons :tag Quote
 +   (string :tag Regexp )
 +   (string :tag Replacement quote ))

The docstring is not valid. It's now an an alist whose key is the
language code and the value is a list of strings, not cons cells.

 +(defun org-e-latex--quotation-marks (text info) 
 +  (org-export-quotation-marks text info org-e-latex-quote-replacements))
 +  ;; (mapc (lambda(l)
 +  ;;   (let ((start 0))
 +  ;; (while (setq start (string-match (car l) text start))
 +  ;;   (let ((new-quote (concat (match-string 1 text) (cdr l
 +  ;; (setq text (replace-match new-quote  t t text))
 +  ;; (cdr (or (assoc (plist-get info :language) org-e-latex-quotes)
 +  ;;  ;; Falls back on English.
 +  ;;  (assoc en org-e-latex-quotes
 +  ;; text)

Use directly `org-e-latex-quote-replacements' in code then.

 +;
 +;; Probably a defcustom eventually.
 +
 +;; Each element of this consists of: car=language code, cdr=list of
 +;; double-quote-open-regexp, double-quote-close-regexp,
 +;; single-quote-open-regexp, single-quote-close-regexp, optional
 +;; single-apostrophe regexp?
 +;; Just about all will be the same anyway, so mostly language DEFAULT.
 +
 +;; For testing purposes, poorly-designed at first.
 +(defvar org-export-quotes-regexps
 +  '((DEFAULT 
 +  \\(?:\\s-\\|[[(]\\|^\\)\\(\\\)\\w 
 +  \\(?:\\S-\\)\\(\\\)\\s- 
 +  \\(?:\\s-\\|(\\|^\\)\\('\\)\\w
 +  \\w\\('\\)\\(?:\\s-\\|\\s.\\|$\\)
 +  \\w\\('\\)\\w)))

I'm not sure this variable can be used for both the buffer and the
export engine. Export back-ends will only see chunks of the paragraph.

For example, in the following text,

  He crossed the Rubicon and said: /Alea jacta est./

Plain text translators will see three strings:

  1. He crossed the Rubicon and said: \
  2. Alea jacta est.
  3. \

In case 1, you have an opening quote with nothing after it. In case 3,
you have a closing quote with nothing before or after it. Plain regexps
can't help here.

The only solution in can think of is to do quote substitutions in
paragraphs within the parse tree before they reach the translators (i.e.
with `org-export-filter-parse-tree-functions').

That's the only way to know if \ is an opening or a closing quote,
for example. The current approach won't work.

 +;; Generic function, usable by exporters, but they can define their own
 +;; instead.
 +(defun org-export-quotation-marks (text info replacements)
 +  Export quotation marks depending on language conventions.
 +TEXT is a string containing quotation marks to be replaced.  INFO
 +is a plist used as a communication channel.

Please document each argument in the docstring.

 +  (let* ((start 0)
 +  (regexps 
 +   (cdr 
 +(or 
 + (assoc (plist-get info :language)
 +org-export-quotes-regexps)
 + (assoc 'DEFAULT org-export-quotes-regexps

Use `assq' instead of `assoc' in the second case.

 +  (subs (cdr (or (assoc (plist-get info :language)
 +replacements)
 + (assoc en replacements
 +  (quotes (pairlis 

Re: [O] (no subject)

[Mark Shoulson]

Mark E. Shoulson mark at kli.org writes:


 
 All right, bottom line, this is sort of what I'm seeing.  I'm not 100% 
 sure which files should house these things, but something like this:
 
 1) a variable containing for each language regexp for each of: open 
 double-quote, close double-quote, open single-quote, close single-quote, 
 and maybe mid-word apostrophe.  Odds are these regexps are going to be 
 the same for just about all languages (the regexps detecting them, mind 
 you), so probably should have some sort of default that the alist can 
 just reference.  A language should also be allowed to define other quote 
 regexps in its list too.  We need these to be ordered, with a standard 
 set, so that we can have...
 
 2) for each *exporter* (including on-screen display), a variable that 
 defines, for each language, what the *substitution* will be for 
 open-double-quote, close-double-quote, etc.  Other extras can be defined 
 too.  That way we can have an exporter-independent way to detect quotes 
 to be smartified, but each exporter has its own way to smartify them.
 
 3) Since most exporters are probably going to be handling doing the 
 process approximately the same (match the regexp, stick in the 
 associated substitution), org-export.el should have a generic function 
 that does this which each exporter *may* call in (or as) its 
 quote-smartifier in its text translator, unless it needs something more 
 specific which it can provide itself.
 
 In terms of what is handled, the idea in my head is that we would expect 
 the writer to be using  or ' to surround their quotes, regardless of 
 what their native custom is (if they're doing it using their 
 language-specific quote-marks, we don't need to bother with all this 
 anyway).  Goal is to handle either quotes or 'quotes' in either 
 nesting (or no nesting, if someone does quote' for some reason), and 
 with any luck not get too confused with other uses of apostrophe.
 
 It makes sense to me, but I bet I explained it badly and people are 
 going to have all kinds of issues with it. :)
 
 No telling when (if?) I'll be able to produce something along these 
 lines, but it's something to start thinking about anyway.
 
 ~mark
 
 


Regarding the this is what I'm seeing, I paste at the bottom a
preliminary patch.  It is totally *not* worth actually applying it unless you
want to develop this; it's a snapshot mid-development.  But it does seem to
actually work.  The same set of regexps is used, and the same function, though
that is defeasible and an exporter can define its own.  The hardest part was
getting the onscreen versions showing right (also the most recently and probably
best tested, so the actual exporters might be more bumpy).  Actual substitutions
being used are not necessarily typologically sensible; chosen more so it's
easier to see the action of the process.  Nothing is in the right place, things
that should be customizables aren't... it's proof-of-concept. Am I going in the
right direction, as far as export-engine is concerned?

==

From 420048063e3fd2af1b019c48864d58d82cef62ef Mon Sep 17 00:00:00 2001
From: Mark Shoulson m...@kli.org
Date: Tue, 29 May 2012 23:01:12 -0400
Subject: [PATCH] Just barely works, nothing in the right places.  For
 entertainment purposes only.

---
 contrib/lisp/org-e-html.el  |5 
 contrib/lisp/org-e-latex.el |   53 +--
 contrib/lisp/org-export.el  |   52 ++
 lisp/org.el |   50 
 4 files changed, 133 insertions(+), 27 deletions(-)

diff --git a/contrib/lisp/org-e-html.el b/contrib/lisp/org-e-html.el
index de98493..b851713 100644
--- a/contrib/lisp/org-e-html.el
+++ b/contrib/lisp/org-e-html.el
@@ -1077,6 +1077,11 @@ in order to mimic default behaviour:
 
  Plain text
 
+(defvar org-e-html-quote-replacements
+  '((fr «   » ‘ ’ ’)
+(en “ ” ‘ ’ ’)
+(de „ “ ‚ ‘ ’))
+
 (defcustom org-e-html-quotes
   '((fr
  (\\(\\s-\\|[[(]\\|^\\)\ . «~)
diff --git a/contrib/lisp/org-e-latex.el b/contrib/lisp/org-e-latex.el
index 67e9197..540ebe1 100644
--- a/contrib/lisp/org-e-latex.el
+++ b/contrib/lisp/org-e-latex.el
@@ -687,6 +687,10 @@ during latex export it will output
 
  Plain text
 
+(defvar org-e-latex-quote-replacements
+  '((fr «~ ~» ‹~ ~› /!)
+(en (( )) .( ). /)))
+
 (defcustom org-e-latex-quotes
   '((fr
  (\\(\\s-\\|[[(]\\|^\\)\ . «~)
@@ -699,25 +703,22 @@ during latex export it will output
   Alist for quotes to use when converting english double-quotes.
 
 The CAR of each item in this alist is the language code.
-The CDR of each item in this alist is a list of three CONS:
-- the first CONS defines the opening quote;
-- the second CONS defines the closing quote;
-- the last CONS defines single quotes.
+The CDR of each item in this alist is a list of CONS:
+- the first CONS should define the opening quote;
+- the second CONS should define 

Re: [O] (no subject)

[Bastien]

Hi Eric and Rick,

Eric Schulte eric.schu...@gmx.com writes:

 Thanks for the patch, I would like to apply it.

 Have you signed the FSF papers for contribution to Org-mode and Emacs?

I guess some communication happened offlist -- if Rick does not have the
FSF papers, we need to mark the change as TINYCHANGE. 

 If you haven't would you be willing to?  See the Org-mode contribution
 instructions for more information.
 http://orgmode.org/worg/org-contribute.html

Also the ChangeLog should start with an uppercase letter and end with a
point...  sorry to nitpick on this, but I try to ease my life in
emacs-devel :)

Thanks for the patch anyway,

-- 
 Bastien

Re: [O] (no subject)

[Eric Schulte]

Thanks for the patch, I would like to apply it.

Have you signed the FSF papers for contribution to Org-mode and Emacs?
If you haven't would you be willing to?  See the Org-mode contribution
instructions for more information.
http://orgmode.org/worg/org-contribute.html

Thanks!

r...@rickster.com (Rick Frankel) writes:

 From 113bbbe1ce9540e2af8c613ba655599fc474cedd Mon Sep 17 00:00:00 2001
 From: Rick Frankel r...@rickster.com
 Date: Fri, 11 May 2012 16:54:32 -0400
 Subject: [PATCH] Add support for perl dbi to SQL code block

 * lisp/ob-sql.el (org-babel-execute:sql): Add dbi as a suppored engine.

 Invokes `dbish' with the arguments specified to :cmdline. Minimum is
 usually the dbi:{dbd} argument, plus the username and password if
 required.
 For example:

  lisp/ob-sql.el |   11 ++-
  1 file changed, 10 insertions(+), 1 deletion(-)

 diff --git a/lisp/ob-sql.el b/lisp/ob-sql.el
 index e3f6edd..c6d4790 100644
 --- a/lisp/ob-sql.el
 +++ b/lisp/ob-sql.el
 @@ -71,6 +71,11 @@ This function is called by `org-babel-execute-src-block'.
 (org-babel-temp-file sql-out-)))
(header-delim )
   (command (case (intern engine)
 +('dbi (format dbish --batch %s  %s | sed '%s'  %s
 +   (or cmdline )
 +   (org-babel-process-file-name in-file)
 +   /^+/d;s/^\|//;$d
 +   (org-babel-process-file-name out-file)))
  ('monetdb (format mclient -f tab %s  %s  %s
(or cmdline )
(org-babel-process-file-name in-file)
 @@ -90,7 +95,11 @@ This function is called by `org-babel-execute-src-block'.
   (or cmdline )))
  (t (error no support for the %s sql engine engine)
  (with-temp-file in-file
 -  (insert (org-babel-expand-body:sql body params)))
 +  (insert
 +   (case (intern engine)
 +  ('dbi /format partbox\n)
 +  (t ))
 +   (org-babel-expand-body:sql body params)))
  (message command)
  (shell-command command)
  (if (or (member scalar result-params)

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

Re: [O] (no subject)

[Bernt Hansen]

Eric Schulte eric.schu...@gmx.com writes:

 * lisp/ob-sql.el (org-babel-execute:sql): Add dbi as a suppored engine.

s/suppored/supported/

-Bernt

Re: [O] (no subject)

[Tom Regner]

Tom Regner t...@goochesa.de writes:

 From aea3adc952de33aa9acad94fbd9baa717b7b1a1e Mon Sep 17 00:00:00 2001
 From: Tom Regner t...@goochesa.de
 Rcpt To: emacs-orgmode@gnu.org
 Date: Mon, 23 Jan 2012 12:39:52 +0100
 Subject: [PATCH] ob.el Adhere to current :padline header during noweb 
 dereferencing.
[...]
I'm awfully sorry -- shall I remail the patch without the errorneous
empty line in between the headers, so that the patchwork server will
receive it?

kind regards,
Tom

Re: [O] (no subject)

[Eric Schulte]

I'd rather not change the default silently in this way.

Could you provide a minimal example of the difference you describe?  I
just tried viewing the expanded form of the following code block and saw
no difference between :noweb-ref and normal #+name: based expansions.

* examples

#+name: first
#+begin_src sh
  echo 1
#+end_src

#+begin_src sh :noweb-ref second
  echo 2
#+end_src

#+begin_src sh :noweb yes
  first
  second
#+end_src

Thanks,

Tom Regner t...@goochesa.de writes:

 From aea3adc952de33aa9acad94fbd9baa717b7b1a1e Mon Sep 17 00:00:00 2001
 From: Tom Regner t...@goochesa.de
 Rcpt To: emacs-orgmode@gnu.org
 Date: Mon, 23 Jan 2012 12:39:52 +0100
 Subject: [PATCH] ob.el Adhere to current :padline header during noweb 
 dereferencing.

 At the moment using the :noweb-ref: property approach on subtrees results in 
 the tangled code beeing broken
 because the newlines before the #+end_src line are excluded from the output. 
 This patch uses :padline
 to check if a newline should be added. The default being yes, tangling with 
 subtree mangling now produces correct
 results; code depending on the (errorneous?) behaviour would be broken though.
 ---
  lisp/ob.el |9 ++---
  1 files changed, 6 insertions(+), 3 deletions(-)

 diff --git a/lisp/ob.el b/lisp/ob.el
 index 47be708..398a997 100644
 --- a/lisp/ob.el
 +++ b/lisp/ob.el
 @@ -2211,13 +2211,16 @@ block but are passed literally to the 
 \example-block\.
(nth 4 i))
source-name)
 (let* ((body (org-babel-expand-noweb-references 
 i))
 -  (full (if comment
 +  (padded (if (not (string= no (cdr 
 (assoc :padline (nth 2 i)
 + (concat body 
 \n) 
 + body ))
 +  (full (if comment
  ((lambda (cs)
 (concat (c-wrap (car cs)) \n
 -   body \n
 +   padded \n
 (c-wrap (cadr cs
   (org-babel-tangle-comment-links 
 i))
 -  body)))
 +  padded)))
   (setq expansion (concat expansion full
   expansion)
 ;; possibly raise an error if named block doesn't exist

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

Re: [O] (no subject)

[Tom Regner]

Eric Schulte eric.schu...@gmx.com writes:

 I'd rather not change the default silently in this way.
I understand that.

 Could you provide a minimal example of the difference you describe?  I
 just tried viewing the expanded form of the following code block and saw
 no difference between :noweb-ref and normal #+name: based expansions.

 * examples

 #+name: first
 #+begin_src sh
   echo 1
 #+end_src

 #+begin_src sh :noweb-ref second
   echo 2
 #+end_src
 #+begin_src sh :noweb yes
   first
   second
 #+end_src

 Thanks,


Example document:
---%
* Subtree
  :PROPERTIES:
  :noweb-ref: subtree
  :END:
** Part 1
#+begin_src sh  
  Line One
#+end_src sh 
** Part 2
#+begin_src sh 
  Line Two
#+end_src sh
* Assamble it
#+begin_src sh :tangle yes :noweb tangle
  subtree
#+end_src sh
---%


tangled without my patch:

---%

Line OneLine Two
---%


tangled with my patch

---%

Line One
Line Two
---%