[O] titles on tables

[Jude DaShiell]

Is it possible to do something like:
| Data Dictionary |
| variable | type| description|
|-

As a table header or maybe even somehow have data dictionary centered?
I made a table earlier without the title line and tried doing a retrofit 
that didn't work.  If this isn't possible and the table won't be exported 
to html or other formats does another way exist to do this?




--

Re: [O] org-babel-capitalize-example-region-markers

[Kyle Meyer]

Kyle Meyer  writes:

[...]

> Here's a patch.  I'll apply it to master in a day or two if there are no
> objections.

Applied with 9c111f63 (with :version changed from 25.2 to 26.1).

-- 
Kyle

Re: [O] How to specify APPT_WARNTIME for entire files?

[Nicolas Goaziou]

Hello,

Jorge Morais Neto  writes:

> Hi.  I have set appt-message-warning-time to 10.  However, there are two
> files where I would like the warning time to be 0.  Is there a quick way to
> do it?  Which?  I do not want to add APPT_WARNTIME properties to each entry
> because, if I did that, then:
> 1. Every time I added a new entry to one of the affected files, I would need
>to remember setting APPT_WARNTIME to the correct value.
> 2. To later change the warning time for the affected files, I would need to
>change APPT_WARNTIME in each of their entries.
> 3. There are many such entries, so it would be space-inefficient to have
>APPT_WARNTIME in each.
>
> I have tried to specify "#+PROPERTY: APPT_WARNTIME 5" and enable inheritance
> of it through org-use-property-inheritance, but it did not work.  I have
> also searched the web and the Org mailing list archives.

This is now fixed.  You can use "#+PROPERTY: APPT_WARNTIME 5", as long
as APPT_WARNTIME can be inherited.

Thank you for the report.

Regards,

-- 
Nicolas Goaziou

Re: [O] Org-mode: Tagging the CLOCK line

[Eric S Fraga]

On Thursday, 26 Jan 2017 at 14:02, Shawn Way wrote:
> Is there a modification that can be made to add a tag, such as
> someone’s initials, to the CLOCK line?  I would like to use this to
> separate out time spent by multiple individuals in a clocking table.

Not what you want as such but what I have done in the past is create
subheadings which I clock into/out of specifically.  
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.3-241-gc3d67b


signature.asc
Description: PGP signature

Re: [O] Sync up the org in emacs master to org maint branch?

[Eli Zaretskii]

> From: Kaushal Modi 
> Date: Thu, 26 Jan 2017 16:01:24 +
> Cc: emacs-org list ,
>   Stefan Monnier ,
>   Rasmus , Emacs developers 
> 
> I don't believe that the target date has yet been set for releasing 26.1. We 
> are currently on the release
> candidate testing stage of 25.2. So I will not be surprised if 26.1 get 
> released even 3 months or 6 months from
> now. Eli? John?

AFAIR, we have never released a major version so quickly, and I don't
see why this one would be different.  A year at least, I'd say,
probably more.

[O] Simultaneously showing multiple todo keyword sequences

[Zans M]

Lets say I have two sequences of TODO keywords:

"TODO" "|" "DONE"

"WORKING" "|" "BROKEN"


At the moment I can show only one of the states at a time, but what if
my task can be in two states at once (one from each sequence), ie


* [TODO] [BROKEN] Build interface for webapp


Would anyone know how to do this, and how to setup key commands so
that I could cycle through each sequence independently?

Re: [O] Sync up the org in emacs master to org maint branch?

[Kaushal Modi]

On Thu, Jan 26, 2017 at 10:39 AM Kyle Meyer  wrote:

> Kaushal Modi  writes:
>
> > On Thu, Jan 26, 2017 at 1:19 AM Kyle Meyer  wrote:
> >
> >> We'd want at least one more release from maint, I think, so that'd be
> >> 9.0.5.
> >
> > Would it be OK to sync the current stable 9.0.4,
>
> I don't think that's a good idea.  Since 9.0.4, I've backported one
> remaining commit from Emacs, I've adjusted :version in defcustoms to the
> appropriate version for a sync targeting Emacs's master, and I've
> cleaned up the spacing in a few places so that all the files pass
> Emacs's pre-commit check.
>

Makes sense. Thanks for the explanation.


> > We never know, we might end up with even higher stable releases by the
> > time emacs 26.1 is released.
>
> I suspect we will, given that 9.0.1 -> 9.0.4 have all been released
> since this November.
>

I don't believe that the target date has yet been set for releasing 26.1.
We are currently on the release candidate testing stage of 25.2. So I will
not be surprised if 26.1 get released even 3 months or 6 months from now.
Eli? John?
-- 

