Re: [O] Repeated tasks marked as DONE

[Tomasz Piotrowski]

Hi Myles,

Thanks a lot for your help. I also do not quite understand the way it
works, and I hope there must be a simpler way to mark previous occurrences
as "DONE", while those in the future as "TO DO", for a given reccurring
event.

If something else is available, please advise.

Kind regards,

Tomasz

2016-01-27 13:47 GMT+01:00 Myles English :

>
> Myles English writes:
>
> > Hello Tomasz,
> >
> > Tomasz Piotrowski writes:
> >
> >> I have a simple question, yet couldn't find an equally simple answer to
> >> it. Namely, if I set a repeated task (everyday, say), the agenda
> >> shows this tasks _for all days_, even in the past.
> >>
> >> How can I mark a repeated task DONE if it is completed for a given day,
> >> while keeping it as TODO for the future?
> >
> > This is what works for me, the last_repeat property seams to enable the
> > behaviour you describe, the logbook is something extra I vaguely
> > remember setting up:
> >
> > * TODO Put recycle bin out
> >  SCHEDULED: <2016-01-28 Thu +2w>
> > :PROPERTIES:
> > :LAST_REPEAT: [2016-01-16 Sat 13:10]
> > :END:
> > :LOGBOOK:
> > - State "DONE"   from "TODO"   [2016-01-16 Sat 13:10]
> > - State "DONE"   from "TODO"   [2016-01-02 Sat 17:41]
> > - State "DONE"   from "TODO"   [2015-12-21 Mon 16:22]
> > :END:
>
> And see also the variable org-agenda-repeating-timestamp-show-all.
> (Having read the available help, don't quite understand way it working
> for me...)
>
> Myles
>
>

Re: [O] Orgmode testsuite

[Nicolas Goaziou]

Hello,

Christian Kruse  writes:

> Do you need more information on that? I hit the error, too.

It is fixed already. 

Unfortunately, Org ELPA updates every Monday AFAICT. So, unless someone
can refresh the Org package there, we'll have to live with it until next
week.

Regards,

-- 
Nicolas Goaziou

Re: [O] Orgmode testsuite

[Christian Kruse]

Hi,

