Hello,
First of all, THANKS for org-mode! I have been using it for several
years, and it's fantastic.
I recently have upgraded to org 20200525 from your package repo because
org-roam requires a newer org-mode than I had. GNU ELPA has 9.3.6,
which would be new enough, but all of my machines f
Eric S Fraga writes:
> On Thursday, 12 Oct 2017 at 16:28, John Goerzen wrote:
>> Dropbox is really not a great option here.) Sync integrity -- or at
>> least robust detection of conflicts -- is a must. Encryption is a "very
>> nice to have."
>>
>>
Neil Jerram writes:
> Hi John,
>
> There is a great discussion about adding git synchronization to Orgzly, in
> progress here:
> https://github.com/orgzly/orgzly-android/issues/24
Thanks for the pointer, Neil. That is indeed encouraging. I may have
to give up on my desire for encryption on t
m thinking about getting a cheap Android tablet myself in order to
> have a ultra light mobile workstation with termux.
> On the other hand, a terminal console on a 5 inch phone screen doesn't
> seem to be very practical for prolonged work.
>
>
> Martin
>
> On Thu, Oct
Hi folks,
All along, I anticipated using this with Android (and, ideally, also
iOS). The MobileOrg feature set looked great, and the syncing mechanism
looked a lot better than sharing Dropbox.
I use git to share my ~/org between two computers (laptop and desktop),
using git-remote-gcrypt to stor
And I should add - the cause of :LOGBOOK: being above :PROPERTIES: on
those particular tasks may be a bug in an Asana-to-Org converter I
wrote, rather than org itself. So I apologize doubly for the noise.
John
On 10/11/2017 07:46 AM, John Goerzen wrote:
> On 10/11/2017 01:55 AM, Eric S Fr
On 10/11/2017 01:55 AM, Eric S Fraga wrote:
> On Tuesday, 10 Oct 2017 at 22:01, John Goerzen wrote:
>> I cannot make it misbehave with either SCHEDULED or CLOSED in my testing
>> now.
> Maybe try org-lint to see if there are more subtle errors in your
> file(s)?
>
Ah ha! S
On 10/10/2017 08:42 PM, Richard Lawrence wrote:
> Hi John,
>
> John Goerzen writes:
>
>> Unfortunately, org-mode only recognizes the PROPERTIES when they
>> occur immediately after the headline. So whenever I take an action
>> on an item like this, the propertie
So I have a lot of cases where there is a :PROPERTIES: drawer. It
contains, crucially, an ID (I use those for linking). When I close a
task with C-c C-t and pick DONE, or when I schedule it with C-c C-s, it
will insert CLOSED: or SCHEDULED: lines ABOVE the :PROPERTIES: line.
Unfortunately, org-m