Kaushal Modi

Re: [O] Sync up the org in emacs master to org maint branch?

[Kyle Meyer]

Kaushal Modi  writes:

> On Thu, Jan 26, 2017 at 1:19 AM Kyle Meyer  wrote:
>
>> We'd want at least one more release from maint, I think, so that'd be
>> 9.0.5.
>
> Would it be OK to sync the current stable 9.0.4,

I don't think that's a good idea.  Since 9.0.4, I've backported one
remaining commit from Emacs, I've adjusted :version in defcustoms to the
appropriate version for a sync targeting Emacs's master, and I've
cleaned up the spacing in a few places so that all the files pass
Emacs's pre-commit check.

> and keep on updating with each stable release as time comes?

Yes, that should be done.

> We never know, we might end up with even higher stable releases by the
> time emacs 26.1 is released.

I suspect we will, given that 9.0.1 -> 9.0.4 have all been released
since this November.

-- 
Kyle

Re: [O] Temporary cancelling recurring tasks

[Michael Welle]

Hello,

Mikhail Skorzhinskiy  writes:

> Take a look to 
> http://karl-voit.at/2017/01/15/org-clone-subtree-with-time-shift/
someone (you ;)?) in #emacs suggested that, too. But I don't understand
how that would help. Can you explain, please?

I understand the problem Karl wants to solve, I myself have the same
problem from time to time. But to be honest, I don't think copying the
same task over and over again is a solution to that problem.

Regards
hmw

Re: [O] Temporary cancelling recurring tasks

[Michael Welle]

Hello,

Nick Dokos  writes:

> Michael Welle  writes:
>
>> Hello,
>>
>> I want to temporary cancel recurring tasks. Let's say I have tasks, that
>> only make sense when I'm in my office. Now I'm away for a few months.
>> The tasks would clutter my agenda. I could comment them, archive them or
>> use org-cancel-repeater and set the task's state to DONE. But all that
>> makes it hard to restore the previous state when I'm back in my office.
>>
>> I think, the clean solution is to set the state of the task to CANCELLED
>> or STOPPED or something like that, to deactivate the recurring task.
>> When I activate the task again, the scheduled date and the repeater
>> should be restored. To achieve that, I tried the following:
>>
>
> Can't you just reschedule them for after you get back?
that means that I need to know in advance when I'm back.

Regards
hmw

Re: [O] Temporary cancelling recurring tasks

[Mikhail Skorzhinskiy]

Take a look to http://karl-voit.at/2017/01/15/org-clone-subtree-with-time-shift/

On 2017-01-26T13:39:50+0300, Michael Welle wrote:

> Hello,
> 
> I want to temporary cancel recurring tasks. Let's say I have tasks, that
> only make sense when I'm in my office. Now I'm away for a few months.
> The tasks would clutter my agenda. I could comment them, archive them or
> use org-cancel-repeater and set the task's state to DONE. But all that
> makes it hard to restore the previous state when I'm back in my office.
> 
> I think, the clean solution is to set the state of the task to CANCELLED
> or STOPPED or something like that, to deactivate the recurring task.
> When I activate the task again, the scheduled date and the repeater
> should be restored. To achieve that, I tried the following:
> 
> 
> ;;
> ;; Deactivate/Activate recurring tasks
> ;;
> 
> 
> ;; Prior to Org commit 7d52a8c3cc86c8ce03eda006752af1ab4bed4316
> ;; there seems to be no way to set the repeater of a, let's say,
> ;; SCHEDULED property programmatically. So we use this function.
> (defun hmw/org-schedule-set-value (val)
>   "Sets the value of the SCHEDULED property. This allows for
> setting the repeater as well."
>   (interactive)
>   (save-excursion
> (org-back-to-heading t)
> (let ((bound1 (point))
> (bound0 (save-excursion (outline-next-heading) (point
>   (when (re-search-forward
>(concat "\\(" org-scheduled-time-regexp "\\)")
>bound0 t)
>   (replace-match val t nil nil 2)
> 
> (defvar hmw/org-scheduled-property-backup "DISABLED-SCHEDULED"
>   "Back up the original value of the SCHEDULED property into this
> property when deactivating a recurring task. The value is rescued from
> this property to initialise the SCHEDULED property when activating the
> task again.")
> 
> (defvar hmw/org-activated-recurring-task-state "TODO"
>   "Switch a recurring task to this state after activating.")
> 
> (defvar hmw/org-deactivated-recurring-task-state "CANCELLED"
>   "Switch a recurring task to this state after deactivating.")
> 
> (defun hmw/org-deactivate-recurring-task ()
>   "Deactivate a recurring task. The value of the SCHEDULED property is
> stored in the property referenced by `hmw/org-scheduled-property-backup',
> so it can be restored later. The task's state is set to the value of
> `hmw/org-deactivated-recurring-task-state'." 
>   (interactive)
>   (when (org-entry-is-todo-p)
> (save-excursion
>   (org-back-to-heading t)
>   (let* ((pom (point-at-bol))
>  (val (org-entry-get pom "SCHEDULED")))
> (when val
> ;; Remove the time stamp meaning. We don't want active
> ;; timestamp to trigger any actions for the deactivated
> ;; task.
> (setq val (replace-regexp-in-string "^<\\(.*\\)>$" "\\1" val))
> (org-entry-put pom hmw/org-scheduled-property-backup val)
> (org-entry-put pom "SCHEDULED" nil)
> (org-todo hmw/org-deactivated-recurring-task-state))
> 
> (defun hmw/org-activate-recurring-task ()
>   "Activate a previously deactivated recurring task. The value of the
> SCHEDULED property is retrieved from the property referenced by
> `hmw/org-scheduled-property-backup', which is then deleted. The task's 
> state is set to the value of `hmw/org-activated-recurring-task-state'."
>   (interactive)
>   (when (org-entry-is-done-p)
> (save-excursion
>   (org-back-to-heading t)
>   (let* ((pom (point-at-bol))
>  (val (org-entry-get pom hmw/org-scheduled-property-backup)))
> (when val
> ;; For Org commit 7d52a8c3cc86c8ce03eda006752af1ab4bed4316 or
> ;; later use this
> ;;(setq val (replace-regexp-in-string "^\\(.*\\)$" "<\\1>" val))
> ;;(org-entry-put pom "SCHEDULED" val)
> 
> ;; For older Org use this
> (org-entry-put pom "SCHEDULED" val)
> (hmw/org-schedule-set-value val)
>   
> (org-entry-delete pom hmw/org-scheduled-property-backup)
> (org-todo hmw/org-activated-recurring-task-state))
>  
> 
> The idea is to store the value of the SCHEDULED property somewhere when
> the task gets deactivated. Later, on activation, the property value is
> restored.
> 
> There are two variants. The one above, which should work for Org prior
> to commit 7d52a8c3cc86c8ce03eda006752af1ab4bed4316 and also for later
> revisions. And one for that commit and later. If you use the newer Org
> revision, you optionally can get rid of the function
> hw/org-schedule-set-value and follow the comments in
> hmw/org-activate-recurring-task.
> 
> Regards
> hmw
> 


-- 
Skorzhinskiy Mikhail

Re: [O] How to have a sideways longtable?

[William Denton]

On 20 January 2017, John Hendy wrote:


#+LATEX_HEADER: \usepackage{lscape}

#+latex: \begin{landscape}
#+latex: \tiny
#+attr_latex: :align |ll|lll|lll :env longtable
| table | goes | here |
#+latex: \end{landscape}


I'm several days late, but: thank you!  This works perfectly.

Bill
--
William Denton :: Toronto, Canada :: https://www.miskatonic.org/
Caveat lector.

Re: [O] Sync up the org in emacs master to org maint branch?

[Kaushal Modi]

On Thu, Jan 26, 2017 at 1:19 AM Kyle Meyer  wrote:

> Rasmus  writes:
> We'd want at least one more release from maint, I think, so that'd be
> 9.0.5.
>

Would it be OK to sync the current stable 9.0.4, and keep on updating with
each stable release as time comes? We never know, we might end up with even
higher stable releases by the time emacs 26.1 is released.

I have been using emacs master and org master for ages now without any
issues. So emacs master + org 9.0.4 should not cause any serious problems.
The major issues I forsee are the few backward incompatible changes people
might have to make when org changes from 8.2.x to 9.x (though all those
changes are documented in ORG-NEWS).


On Thu, Jan 26, 2017 at 8:46 AM Rasmus  wrote:

> So would now be a good time to sync the Emacs master?  I guess the
> appropriate way would be to make a new branch that can eventually be
> merged.
>

Going by the same argument as above, do you think that merging org maint
into emacs master directly is that risky? org master + emacs master has
been super-stable for me.


On Thu, Jan 26, 2017 at 9:22 AM Stefan Monnier 
wrote:

> > So would now be a good time to sync the Emacs master?
>
> On `master`, "now" is pretty much *always* a good time to sync.
> More specifically, it's better to always keep `master` in sync with the
> upstream (applies not just to Org).
>
> "sync early, sync often",
>

+1!


-- 

Kaushal Modi

Re: [O] Temporary cancelling recurring tasks

[Nick Dokos]

Michael Welle  writes:

> Hello,
>
> I want to temporary cancel recurring tasks. Let's say I have tasks, that
> only make sense when I'm in my office. Now I'm away for a few months.
> The tasks would clutter my agenda. I could comment them, archive them or
> use org-cancel-repeater and set the task's state to DONE. But all that
> makes it hard to restore the previous state when I'm back in my office.
>
> I think, the clean solution is to set the state of the task to CANCELLED
> or STOPPED or something like that, to deactivate the recurring task.
> When I activate the task again, the scheduled date and the repeater
> should be restored. To achieve that, I tried the following:
>

Can't you just reschedule them for after you get back?

-- 
Nick

Re: [O] Dates in Tables Should be Inactive

[Daniel E. Doherty]

Nicolas Goaziou  writes:

>
> Agreed. In master, I pushed a change that transforms all computed dates
> as inactive time stamps.

Nicolas, just say this, and thanks for the quick action.

Regards,

--

Daniel E. Doherty
Law Offices of Daniel E. Doherty
7300 W. 110th Street, Suite 930
Overland Park, KS 66210
913.338.7182 (Phone)
913.338.7164 (FAX)
ded-...@ddoherty.net

[O] Org-mode: Tagging the CLOCK line

[Shawn Way]

Is there a modification that can be made to add a tag, such as someone's 
initials, to the CLOCK line?  I would like to use this to separate out time 
spent by multiple individuals in a clocking table.

Project Engineer
Shawn Way, P.E.


281.276.76212 | s...@meco.com
12603 SOUTHWEST FREEWAY, SUITE 500, STAFFORD, TX 77477

800.450.6326 | MECO.COM
Ireland | Singapore | UAE | USA

[Where Tomorrow Gets Its Water (tm)  |  MECO]

[http://cdn2.hubspot.net/hubfs/2145052/images/facebook.png]
 [http://cdn2.hubspot.net/hubfs/2145052/images/twitter.png] 
  
[http://cdn2.hubspot.net/hubfs/2145052/images/youtube.png] 
  
[http://cdn2.hubspot.net/hubfs/2145052/images/linkedin-24.png] 

[O] Temporary cancelling recurring tasks

[Michael Welle]

Hello,

I want to temporary cancel recurring tasks. Let's say I have tasks, that
only make sense when I'm in my office. Now I'm away for a few months.
The tasks would clutter my agenda. I could comment them, archive them or
use org-cancel-repeater and set the task's state to DONE. But all that
makes it hard to restore the previous state when I'm back in my office.

I think, the clean solution is to set the state of the task to CANCELLED
or STOPPED or something like that, to deactivate the recurring task.
When I activate the task again, the scheduled date and the repeater
should be restored. To achieve that, I tried the following:


;;
;; Deactivate/Activate recurring tasks
;;


;; Prior to Org commit 7d52a8c3cc86c8ce03eda006752af1ab4bed4316
;; there seems to be no way to set the repeater of a, let's say,
;; SCHEDULED property programmatically. So we use this function.
(defun hmw/org-schedule-set-value (val)
  "Sets the value of the SCHEDULED property. This allows for
setting the repeater as well."
  (interactive)
  (save-excursion
(org-back-to-heading t)
(let ((bound1 (point))
  (bound0 (save-excursion (outline-next-heading) (point
  (when (re-search-forward
 (concat "\\(" org-scheduled-time-regexp "\\)")
 bound0 t)
(replace-match val t nil nil 2)

(defvar hmw/org-scheduled-property-backup "DISABLED-SCHEDULED"
  "Back up the original value of the SCHEDULED property into this
property when deactivating a recurring task. The value is rescued from
this property to initialise the SCHEDULED property when activating the
task again.")

(defvar hmw/org-activated-recurring-task-state "TODO"
  "Switch a recurring task to this state after activating.")

(defvar hmw/org-deactivated-recurring-task-state "CANCELLED"
  "Switch a recurring task to this state after deactivating.")

(defun hmw/org-deactivate-recurring-task ()
  "Deactivate a recurring task. The value of the SCHEDULED property is
stored in the property referenced by `hmw/org-scheduled-property-backup',
so it can be restored later. The task's state is set to the value of
`hmw/org-deactivated-recurring-task-state'." 
  (interactive)
  (when (org-entry-is-todo-p)
(save-excursion
  (org-back-to-heading t)
  (let* ((pom (point-at-bol))
 (val (org-entry-get pom "SCHEDULED")))
(when val
  ;; Remove the time stamp meaning. We don't want active
  ;; timestamp to trigger any actions for the deactivated
  ;; task.
  (setq val (replace-regexp-in-string "^<\\(.*\\)>$" "\\1" val))
  (org-entry-put pom hmw/org-scheduled-property-backup val)
  (org-entry-put pom "SCHEDULED" nil)
  (org-todo hmw/org-deactivated-recurring-task-state))

(defun hmw/org-activate-recurring-task ()
  "Activate a previously deactivated recurring task. The value of the
SCHEDULED property is retrieved from the property referenced by
`hmw/org-scheduled-property-backup', which is then deleted. The task's 
state is set to the value of `hmw/org-activated-recurring-task-state'."
  (interactive)
  (when (org-entry-is-done-p)
(save-excursion
  (org-back-to-heading t)
  (let* ((pom (point-at-bol))
 (val (org-entry-get pom hmw/org-scheduled-property-backup)))
(when val
  ;; For Org commit 7d52a8c3cc86c8ce03eda006752af1ab4bed4316 or
  ;; later use this
  ;;(setq val (replace-regexp-in-string "^\\(.*\\)$" "<\\1>" val))
  ;;(org-entry-put pom "SCHEDULED" val)
  
  ;; For older Org use this
  (org-entry-put pom "SCHEDULED" val)
  (hmw/org-schedule-set-value val)
  
  (org-entry-delete pom hmw/org-scheduled-property-backup)
  (org-todo hmw/org-activated-recurring-task-state))
 

The idea is to store the value of the SCHEDULED property somewhere when
the task gets deactivated. Later, on activation, the property value is
restored.

There are two variants. The one above, which should work for Org prior
to commit 7d52a8c3cc86c8ce03eda006752af1ab4bed4316 and also for later
revisions. And one for that commit and later. If you use the newer Org
revision, you optionally can get rid of the function
hw/org-schedule-set-value and follow the comments in
hmw/org-activate-recurring-task.

Regards
hmw

Re: [O] How to set the scheduled property programmatically?

[Michael Welle]

Hello,

Nicolas Goaziou  writes:

> Hello,
>
> Michael Welle  writes:
>
>> what is the correct way to set the property? I tried
>>
>> (org-entry-put pom "SCHEDULED" "<2017-01-01 Sun ++1w>")
>>
>> which results in
>>
>> SCHEDULED: <2017-01-01 Sun>
>>
>> As you can see, the 'repeater' is missing.
>
> Fixed. Thank you.
thank you, that's much appreciated.

Regards
hmw

Re: [O] What would you like to see in the next MobileOrg iOS?

[Rainer M Krug]

Sean Escriva  writes:

> Hi fellow Org users,
>
> I'm the current maintainer of MobileOrg for iOS[1]. We've recently been 
> working on a refreshed release of the current version of MobileOrg and it 
> will be released soon as v1.7. After
> this release v1 will be in maintenance mode while we focus efforts on the 
> next version.
>
> We've started plans on the future version of MobileOrg, dubbed just v2 
> currently. It will be a major rewrite and we need your input. We hope to not 
> just improve the codebase but also
> add more features that would be useful specifically to mobile users and 
> provide a great Org mode experience on an iOS device.
>
> We've started a specification document[2] which is slowly evolving and we'd 
> like to track issues for discussion[3] with the community of users before 
> making decisions.
>
> If you have any additional requirements feel free to add them as an issue or 
> by pull request[4]. Your input is much appreciated!

Thanks - this looks like I might use MobileOrg again when version 2 is
out! Great.

One more idea (of which I don't know if it is possible) - sync of org /
emacs calender tasks to the iOS calender. This would be brilliant.

I filed an Issue https://github.com/MobileOrg/mobileorg.next/issues/2
but I think you have to set the tag?

Looking forward to version 2,

Cheers,

Rainer

>
> Sean 
>
> [1] https://github.com/MobileOrg/mobileorg
> [2] 
> https://github.com/MobileOrg/mobileorg.next/blob/specification/docs/MobileOrgv2.org
>  
> [3] https://github.com/MobileOrg/mobileorg.next/labels/discussion 
> [4] https://github.com/MobileOrg/mobileorg.next/issues 
>

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] Sync up the org in emacs master to org maint branch?

[Michael Albinus]

Rasmus  writes:

> Hi,

Hi,

> *AFAIR* it was too late and would thus not have received enough test from
> the general Emacs community.

org-mode comes with some hundred ert test cases. It would be great if
they'll land also in the Emacs master branch; this will give much more
testing.

> Thanks,
> Rasmus

Best regards, Michael.