Nicolas Goaziou  writes:
>> When I'm firing up org agenda, I got an error in the function `org-activate-
>> plain-links`
>>
>> (wrong-type-argument listp org-link)
>
> Indeed. It should be fixed. Thank you.

Do you need more information on that? I hit the error, too.

Best regards,
-- 
Christian Kruse
https://wwwtech.de/about


signature.asc
Description: PGP signature

Re: [O] Conditionally formatting org-html-postamble-format

[Kaushal Modi]

Thank you guys.

With your help, I came up with this solution and it works great! I tested
it with all 4 combinations (author=nil/non-nil and date=nil/non-nil).

# #+AUTHOR:
#+AUTHOR: Kaushal Modi
# #+DATE:
#+DATE: {{{time(%b %e %Y\, %a)}}}

;; Customize the HTML postamble
(defun modi/org-html-postamble-fn (info)
  "My custom postamble for org to HTML exports.
INFO is the property list of export options."
  (let ((author (car (plist-get info :author)))
(creator (plist-get info :creator))
(date (car (org-export-get-date info)))
(d1 ""))
(concat "Exported using "
d1 "class=\"creator\">" creator d2 ; emacs and org versions
(when author
  (concat " by " author))
(when date
  (concat " on " d1 "class=\"date\">" date d2))
".")))
(setq org-html-postamble #'modi/org-html-postamble-fn) ; default: 'auto

Re: [O] Bug: Export breaks on documents with title [8.3.3 (8.3.3-26-ge92a06-elpaplus @ /Users/leafac/.emacs.d/elpa/org-plus-contrib-20160125/)]

[Kyle Meyer]

Hello,

Leandro Facchinetti  writes:

[...]

> Trying to export a file with a `#+TITLE:' set leads to the error:
>
> apply: Wrong type argument: listp, #("Writings" 0 8 (:parent (#0)))
>
> Sample file:
>
> #+TITLE: Writings
>
> The error happens regardless of the export backend.
>
> I already ran `emacs -q' and the problem persists.

We've seen similar error due to issues with installation. For example,

  http://thread.gmane.org/gmane.emacs.bugs/110037/focus=103649

Please see if re-installing without the builtin Org loaded helps.

-- 
Kyle

Re: [O] [PATCH] org-attach.el: Get attachments from git annex

[Rasmus]

Hi Erik,

Thanks for the updated patch!

A couple of more comments follow.
I hope I’m not being too annoying! 

Erik Hetzner  writes:

> +(defcustom org-attach-annex-confirm-get-function #'y-or-n-p
> +  "Function to call to confirm if Org should call git annex get if necessary.
> +If t, always get, if nil, never get."


Please note that the function should accept one argument cf. your code
below.  Also, I wonder if there’s really a point in having the increased
flexibility of a function over just: t, nil and ’ask.

> +  :group 'org-attach
> +  :package-version '(Org . "8.3")
> +  :type '(choice
> +   (const :tag "confirm with y-or-n" y-or-n-p)
> +   (const :tag "always get from annex if necessary" t)
> +   (const :tag "never get from annex" nil)))

Nitpick: package version should be org 9.  You should add :version tag as
well.  Probably "25.1" is good.  Then we can mass-update them all when we
are allowed to merge...

> +(defun org-attach-annex-get-maybe (path)
> +  "Call git annex get PATH if using git annex."
> +  (when (and (org-attach-use-annex)
> +  (not (string-equal "found"
> + (shell-command-to-string
> +  (format "git annex find --format=found 
> --in=here %s" (shell-quote-argument path))
> +(if (if (functionp org-attach-annex-confirm-get-function)
> + (funcall org-attach-annex-confirm-get-function (format "Run git 
> annex get %s? " path))
> +   org-attach-annex-confirm-get-function)
> + (progn (message "Running git annex get \"%s\"." path)
> +(call-process "git" nil nil nil "annex" "get" path))
> +  (error "File %s stored in git annex but it is not available, and was 
> not retrieved" path

Can’t you factor out the inner "if", e.g. to an outer let?  Shouldn’t you
check the return of annex get and show a warning or an error if it fails?
It seems the error is only called if the inner if fails (in which case the
error message is not precise since we didn’t try to retrieve the file).

>  (defun org-attach-commit ()

Looks fine. 

>  cleantest:
> +# git annex makes files 444, change to user writable so we can delete them
> + if [ -d $(testdir) ] ; then chmod u+w -R $(testdir) ; fi
>   $(RMR) $(testdir)

I wonder if it would be better to directly target the files you use?  I
don’t think there’s a case where changing the mod of the testdir is a
problem though


> +;;; test-org-attach.el --- Tests for Org Attach

Skipped again...

-- 
Slowly unravels in a ball of yarn and the devil collects it

Re: [O] [PATCH] ox-koma-letter.el: Add support for 'location' koma variable

[Rasmus]

Hi Myles,

Thanks for your patch.

It always makes me happy when someone is using ox-koma-letter.

Myles English  writes:

> Often when writing a letter I want to include "Your Ref: xyz" or
> "Account No.: 1234" and a good place to do this is below the sender's
> address field and above the date (and 'place') field(s).  This space
> becomes filled with the contents of the koma variable called 'location'.
> This patch enables filling this variable via org-mode's contrib
> ox-koma-letter exporter.

Aside: it sounds like what you need is "yourref", maybe "yourmail",
"myref", "customer", and "invoice".  These are typed in the same line as
the date and place.  In my manual it’s described around pp. 180.

On to "location".  From the manual pp. 195 it looks like it is usually
something akin to an address field on the right side of the head.  I think
"location" should be settable via a special :location: heading, probably
with special line breaking rules like the :to:/:from: special headings.
We can allow a #+LOCATION keyword in addition, but need not.  All IMO.
WDYT?

Thanks,
Rasmus

-- 
This message is brought to you by the department of redundant departments

[O] Bug: Habits will not correctly reset timestamp [8.3.2 (release_8.3.2-570-gc17fcc @ /home/swflint/.emacs.d/org-mode/lisp/)]

[Samuel W. Flint]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


See my previous bug report.  This still happens.

If I have a heading like so:

* TODO Something
SCHEDULED: <2016-01-17 Sun .+1w/2w>
:PROPERTIES:
:STYLE: habit
:END:

And execute C-c C-t d on the heading, the following appears:

* TODO Something
:PROPERTIES:
:STYLE: habit
:END:

This is incorrect behavior, and I'm unable to use org-habits correctly.

Thanks,

Sam

Emacs  : GNU Emacs 24.5.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.17.8)
 of 2015-09-11 on buildvm-21.phx2.fedoraproject.org
Package: Org-mode version 8.3.2 (release_8.3.2-570-gc17fcc @ 
/home/swflint/.emacs.d/org-mode/lisp/)

--
Samuel W. Flint
4096R/266596F4
  (9477 D23E 389E 40C5 2F10  DE19 68E5 318E 2665 96F4)
(λs.s s) λs.s s


signature.asc
Description: PGP signature

Re: [O] Bug: Export breaks on documents with title [8.3.3 (8.3.3-26-ge92a06-elpaplus @ /Users/leafac/.emacs.d/elpa/org-plus-contrib-20160125/)]

[Leandro Facchinetti]

Hi, Org Mode contributors.

I was able to figure out the issue: my versions of the packages `org'
and `org-plus-contrib' were not matching. Updating both solved the
issue.

Sorry to bother, thanks for the attention and---again---thanks for Org
Mode. It rocks!

Best.
-- 
Leandro Facchinetti 
https://www.leafac.com
GPG key: 3DF3D583

Re: [O] Conditionally formatting org-html-postamble-format

[Robert H. Klein]

Hi Kaushal,

> Thanks for the reply.
> 
> > how about using a postamble function instead of
> > html-postamble-format  
> 
> Does it mean that I need to look into modifying the
> org-html--build-pre/postamble function?
> 
> If so, I will start looking into it but it will take a while as it
> full of elisp that I have never used (until today maybe):
> format-spec, plist-get and a lot of assoc's and assq's :)

No, I have two functions, one for the preamble, one for the postamble,
both returning a string.  In the project alist I set :html-preamble
and :html-postamble to those functions (beware of typos):


  ;; pre- and postamble for html export
  (defun linux-e-preamble (info)
(with-temp-buffer
  (insert-file-contents "~/linuxdocs/html/preamble.html")
  (let ((title (car (plist-get info :title
(when title
  (if (stringp title)
  (let ((case-fold-search t)) ; case-insensitive
(goto-char (point-min))
(while (search-forward "" nil t)
  (replace-match title))
  (buffer-string)))

  (defun linux-e-postamble (info)
(with-temp-buffer
  (insert-file-contents "~/linuxdocs/html/postamble.html")
  (buffer-string)))

  ;; add linux to org-publish-poject-alist
  (add-to-list 'org-publish-project-alist
   '("linux-e-html"
 :base-directory "~/linuxdocs"
 :base-extension "org"
 :publishing-directory "~/public_html/linuxdocs"
 :publishing-function org-html-publish-to-html
 :html-head "" :html-head-include-default-style nil
 :html-head-include-scripts nil
 :html-preamble linux-e-preamble
 :html-postamble linux-e-postamble
 ))


Best regards
Robert

Re: [O] Conditionally formatting org-html-postamble-format

[Nick Dokos]

Kaushal Modi  writes:

> Hi Robert,
>
> Thanks for the reply.
>
>> how about using a postamble function instead of html-postamble-format
>
> Does it mean that I need to look into modifying the 
> org-html--build-pre/postamble function?
>

No, Robert is talking about the variable org-html-postamble,
which you can set to a function. No need to muck around with
the internals of org.

C-h v org-html-postamble says

,
| org-html-postamble is a variable defined in ‘ox-html.el’.
| Its value is auto
| 
| Documentation:
| Non-nil means insert a postamble in HTML export.
| 
| When set to ‘auto’, check against the
| ‘org-export-with-author/email/creator/date’ variables to set the
| content of the postamble.  When set to a string, use this string
| as the postamble.  When t, insert a string as defined by the
| formatting string in ‘org-html-postamble-format’.
| 
| When set to a function, apply this function and insert the
| returned string.  The function takes the property list of export
| options as its only argument.
| 
| Setting :html-postamble in publishing projects will take
| precedence over this variable.
`

