Re: [O] export of src block ignores :results

2016-09-30 Thread Thomas Alexander Gerds

right, this is what changed and setting :eval never-export on a each
block solves the problem. however, the new way breaks all my existing
org-code.

is there a reason why the header args have to be ignored when
org-export-babel-evaluate is nil? or asking more directly: would it be
possible to have another option, e.g.,

(setq org-export-babel-evaluate 'never-eval-obey-header-args)

such that the export process does never evaluate src code but header
arguments are always obeyed?

actually, my org-life improved alot when I found Ista Zahn's (cc) remark
in the org-mode mailing list about setting org-export-babel-evaluate to
nil. here is the quote:

,Fri, 21 Aug 2015 Re: [O] "user-error: No language for src block ...
||
| Unless you've restored sanity by setting org-export-babel-evaluate to  |
| nil. Personally I think this is not a good default. Source block   |
| evaluation and export are distinct actions, and I don't see why they   |
| should be linked by default.   |
||
| https://lists.gnu.org/archive/html/emacs-orgmode/2015-08/msg00940.html |
`

to me personally, the fact that one can separate the export process from
the source block evaluation in org-mode is one of the great advantages
over R-studio's markdown.

Thomas


"Charles C. Berry"  writes:

> On Thu, 29 Sep 2016, Thomas Alexander Gerds wrote:
>
>>
> [deleted]
>
> Follow the advice in the docstring for
> `org-export-babel-evaluate'. Use `:eval never-export'. Set
> org-export-babel-evaluate to t.
>
> Chuck
>
>

-- 
sent from nil



[O] Bug with capture template having %? cursor in the tags section

2016-09-30 Thread Michael Fiano
If I create a capture template that creates a headline such as:

"* %? :note:\n", then upon capturing the note tag is correctly shifted over
to org-tags-column.

However, if I position the %? cursor to be:

%?:note:
:note:%?

or anywhere in between, the tags are not written to the correct column,
instead with 1 space after the headline. I just wanted to manually define
some extra tags, instead of using %^g/%^G, but this messes up the column
placement.


[O] Bug capturing to a file while visiting buffer and auto-revert-mode active

2016-09-30 Thread Michael Fiano
If you visit an empty file buffer (0 bytes), turn auto-revert-mode on, and
capture something to this file, it will appear as if the buffer is still
empty. The cursor appears to be on an empty first line, but in reality, the
rest of the file contents are off screen and you must scroll up to see
them. Alternatively, manually calling revert-buffer will shift the view so
the file contents are displayed. It seems like auto-revert-mode and
org-capturing are not playing nice together. It took me a few hours to
realize that the buffer indeed was modified, but you had to scroll up to
see that it was.


Re: [O] Is there a *Org PDF LaTeX Output* buffer ?

2016-09-30 Thread Nick Dokos
Julien Cubizolles  writes:

> When an export from org to pdf fails, the error message refers to a *Org
> PDF LaTeX Output* buffer that doesn't seem to have been created on my
> setup. Is it an old message from a previous behaviour long gone ?
>

No, it should be present: it is created when you export to PDF through
LaTeX (it is created by org-latex-compile which is called by
org-latex-export-to-pdf). I just tried a (successful, but I don't
think it matters) export and was able to visit it afterwards.

Org-mode version 8.3.6 (release_8.3.6-1135-g0ba465 @ 
/home/nick/elisp/org-mode/lisp/)

-- 
Nick




Re: [O] [DOCS] Re: Making DocBook xml books from org mode?

2016-09-30 Thread Colin Baxter

Hello,

On Fri, Sep 30 2016, Nick Dokos wrote:

> Peter Davis  writes:

... snip ...
> ,
> | (1) DocBook export, available in previous Org-mode versions, has not
> | currently been ported to the new exporter, however the new ox-texinfo
> | backend can generate DocBook format. Once file.texi is created via
> | ox-texinfo, simply execute:
> | 
> | makeinfo --docbook file.texi
> `
>

No need to call makeinfo explicitly, "file.info" is an output option.

Best wishes,

Colin.



[O] Is there a *Org PDF LaTeX Output* buffer ?

2016-09-30 Thread Julien Cubizolles
When an export from org to pdf fails, the error message refers to a *Org
PDF LaTeX Output* buffer that doesn't seem to have been created on my
setup. Is it an old message from a previous behaviour long gone ?

Julien.




Re: [O] manipulate org tables using emacs-lisp

2016-09-30 Thread Thorsten Jolitz
Alan Schmitt  writes:

Hi Alan,

> Are there functions for manipulating org-tables using emacs-lisp? More
> precisely, I would like to refer to a table by its name, read some cells
> (either by position or by matching some given text with some text in the
> first row/column), and write in some cells.

,[ C-h f org-table-to-lisp RET ]
| org-table-to-lisp is an autoloaded compiled Lisp function in
| ‘../org-mode/lisp/org-table.el’.
| 
| (org-table-to-lisp  TXT)
| 
| Convert the table at point to a Lisp structure.
| The structure will be a list.  Each item is either the symbol ‘hline’
| for a horizontal separator line, or a list of field values as strings.
| The table is taken from the parameter TXT, or from the buffer at point.
| 
| [back]
`

returns the table as a nested list you can map with lots of Elisp
functions (like mapcar). 

Ex.:

| my | tab |
|  1 |   2 |

=>

(("my" "tab") ("1" "2"))

-- 
cheers,
Thorsten




Re: [O] [DOCS] Re: Making DocBook xml books from org mode?

2016-09-30 Thread Nick Dokos
Colin Baxter  writes:

> Hello,
>
> On Fri, Sep 30 2016, Nick Dokos wrote:
>
>> Peter Davis  writes:
>
> ... snip ...
>> ,
>> | (1) DocBook export, available in previous Org-mode versions, has not
>> | currently been ported to the new exporter, however the new ox-texinfo
>> | backend can generate DocBook format. Once file.texi is created via
>> | ox-texinfo, simply execute:
>> | 
>> | makeinfo --docbook file.texi
>> `
>>
>
> No need to call makeinfo explicitly, "file.info" is an output option.
>

But the OP wanted Docbook XML, not info.

-- 
Nick




Re: [O] [DOCS] Re: Making DocBook xml books from org mode?

2016-09-30 Thread Peter Davis

On Fri, Sep 30, 2016, at 03:37 PM, Nick Dokos wrote:
> Peter Davis  writes:
> 
> > Hi, Tom,
> >
> > On Fri, Sep 30, 2016, at 11:33 AM, Thomas S. Dye wrote:
> >> ... stuff excised ...
> >> 
> >> This was part of the old exporter.  It hasn't been ported to the new one.
> >
> > Thanks, Tom. Christian's post made me wonder if this was hiding in the
> > background somewhere.
> >
> 
> There is a footnote in the (incomplete) page
> 
> http://orgmode.org/worg/exporters/ox-overview.html
> 
> that says:
> 
> ,
> | (1) DocBook export, available in previous Org-mode versions, has not
> | currently been ported to the new exporter, however the new ox-texinfo
> | backend can generate DocBook format. Once file.texi is created via
> | ox-texinfo, simply execute:
> | 
> | makeinfo --docbook file.texi
> `
> 
> I wonder if that will meet the OP's requirements.
> 

Hi, Nick,

Yes, I did see that, and I did succeed in creating a DocBook file by
exporting to texi and then converting with makeinfo. It's a bit
unwieldy, but it will do in a pinch. I'm not sure how this compares with
pandoc.

I'd really like to be able to set things like doctype, etc.
automatically, but there doesn't seem to be a way to do that in the org
file so that it would survive getting passed through texi into docbook
xml (or pandoc, for that matter).

Thanks,
-pd



-- 
  Peter Davis
  www.techcurmudgeon.com



Re: [O] [DOCS] Re: Making DocBook xml books from org mode?

2016-09-30 Thread Nick Dokos
Peter Davis  writes:

> Hi, Tom,
>
> On Fri, Sep 30, 2016, at 11:33 AM, Thomas S. Dye wrote:
>> ... stuff excised ...
>> 
>> This was part of the old exporter.  It hasn't been ported to the new one.
>
> Thanks, Tom. Christian's post made me wonder if this was hiding in the
> background somewhere.
>

There is a footnote in the (incomplete) page

http://orgmode.org/worg/exporters/ox-overview.html

that says:

,
| (1) DocBook export, available in previous Org-mode versions, has not
| currently been ported to the new exporter, however the new ox-texinfo
| backend can generate DocBook format. Once file.texi is created via
| ox-texinfo, simply execute:
| 
| makeinfo --docbook file.texi
`

I wonder if that will meet the OP's requirements.

-- 
Nick




Re: [O] Making DocBook xml books from org mode?

2016-09-30 Thread Nick Dokos
Marcin Borkowski  writes:

> On 2016-09-29, at 20:04, Peter Davis  wrote:
>
>> I've started a new position in which I have to create and maintain a
>> large set of documents in DocBook xml format. For new books, I'd really
>> like to use org mode, since a) I'm already familiar with it, b) I love
>> it, and c) I believe it does (or can be made to do) nearly everything I
>> need.
>
> Nice.  Of many things XML is ill-suited to, marking text up is a nice
> exception: it seems really good at it (definitely way better than LaTeX,
> of which I'm a great fan!).
>

Why do you think so? I've used XML lightly over the years and I have found
it to be a bear. LaTeX has its own problems but I grew up with it, so I guess
I'm less conscious of its flaws (but I rarely write LaTeX any more: org has
subsumed it). Should I change my mind?

>>  3. The direct route from org to DocBook xml seems to be missing. From
>

My memory might be playing tricks on me, but wasn't there a docbook
exporter at some point? Maybe it did not survive the 8.x transition?
Or am I misremembering?

-- 
Nick




Re: [O] export of src block ignores :results

2016-09-30 Thread Charles C. Berry

On Thu, 29 Sep 2016, Thomas Alexander Gerds wrote:




[deleted]



anyway, the original problem is not solved yet.
org-babel-current-result-hash is related to the execution of the src
block which is independent of the export process since I have

(setq org-export-babel-evaluate nil).

and the problem that the results are exported in case of ":results code"
persists when I set (setq org-babel-hash-show-time nil)



Follow the advice in the docstring for `org-export-babel-evaluate'. Use 
`:eval never-export'. Set org-export-babel-evaluate to t.




so, unfortunately my question remains. which function in the export
process interprets the "results code" option?



With org-export-babel-evaluate set to nil, none of the babel functions 
are run. And none of the export transcoders take account of the header 
args, AFAICS. So the answer is `none of them'.


Chuck



Re: [O] [DOCS] Re: Making DocBook xml books from org mode?

2016-09-30 Thread Peter Davis
Hi, Tom,

On Fri, Sep 30, 2016, at 11:33 AM, Thomas S. Dye wrote:
> ... stuff excised ...
> 
> This was part of the old exporter.  It hasn't been ported to the new one.

Thanks, Tom. Christian's post made me wonder if this was hiding in the
background somewhere.

Cheers,
-pd

-- 
  Peter Davis
  www.techcurmudgeon.com



Re: [O] Fwd: comment lines inside org tables

2016-09-30 Thread Nicolas Goaziou
Hello,

Rolf Sander  writes:

> I want to add a comment line into the file that does not disturb the
> table.

Disturb the table wrt to what action? Alignment? This is a minor issue
if you fix an arbitrary column width, isn't it?

> Like a "|---+---+---|" hline. I don't want any action. All
> programming languages have the option to add comments to the source
> code.

But Org is not a programming language, and an Org document is not source
code.

> Okay, so my question turns into a feature request now...

Allowing to comment anything is a can of worms I really don't want to
open. It complicates a lot of code for little benefit.

> I have started to modify defun org-table-align. With the modification,
> org-tbl now ignores all lines starting with "|-/". For me it works
> fine.

Sorry, but you're barely scratching the surface of the problem. Tables
are not just about alignment. Formulas don't handle these special lines,
neither do exported tables.

Again, this implies a serious work on org-table.el, and it would
introduce inconsistencies with other parts of Org (e.g., lists, where
you cannot comment an item, or even the syntax for commenting table
rows, which would be unusual).

All in all, I think there are more important itches to scratch for the
time being. Of course, YMMV.


Regards,

-- 
Nicolas Goaziou



Re: [O] [DOCS] Re: Making DocBook xml books from org mode?

2016-09-30 Thread Thomas S. Dye
Aloha pd,

Peter Davis writes:

> On Fri, Sep 30, 2016, at 05:16 AM, Christian Moe wrote:
>> 
>> Peter Davis writes:
>> 
>> >  3. The direct route from org to DocBook xml seems to be missing.
>> 
>> It's gone extinct, but there is a fossil record of it in the online
>> manual:
>> 
>>   http://orgmode.org/guide/DocBook-export.html
>> 
>> It's not linked to from the TOC, but turned up in a DuckDuckGo
>> search. It should probably be carefully excavated and placed in the
>> Museum of Paleorgology.
>
> Thanks, Christian. This say I can use
>
> C-c C-e D
>
> but that gives me 'Invalid key', and it doesn't show up in the export
> menu.

This was part of the old exporter.  It hasn't been ported to the new one.

All the best,
Tom

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



Re: [O] Making DocBook xml books from org mode?

2016-09-30 Thread Peter Davis


On Fri, Sep 30, 2016, at 05:37 AM, Marcin Borkowski wrote:
> 
> On 2016-09-29, at 20:04, Peter Davis  wrote:
> 
> > I've started a new position in which I have to create and maintain a
> > large set of documents in DocBook xml format. For new books, I'd really
> > like to use org mode, since a) I'm already familiar with it, b) I love
> > it, and c) I believe it does (or can be made to do) nearly everything I
> > need.
> 
> Nice.  Of many things XML is ill-suited to, marking text up is a nice
> exception: it seems really good at it (definitely way better than LaTeX,
> of which I'm a great fan!).
>

I'm also a big LaTeX fan, but I don't use it often enough to remember
everything I need. I rely on copying stretches from documents I created
earlier, or constantly having to Google for solutions.

One thing I like about org-mode for creating documents (as opposed to
all its other uses), is the fact that I can easily remember the simple
mark-up, see reminders on screen while editing, and easily generate HTML
and PDF.
 
> >  3. The direct route from org to DocBook xml seems to be missing. From
> 
> Why not start with the HTML exporter and write your own one?  It's quite
> fun, and can be done in reasonable time.
>

For some definition of "reasonable." Seriously, I might want to do this
as an exercise sometime, but I can't wait for that right now.

> 
> >  4. [LONGSHOT] Is there any way to /import/ docbook xml into org mode?
> 
> XSLT?
>

Yes, that's a good option I hadn't considered.

> 
> Hth,
> 

Definitely. Thanks!

-pd

-- 
  Peter Davis
  www.techcurmudgeon.com



Re: [O] Fwd: comment lines inside org tables

2016-09-30 Thread Rolf Sander

Hello Nicolas,


Then I don't understand what you really want. You want to comment a
row, but it's not clear wrt to what action.


I want to add a comment line into the file that does not disturb the
table. Like a "|---+---+---|" hline. I don't want any action. All
programming languages have the option to add comments to the source
code. The comment does not trigger any action, and the result of
executing the code is the same, whether with or without comment lines.
It would be nice if org-tbl would allow comment lines as well.


Anyway, in the general case, there is no way to comment a row.


Okay, so my question turns into a feature request now...

I have started to modify defun org-table-align. With the modification,
org-tbl now ignores all lines starting with "|-/". For me it works fine.
However, please let me know if you see any side-effects. You can
download the full defun here:

http://www.rolf-sander.net/tmp/org-table-align-new.el

And here is a diff to the original code:

***
diff -U 1 org-table-align-old.el org-table-align-new.el
@@ -63,4 +63,12 @@
 ;; At the same time, we remove trailing space.
+(setq lines0 (mapcar (lambda (l)
+  (cond ((string-match "^ *|-" l)
+ nil)
+((string-match "[ \t]+$" l)
+ (substring l 0 (match-beginning 0)))
+(t l))
+  )
+   lines))
 (setq lines (mapcar (lambda (l)
- (if (string-match "^ *|-" l)
+ (if (string-match "^ *|-\\($\\|[^/]\\)" l)
  nil
@@ -74,3 +82,3 @@
(org-split-string l " *| *"))
- (delq nil (copy-sequence lines
+  (delq nil (copy-sequence lines0
 ;; How many fields in the longest line?
@@ -164,5 +172,9 @@
   (lambda (l)
-(if l (apply 'format rfmt
- (append (pop fields) emptystrings))
-  hfmt))
+ (cond ((eq l nil)
+hfmt)
+   ((string-match "^ *|-/" l)
+(concat l "\n"))
+   (t
+(apply 'format rfmt
+   (append (pop fields) emptystrings)
   lines ""))
***

 Best regards
Rolf

--
---
  Rolf Sander  phone: [+49] 6131/305-4610
  Max-Planck Institute of Chemistryemail: rolf.san...@mpic.de
  PO Box 3060, 55020 Mainz, Germany homepage: www.rolf-sander.net
---
   www.atmospheric-chemistry-and-physics.net
www.geoscientific-model-development.net
---



Re: [O] [DOCS] Re: Making DocBook xml books from org mode?

2016-09-30 Thread Peter Davis


On Fri, Sep 30, 2016, at 05:16 AM, Christian Moe wrote:
> 
> Peter Davis writes:
> 
> >  3. The direct route from org to DocBook xml seems to be missing.
> 
> It's gone extinct, but there is a fossil record of it in the online
> manual:
> 
>   http://orgmode.org/guide/DocBook-export.html
> 
> It's not linked to from the TOC, but turned up in a DuckDuckGo
> search. It should probably be carefully excavated and placed in the
> Museum of Paleorgology.

Thanks, Christian. This say I can use

C-c C-e D

but that gives me 'Invalid key', and it doesn't show up in the export
menu.

Thanks,
-pd

-- 
  Peter Davis
  www.techcurmudgeon.com



Re: [O] Bug: Several small documentation problems [8.3.6 (8.3.6-4-g4835be-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20160926/)]

2016-09-30 Thread Jorge
On 29 September 2016 at 17:36, Nicolas Goaziou  wrote:
> I think "grandparent" is correct. In the following document
>
>   * H1
>   ** H2
>   Text<--point
>
> "H2" is the parent headline of "Text" and as a consequence, "H1" is its
> grandparent.
What if point is in the headline, which is often the case?  Besides the
docstring is inconsistent:
  With two universal prefix arguments, insert the heading at the end
  of the grandparent subtree.  For example, if point is within a
  2nd-level heading, then it will insert a 2nd-level heading at the
  end of the 1st-level parent heading.

In the first sentence it says "grandparent subtree", whereas in the second
sentence it says "parent heading".  And the manual says "parent":
  Calling this command with `C-u C-u' will unconditionally respect
  the headline's content and create a new item at the end of the
  parent subtree.

Perhaps uniformity of terminology would help here.

> You are right, M-RET and C-RET are confusing, and making C-u M-RET
> a duplicate of C-RET is wasting some important keybinding. This was
> discussed on this ML already (with Rasmus) but led nowhere so far.
>
> In any case, it is more future-proof to not insist on the fact that
> C-RET is C-u M-RET.
I think that, whether we describe both behaviors separately or tell
the user that
C-RET is equivalent to C-u M-RET, the commitment (to not change the behavior)
is the same.  But if you still think that describing both separately is more
future-proof, I won't argue.

But I still ask you to look at the other points I made about that manual
section: that it doesn't adequately explain the effect of C-u M-RET, and that
the description of C-RET is actually wrong.

> Thank you for this tedious, yet very important work.
Thank you very much for working on Org!

-- 
• I am Brazilian.  I hope my English is correct and I welcome corrections.
• Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z.
• Free (as in free speech) software for Android: https://f-droid.org/



Re: [O] Making DocBook xml books from org mode?

2016-09-30 Thread Marcin Borkowski

On 2016-09-29, at 20:04, Peter Davis  wrote:

> I've started a new position in which I have to create and maintain a
> large set of documents in DocBook xml format. For new books, I'd really
> like to use org mode, since a) I'm already familiar with it, b) I love
> it, and c) I believe it does (or can be made to do) nearly everything I
> need.

Nice.  Of many things XML is ill-suited to, marking text up is a nice
exception: it seems really good at it (definitely way better than LaTeX,
of which I'm a great fan!).

>  3. The direct route from org to DocBook xml seems to be missing. From

Why not start with the HTML exporter and write your own one?  It's quite
fun, and can be done in reasonable time.

I did a talk about writing your own Org exporter during EmacsConf 2015;
also, I had a plan (and I even started) for a series of blog posts on
that topic, but I don't have time for that now.  Still, you might want
to pursue this road - you'd have (as opposed to Pandoc, which admittedly
is a great tool, but has its limitations, as Joost mentioned) full
control over what get exported to what.

>  4. [LONGSHOT] Is there any way to /import/ docbook xml into org mode?

XSLT?

> Thank you very much.
>
> -pd

Hth,

-- 
Marcin Borkowski



Re: [O] Org Agenda and recurring icalendar events

2016-09-30 Thread Eric S Fraga
On Friday, 30 Sep 2016 at 08:54, cschr wrote:
> Hello together
>
> Im now running Emacs 25.1 with Org 8.3.5 on Windows.  I love Emacs and
> Orgmode and I want to use it instead of Microsoft Office.  But in
> order to replace MS-Outlook calendar by Org Agenda, and in order to
> sync Org Agenda with my Android phone, I would need all icalendar
> functionality, which is used by MS-Outlook and by Android, implemented
> in Orgmode. Most urgently missing are recurrence features like RRULE,
> EXDATE, DTSTART, DTEND, etc, and import and export of those from and
> to icalendar.  The current implementation is only rudimentary.

Rudimentary but works, at least for me, albeit using Google calendar and
not Outlook as the latter is so non-standard that it's a
nightmare.  Google is marginally better although not fantastic either.

With Google calendar, the easiest way to have org and Android/Windows
synchronised is to use MobileOrg and have it take care of the
synchronisation with the calendar.  This will handle many but not all of
your cases, specifically excluded dates and end dates for recurring
events which org does not support out of the box.

Alternatively, you can have two separate processes for synchronisation
in each direction: converting from ics to org and vice versa.  This has
been discussed many times on the list and there is material on worg.

> I had sent the below emails via bug-gnu-emacs, but there was no
> response – was it the wrong place to send to ?

Not sure whether wrong or not but this mailing list is the best place
for discussions of this form as you are requesting a feature as opposed
to reporting a bug.


-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.1.1, Org release_8.3.6-1131-gd68497



[O] [DOCS] Re: Making DocBook xml books from org mode?

2016-09-30 Thread Christian Moe

Peter Davis writes:

>  3. The direct route from org to DocBook xml seems to be missing.

It's gone extinct, but there is a fossil record of it in the online
manual:

  http://orgmode.org/guide/DocBook-export.html

It's not linked to from the TOC, but turned up in a DuckDuckGo
search. It should probably be carefully excavated and placed in the
Museum of Paleorgology.

Yours,
Christian



[O] Org Agenda and recurring icalendar events

2016-09-30 Thread cschr
Hello together

 

Im now running Emacs 25.1 with Org 8.3.5 on Windows.   I love Emacs and
Orgmode and I want to use it instead of Microsoft Office.   But in order to
replace MS-Outlook calendar by Org Agenda, and in order to sync Org Agenda
with my Android phone, I would need all icalendar functionality, which is
used by MS-Outlook and by Android, implemented in Orgmode. Most urgently
missing are recurrence features like RRULE, EXDATE, DTSTART, DTEND, etc, and
import and export of those from and to icalendar.   The current
implementation is only rudimentary.

 

Emacs diary is not suitable - import and export from and to icalendar are
also not working properly for most recurring events, and of course it misses
the Orgmode features.

 

My idea would be to introduce recurring icalendar elements like RRULE,
EXDATE, DTSTART and DTEND as Org Properties, which would make importing and
exporting them straightforward, I guess. Main work would be to make these
dates show up in the Org Agenda properly.

 

Wonderful would be to have this functionality as an official part of orgmode
and maintained

 

A similar work was started in 2013 already:
http://thread.gmane.org/gmane.emacs.orgmode/74391

 

But that’s all I was able to find on the web about this subject – it seems
no work is going on here - or does anybody know there is?

 

Im wondering if this idea is of interest to anybody else – to me this is a
real killer feature for using Org Agenda.

 

I had sent the below emails via bug-gnu-emacs, but there was no response –
was it the wrong place to send to ?

 

I don’t have Emacs development knowledge.  Is there any expert here who
could tell me if this is possible at all, whether this could become part of
official orgmode and how, and what could the effort be – is this a few
weeks, or a few months, or much more work ?

 

Thank you so much

 

Kind regards

Chris

 

 

 

 

From: cschr [mailto:cs...@freenet.de] 
Sent: 12 August 2016 09:34
To: bug-gnu-em...@gnu.org
Subject: RE: Subject: 25.0.94; Proposal to make orgmode agenda really useful

 

RRULE might better be an orgmode PROPERTY too, like proposed for Recurrence
End Date and Exceptions in

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

 

In fact, its several properties, but not all are needed for Android Sync. I
only need: RRULE_FREQ, RRULE_INTERVAL, RRULE_BYDAY, RRULE_COUNT,
RRULE_UNTIL. 

Also, EXDATE is needed which is not part of RRULE but part of VEVENT, and
TRIGGER which is part of VALARM

 

 

From: cschr [  mailto:cs...@freenet.de] 
Sent: 10 August 2016 20:27
To:   bug-gnu-em...@gnu.org
Subject: Subject: 25.0.94; Proposal to make orgmode agenda really useful

 

I love emacs - its incredibly powerful and helpful - its almost all i

ever dreamt of. 

 

One thing i miss urgently: make org agenda files fully sync with my

icalendar files, including recurrance with end dates, and including alarms.

RRule Exceptions would also be helpfull. 

 

Here are my ideas, and I would be curious to hear your plans:

 

1. Would it be an idea to implement a DIARY_RRULE function which can be used

in date sexpr in org agenda (and maybe also the diary) and which accepts

an icalendar RRULE string as parameter ?   This could make icalendar

export and import very easy (just copy the string), and implementation

in elisp shouldnt be too hard (but thats something I can only guess -

you know it better).

 

2. exceptions and end dates could also be implemented as org properties,

as already proposed by  
http://thread.gmane.org/gmane.emacs.orgmode/74391

 

3. At the moment i am stuck because my icalendar file can only be

imported into the diary: import into org files is restricted to single
events

(and maybe very simple recurring events?). And the diary import uses
diary-date

a lot which cannot be exported, and diary export does not create VALARms,

and the ORG features are not available for the diary.

 

Thanks a lot for your great work !!!

Kind regards – Christoph Schröder, Cham, Switzerland

 

 



[O] manipulate org tables using emacs-lisp

2016-09-30 Thread Alan Schmitt
Hello,

Are there functions for manipulating org-tables using emacs-lisp? More
precisely, I would like to refer to a table by its name, read some cells
(either by position or by matching some given text with some text in the
first row/column), and write in some cells.

Thanks,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2016-08: 402.25, 2015-08: 398.93


signature.asc
Description: PGP signature