Try

--8<---cut here---start->8---
(defun foo (info)
  "This is my postamble")

(setq org-html-postamble (function foo))
--8<---cut here---end--->8---

and complicate the function as necessary to produce what you want.
Of course, you can use an anonymous function too:

--8<---cut here---start->8---
(setq org-html-postamble (function (lambda (info)
 "This is my postamble")))
--8<---cut here---end--->8---

--
Nick

[O] Bug: Export breaks on documents with title [8.3.3 (8.3.3-26-ge92a06-elpaplus @ /Users/leafac/.emacs.d/elpa/org-plus-contrib-20160125/)]

[Leandro Facchinetti]

Hi, Org Mode contributors.

First, thanks for Org Mode. It changed my life!

I installed `org-plus-contrib' from `http://orgmode.org/elpa/' this
morning and got version `org-plus-contrib-20160125'.

Trying to export a file with a `#+TITLE:' set leads to the error:

apply: Wrong type argument: listp, #("Writings" 0 8 (:parent (#0)))

Sample file:

#+TITLE: Writings

The error happens regardless of the export backend.

I already ran `emacs -q' and the problem persists.

I appreciate any help debugging.

Emacs  : GNU Emacs 24.5.1 (x86_64-apple-darwin14.3.0, NS apple-appkit-1347.57)
 of 2015-05-29 on Leandros-MacBook-Air.local
Package: Org-mode version 8.3.3 (8.3.3-26-ge92a06-elpaplus @ 
/Users/leafac/.emacs.d/elpa/org-plus-contrib-20160125/)
-- 
Leandro Facchinetti 
https://www.leafac.com
GPG key: 3DF3D583

Re: [O] Conditionally formatting org-html-postamble-format

[Kaushal Modi]

Hi Robert,

Thanks for the reply.

> how about using a postamble function instead of html-postamble-format

Does it mean that I need to look into modifying the
org-html--build-pre/postamble function?

If so, I will start looking into it but it will take a while as it full of
elisp that I have never used (until today maybe): format-spec, plist-get
and a lot of assoc's and assq's :)

Kaushal

[O] [PATCH] ox-koma-letter.el: Add support for 'location' koma variable

[Myles English]

Hello,

Often when writing a letter I want to include "Your Ref: xyz" or
"Account No.: 1234" and a good place to do this is below the sender's
address field and above the date (and 'place') field(s).  This space
becomes filled with the contents of the koma variable called 'location'.
This patch enables filling this variable via org-mode's contrib
ox-koma-letter exporter.

Please apply the attached patch.

Myles

>From 4495abd39d57abc0dd64361f852c3a638f86915b Mon Sep 17 00:00:00 2001
From: Myles English 
Date: Wed, 27 Jan 2016 18:18:38 +
Subject: [PATCH] ox-koma-letter: Add support for LOCATION koma variable

* contrib/lisp/ox-koma-letter.el (koma-letter): Duplicated code
  used for 'place' variable, renamed as 'location'

Whenever OPTION keyword contains a 'location' item or LOCATION
keyword is used in the buffer, set KOMA option 'location' after
LCO inclusion.
---
 contrib/lisp/ox-koma-letter.el | 29 -
 1 file changed, 28 insertions(+), 1 deletion(-)

diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index 9a4686e..8afeed2 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -41,6 +41,7 @@
 ;;   - PHONE_NUMBER: see `org-koma-letter-phone-number',
 ;;   - SIGNATURE: see `org-koma-letter-signature',
 ;;   - PLACE: see `org-koma-letter-place',
+;;   - LOCATION: see `org-koma-letter-location',
 ;;   - TO_ADDRESS:  If unspecified this is set to "\mbox{}".
 ;;
 ;; TO_ADDRESS and FROM_ADDRESS can also be specified using heading
@@ -58,6 +59,7 @@
 ;;   - phone (see `org-koma-letter-use-phone')
 ;;   - email (see `org-koma-letter-use-email')
 ;;   - place (see `org-koma-letter-use-place')
+;;   - location (see `org-koma-letter-use-location')
 ;;   - subject, a list of format options
 ;; (see `org-koma-letter-subject-format')
 ;;   - after-closing-order, a list of the ordering of headings with
@@ -188,6 +190,12 @@ This option can also be set with the PLACE keyword."
   :group 'org-export-koma-letter
   :type 'string)
 
+(defcustom org-koma-letter-location ""
+  "Sender's extension field, as a string.
+This option can also be set with the LOCATION keyword."
+  :group 'org-export-koma-letter
+  :type 'string)
+
 (defcustom org-koma-letter-opening ""
   "Letter's opening, as a string.
 
@@ -356,6 +364,13 @@ This option can also be set with the OPTIONS keyword, e.g.:
   :group 'org-export-koma-letter
   :type 'boolean)
 
+(defcustom org-koma-letter-use-location t
+  "Non-nil prints the contents of the letter's extension below the header.
+This option can also be set with the OPTIONS keyword, e.g.:
+\"location:nil\"."
+  :group 'org-export-koma-letter
+  :type 'boolean)
+
 (defcustom org-koma-letter-default-class "default-koma-letter"
   "Default class for `org-koma-letter'.
 The value must be a member of `org-latex-classes'."
@@ -406,6 +421,7 @@ e.g. \"title-subject:t\"."
 (:email "EMAIL" nil (org-koma-letter--get-value org-koma-letter-email) t)
 (:to-address "TO_ADDRESS" nil nil newline)
 (:place "PLACE" nil org-koma-letter-place)
+(:location "LOCATION" nil org-koma-letter-location)
 (:subject "SUBJECT" nil nil parse)
 (:opening "OPENING" nil org-koma-letter-opening parse)
 (:closing "CLOSING" nil org-koma-letter-closing parse)
@@ -425,6 +441,7 @@ e.g. \"title-subject:t\"."
 (:with-foldmarks nil "foldmarks" org-koma-letter-use-foldmarks)
 (:with-phone nil "phone" org-koma-letter-use-phone)
 (:with-place nil "place" org-koma-letter-use-place)
+(:with-location nil "location" org-koma-letter-use-location)
 (:with-subject nil "subject" org-koma-letter-subject-format)
 (:with-title-as-subject nil "title-subject" org-koma-letter-prefer-subject)
 (:with-headline-opening nil nil org-koma-letter-headline-is-opening-maybe)
@@ -435,12 +452,14 @@ e.g. \"title-subject:t\"."
 (:inbuffer-email "EMAIL" nil 'koma-letter:empty)
 (:inbuffer-phone-number "PHONE_NUMBER" nil 'koma-letter:empty)
 (:inbuffer-place "PLACE" nil 'koma-letter:empty)
+(:inbuffer-location "LOCATION" nil 'koma-letter:empty)
 (:inbuffer-signature "SIGNATURE" nil 'koma-letter:empty)
 (:inbuffer-with-backaddress nil "backaddress" 'koma-letter:empty)
 (:inbuffer-with-email nil "email" 'koma-letter:empty)
 (:inbuffer-with-foldmarks nil "foldmarks" 'koma-letter:empty)
 (:inbuffer-with-phone nil "phone" 'koma-letter:empty)
-(:inbuffer-with-place nil "place" 'koma-letter:empty))
+(:inbuffer-with-place nil "place" 'koma-letter:empty)
+(:inbuffer-with-location nil "location" 'koma-letter:empty))
   :translate-alist '((export-block . org-koma-letter-export-block)
 		 (export-snippet . org-koma-letter-export-snippet)
 		 (headline . org-koma-letter-headline)
@@ -755,6 +774,14 @@ a communication channel."
 	(format "\\setkomavar{place}{%s}\n"
 		(if (plist-get info :with-place) (plist-get info :place)
 		  ""
+ ;; Location.
+ (let ((with-location-set (

Re: [O] Conditionally formatting org-html-postamble-format

[Robert H. Klein]

Hi,

Kaushal Modi  wrote:

> Hi,
> 
> I have the org-html-postamble-format set to the below:
> 
> (setq org-html-postamble-format
>   `(("en"
>  ,(concat "Exported using "
>   ;; "%c" is replaced with
> `org-html-creator-string'
>   ;; Emacs  (Org mode )
>   " class=\"creator\">"  
>   "%c "
>   "by %a. — "
>   " class=\"date\">"  
>   "%d"
> 
> 
> It works great except for the cases where I have set a document
> author to nothing using
> 
> #+AUTHOR:
> 
> What would be the best way to set the postamble so that the "by %a"
> portion does not get printed if the %a value is "".
> 
> Right now, if the author is nil, the postamble gets exported as:
> 
> Exported using
> Emacs  25.0.50.1 (Org
>  mode 8.3.3)
>  by . —
> Jan 26 2016, Tue


how about using a postamble function instead of
html-postamble-format, something like

(let ((author (car (plist-get info :author
  (when (not (equal author ""))
"by " author ". "))
" - "

instead of "by %a. - "

and similar for the rest of the %-thingies.

Note, you'll probably have to inspect the plist, the (car ...) I'm
using in some project for getting the title.

Best regards
Robert

[O] Columnview *** is exported as *

[Axel Kielhorn]

Hi,

I use org to track time and money spend on a project.
This project has several sub levels that are assigned to certain workers.

To view and edit the time and money spend, I use columnview which works fine.
When I want to report about our effort I want to export a columnview table.
In this table the tasks are shown with *, **, and *** to indicate the level.
In the export the *** is rendered as a bold *.

Right now I insert a space between the ** but that is not really efficient.

Is there a way to render the different level via different indenting as it is 
done for clocktables? 
I looked at the code for clocktable but that is above my understanding of elisp.

I’m using org-mode 8.3.3-17 from ELPA with emacs 24.5.

Axel


Title: ECM






ECM


1 Top Level





















Baugruppe
Zeit
Plan
Kosten
Fällig
Fertig
Verant.




* Top Level
24
44.0
1050
 
[2/4]
 



** Sub level 1
12
2d
500
2016-03-12
[ ]
:MA1:



** Sub level 2
12
28
550
2016-03-12
[2/3]
 



* Sub sub level 2a
4
8
100
2016-03-12
[X]
:MA2:



* Sub sub level 2b
4
8
400
2016-03-12
[X]
:MA2:



* Sub sub level 2c
4
12
50
2016-03-12
[ ]
:MA1:







1.1 Sub level 1





1.2 Sub level 2




1.2.1 Sub sub level 2a





1.2.2 Sub sub level 2b





1.2.3 Sub sub level 2c







Autor: Axel Kielhorn
Created: 2016-01-27 Wed 18:53
Validate




ECM-Columnview.org
Description: Binary data

Re: [O] syncing my life (orgmode :)) to a mobile (android) device

[Karl Voit]

* Matt Lundin  wrote:
> 
> If you use google calendar you could accomplish something similar with
> the following workflow:
>
> a) Export your org data to an ics file and put it in dropbox. In
> dropbox, grab a secret link to share that file.
>
> b) Point google calendar to the secret link. This will create a
> read-only calendar in google calendar.

I was using this method since 2013. Unfortunately, Google stopped
fetching my iCal file without any reason I could find. So I stopped
using Cloud-based services.

> c) Script a tool like gcalcli[fn:2] to pull and delete new items from a
> writable google calendar. Convert the data to org markup and add them to
> an org file. (This is the part that will involve just a bit of basic
> shell scripting.)

For now, I only use MobileOrg for capturing stuff on Android and for
displaying my agenda which was generated on the big machine.

> For fun (but not much profit) you can set up a chroot linux environment
> on a rooted android device and install all your favorite software
> (emacs, org, etc.). See https://github.com/guardianproject/lildebi for
> instance.
>
> By far the easiest way to access org mode is to set up some sort of ssh
> access to a computer running emacs. There are several good ssh clients
> for android. The hacker's keyboard app offers all the familiar modifier
> keys (Ctrl, Alt, etc.)

I tried this approach as well.

Unfortunately, the bluetooth HW keyboards I was testing did not
provide a method to send Ctrl/Alt/Esc -> no way. With software
keyboards (hacker's keyboard) I don't want to use Emacs since the
commands are "in my fingers" and with SW keyboards, I have to start
remembering the commands to use them slowly.

I was reading about the ARM-based mini-computers here. But since my
Org is rather slow on my intel i5/16GB RAM, I can't imagine working
on such a low performance hardware (again).

So far, Org-mode to go is a very unfortunate adventure.

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] Radio target appears as a link in html export (in Emacs stable)

[Nicolas Goaziou]

Hello,

die...@duenenhof-wilhelm.de (H. Dieter Wilhelm) writes:

> But then I would have to turn all my radio links into proper links,
> which I see no method - except with radio targets - to do this
> automatically.

Instead of 

  <<>> ... radio

you would have to type

  <>   ... [[radio]]

which, IMO, is almost equally simple.

> The radio links are turned correctly into links. :-)
>
> But the targets (anchors) appear *also* as links (in HTML).  Which is
> confusing and redundant because there are not linked to anything.

I'm confused, mainly because I'm not well versed in HTML. Let's consider
the following document:

  <<>> :target link: radio

When exporting it to HTML, I get the following:

  radio :target link: radio

What would you expect instead?


Regards,

-- 
Nicolas Goaziou

Re: [O] Repeated tasks marked as DONE

[Myles English]

Myles English writes:

> Hello Tomasz,
>
> Tomasz Piotrowski writes:
>
>> I have a simple question, yet couldn't find an equally simple answer to
>> it. Namely, if I set a repeated task (everyday, say), the agenda
>> shows this tasks _for all days_, even in the past.
>>
>> How can I mark a repeated task DONE if it is completed for a given day,
>> while keeping it as TODO for the future?
>
> This is what works for me, the last_repeat property seams to enable the
> behaviour you describe, the logbook is something extra I vaguely
> remember setting up:
>
> * TODO Put recycle bin out
>  SCHEDULED: <2016-01-28 Thu +2w>
> :PROPERTIES:
> :LAST_REPEAT: [2016-01-16 Sat 13:10]
> :END:
> :LOGBOOK:
> - State "DONE"   from "TODO"   [2016-01-16 Sat 13:10]
> - State "DONE"   from "TODO"   [2016-01-02 Sat 17:41]
> - State "DONE"   from "TODO"   [2015-12-21 Mon 16:22]
> :END:

And see also the variable org-agenda-repeating-timestamp-show-all.
(Having read the available help, don't quite understand way it working
for me...)

Myles

Re: [O] Repeated tasks marked as DONE

[Myles English]

Hello Tomasz,

Tomasz Piotrowski writes:

> I have a simple question, yet couldn't find an equally simple answer to
> it. Namely, if I set a repeated task (everyday, say), the agenda
> shows this tasks _for all days_, even in the past.
>
> How can I mark a repeated task DONE if it is completed for a given day,
> while keeping it as TODO for the future?

This is what works for me, the last_repeat property seams to enable the
behaviour you describe, the logbook is something extra I vaguely
remember setting up:

* TODO Put recycle bin out
 SCHEDULED: <2016-01-28 Thu +2w>
:PROPERTIES:
:LAST_REPEAT: [2016-01-16 Sat 13:10]
:END:
:LOGBOOK:
- State "DONE"   from "TODO"   [2016-01-16 Sat 13:10]
- State "DONE"   from "TODO"   [2016-01-02 Sat 17:41]
- State "DONE"   from "TODO"   [2015-12-21 Mon 16:22]
:END:

Myles

[O] Repeated tasks marked as DONE

[Tomasz Piotrowski]

Hi,

I have a simple question, yet couldn't find an equally simple answer to
it. Namely, if I set a repeated task (everyday, say), the agenda
shows this tasks _for all days_, even in the past.

How can I mark a repeated task DONE if it is completed for a given day,
while keeping it as TODO for the future?

Kind regards,

Tomasz Piotrowski

-- 
Sent with my mu4e

Re: [O] [Beamer] headings missing with two columns

[Eric S Fraga]

On Wednesday, 27 Jan 2016 at 09:44, Loris Bennett wrote:

[...]

> Thanks, this works (I'm using 8.3.3).  Now I am wondering whether it is
> possible to have two headings in the same columns of the same order?  I
> thought that I would need a dummy heading between "Food" and "Fruit",
> but the following does not work (everything ends up in a single
> column).  Even if it had worked, presumably it would have changed the
> formatting, since ' Fruit' is now '* Fruit', or should
> 'ignoreheading' handle that?

I am not entirely sure what you are trying to achieve.  However, I can
say that ignoreheading and block are mutually exclusive environment
settings so you cannot have both.  A block needs a heading but if you
ignore it, you cannot have a block.

The following works, assuming I have understood what you wanted:

#+begin_src org
  ,#+TITLE: test
  ,#+OPTIONS: H:3

  ,#+STARTUP: beamer

  ,* blah
  ,** test
  ,*** Food
  , dummy 1  :BMCOL:
  :PROPERTIES:
  :BEAMER_col: 0.5
  :END:
  ,* Fruit
   - apple
   - banana
  ,* Nuts
- brasil
- cashew
  , dummy 2  :BMCOL:
  :PROPERTIES:
  :BEAMER_col: 0.5
  :END:
  ,* Vegetables
   - artichoke
   - broccoli
  ,* Pulses
   - chickpea
   - lentil
#+end_src

If you want a block with an empty heading, use a non-printing space of
some sort for the heading, maybe @@latex:~@@?

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.3-456-g164555

Re: [O] Again - Unable to filter agenda to show only non-tagged items

[sgeorgii .]

Thank you Nicolas!

On 26 January 2016 at 23:59, Nicolas Goaziou  wrote:

> Hello,
>
> "sgeorgii ."  writes:
>
> > Today I completely uninstalled org-mode from emacs, restalled fresh and
> > installed the latest org version 20160125.
> >
> > I see the bug right now on my screen.
> >
> > M-x
> >
> > org-agenda 
> >
> > M
> >
> > Match: 
> >
> > Result:   *Messages* = org-agenda-finalize: Wrong type argument: listp,
> > default
> >
> > What else can I say?
> >
> > Anyone else having this bug with org version 20160125?
>
> This bug was fixed yesterday.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] table, columns and plot

[Eric S Fraga]

On Wednesday, 27 Jan 2016 at 07:58, f...@epita.fr wrote:
> Eric S Fraga  writes:

[...]

>>>   #+name: tab1
>>>   #+begin: columnview :hlines 1 :id "prj_encours"
>>
>> What is this line meant to do?  Without it, the gnuplot src block works
>> just fine.
>
>#+begin: columnview :hlines 1 :id "prj_encours"
>
> without this line "#+begin: columnview :hlines 1 :id "prj_encours", I
> can't extract properties to make my table, isn't it ?

Apologies for the previous reply which got sent before I had a chance to
type anything -- hit wrong key! 

Anyway, I cannot help with this particular aspect as I have never tried
to extract properties from a table.  I do not even know what that
means.  :-)

Hope somebody else can help you.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.3-456-g164555

Re: [O] table, columns and plot

[Eric S Fraga]

On Wednesday, 27 Jan 2016 at 07:58, f...@epita.fr wrote:
> Eric S Fraga  writes:
>
>> On Tuesday, 26 Jan 2016 at 11:20, f...@epita.fr wrote:
>>> Hi !
>>> I want to plot the extract of columns :
>>> But, the gnuplot block do not found the tab1.
>>> Is it possible to name the columnview table ?
>>>
>>> Org-mode version 8.3.3 (8.3.3-17-gce80a0-elpa @
>>> /home/flav/.emacs.d/elpa/org-20160118/) 
>>>
>>> Thks
>>>
>>> * Synthèse
>>>
>>>   #+name: tab1
>>>   #+begin: columnview :hlines 1 :id "prj_encours"
>>
>> What is this line meant to do?  Without it, the gnuplot src block works
>> just fine.
>
>#+begin: columnview :hlines 1 :id "prj_encours"
>
> without this line "#+begin: columnview :hlines 1 :id "prj_encours", I
> can't extract properties to make my table, isn't it ?

Re: [O] [Beamer] headings missing with two columns

[Loris Bennett]

Hi Eric,

Eric S Fraga  writes:

> On Tuesday, 26 Jan 2016 at 16:11, Loris Bennett wrote:
>> Hi,
>>
>> With the following:
>
> [...]
>
>> I expected to see headings "Fruit" and "Vegetables" over the two
>> columns, but they do not appear.  I thought I had to use
>>
>> :BEAMER_env: ignoreheading
>>
>> explicitly to suppress the headings and that the default was to show
>> them. 
>>
>> What am I doing wrong?
>
> You haven't said what version of org you are using.  The above would
> probably work with versions of org 7.x but for 8.x, you need a different
> set of commands to achieve what you want.  The following should do what
> you want:
>
> #+begin_src org
>   ,#+TITLE: test
>   ,#+OPTIONS: H:3
>
>   ,#+startup: beamer
>   ,* blah
>   ,** test
>   ,*** Food
>   , Fruit:B_block:BMCOL:
>:PROPERTIES:
>:BEAMER_col: 0.5
>:BEAMER_env: block
>:END:
>- apple
>- banana
>   , Vegetables   :B_block:BMCOL:
>:PROPERTIES:
>:BEAMER_col: 0.5
>:BEAMER_env: block
>:END:
>- artichoke
>- broccoli
>
> #+end_src
>
> Note the removal of the LaTeX class declaration.  In v8, blocks have
> headings ignored by default if they are columns so you need to specify a
> block type explicitly.  Using the beamer startup directive allows you to
> easily specify what you want on a headline by C-c C-b.
>
> HTH,
> eric

Thanks, this works (I'm using 8.3.3).  Now I am wondering whether it is
possible to have two headings in the same columns of the same order?  I
thought that I would need a dummy heading between "Food" and "Fruit",
but the following does not work (everything ends up in a single
column).  Even if it had worked, presumably it would have changed the
formatting, since ' Fruit' is now '* Fruit', or should
'ignoreheading' handle that?

This is what I tried but only got a single column:

#+TITLE: test
#+OPTIONS: H:3
#+STARTUP: beamer

* blah
** test
*** Food
 dummy 1  :B_block:BMCOL:
:PROPERTIES:
:BEAMER_col: 0.5
:BEAMER_env: block
:BEAMER_env: ignoreheading
:END:
* Fruit
 - apple
 - banana
* Nuts
  - brasil
  - cashew
 dummy 2  :B_block:BMCOL:
:PROPERTIES:
:BEAMER_col: 0.5
:BEAMER_env: block
:BEAMER_env: ignoreheading
:END:
* Vegetables
 - artichoke
 - broccoli
* Pulses
 - chickpea
 - lentil

Cheers,

Loris

-- 
This signature is currently under construction.

Re: [O] Radio target appears as a link in html export (in Emacs stable)

[H. Dieter Wilhelm]

Nicolas Goaziou  writes:
> die...@duenenhof-wilhelm.de (H. Dieter Wilhelm) writes:
>
>> when exporting radio targets to PDF they appear as normal text.
>> Sometimes I wish I could make them invisible but this is a behaviour I
>> can live with.
>
> You should use regular targets, then.

But then I would have to turn all my radio links into proper links,
which I see no method - except with radio targets - to do this
automatically.

>> Anyway, when exporting to html the radio targets appear like a regular
>> link (technically I think they are a named anchor, something like > id="bla" name="bla">bla).  The apperance is not helpful, only
>> confusing.  I guess I could change this behaviour with some css trickery
>> but it might become complicated, at least for my little html knowledge.
>
> There are radio targets (e.g., <<>>) and radio links and (e.g.,
> radio). The former are turned into anchors and the latter into links.
> Don't you get the same?

The radio links are turned correctly into links. :-)

But the targets (anchors) appear *also* as links (in HTML).  Which is
confusing and redundant because there are not linked to anything.

Here's an example:
http://duenenhof-wilhelm.de/dancing/date.html

E. g. _EDanceFever_ are links to their anchor below.

Maybe the following would be a good idea for org in general: A radio
target with an optional address argument like babel src blocks
<<>>[http://targetaddresse.com] and upgrading the anchor to a
real, working link.

Thank you Nicolas

-- 
Best wishes
H. Dieter Wilhelm
Darmstadt, Germany