Re: [O] *Good* client for Android?

[Eric Thomas]

Hi John,

I like installing GNURootDebian (from source at
https://github.com/corbinlc/GNURootDebian) with Hackers Keyboard (from
Fdroid at https://f-droid.org/packages/org.pocketworkstation.pckeyboard/)
on my Android devices. Then slapping a fresh instance of emacs on
there.

File perms and file system can be a bit tricky to get used to, but
once you get it, you basically have a working Debian instance on
Android. From there you can VC your dotfiles and orgfiles just like
you would another machine.

See this issue https://github.com/corbinlc/GNURootDebian/issues/159)
for good insights on how to install on a Nexus 7.

Take care

[O] Solved: Bug: org-encrypt-entry fails [9.1.2 (9.1.2-elpa @ /Users/dmm/.emacs.d/elpa/org-20171004/)]

[David Maslen]

Solved. 
Problem was that in graphical mode I saw no password prompt. Failed without a 
useful failure message.
Perhaps org-crypt could be improved to catch this situation?

Starting emacs in a terminal worked, as the password prompt was in the 
originating terminal window.
On a Mac, I tended to start emacs from the dock, so no terminal.

Solution was to follow the instruction in pinentry. 
I then added (pinenty-start) to my .emacs init file.
No org-encrypt-entry prompts for a password in the minibuffer.


pinentry is a built-in package.

 Status: Built-In.
Version: 0.1
Summary: GnuPG Pinentry server implementation
Other versions: 0.1 (gnu).


This package allows GnuPG passphrase to be prompted through the
minibuffer instead of graphical dialog.

To use, add "allow-emacs-pinentry" to "~/.gnupg/gpg-agent.conf",
reload the configuration with "gpgconf --reload gpg-agent", and
start the server with M-x pinentry-start.



> On 14 Oct 2017, at 3:33 am, Nicolas Goaziou  wrote:
> 
> Hello,
> 
> David Maslen  writes:
> 
>> In the example below the words “test this” are not replaced by encrypted
>> text.
>> My previous experience is that the entire contents of a org subheading
>> structure marked with the :crypt: tag would be encrypted/decrypted by the
>> related org function.
> 
> I cannot reproduce it. The text is properly replaced by encrypted text
> here.
> 
> Regards,
> 
> -- 
> Nicolas Goaziou0x80A93738

[O] The error "Opening input file: No such file or directory" should show the source org file

[Joon Ro]

Hi,

I often see the error message: "Opening input file: No such file or directory" 
for one of the org files that has wrong file path for a #+SETUPFILE. It usually 
happens when I change the path of the setup file which is used by multiple org 
files.

However, currently it is hard to locate the file where the error is originated 
from. I think it would be great if the error message shows the location of the 
file as well.

Best Regards,
Joon

Re: [O] *Good* client for Android?

[Leslie Watter]

Dropbox has quitted their v1 API access a few days ago (Sept 28th), so
probably your problem with Dropbox will be everyone' s using MobileOrg
(including myself) and Dropbox.

Unfortunatelly I won' t have time to tackle with this until December 15th,
but I'm planning to upgrade MobileOrg's Dropbox API support (and perhaps
add a few new features).

Cheers,

LEslie

On Fri, Oct 13, 2017 at 10:49 AM, Eric S Fraga  wrote:

> On Friday, 13 Oct 2017 at 08:34, John Goerzen wrote:
>
> [...]
>
> > The bitrot is a big concern.  Android moves pretty fast, and something
> > that was last updated in 2013 is likely to not play well with a phone on
> > Oreo (such as mine).  I could be surprised, I suppose.
>
> I agree with the concern but I must admit at being quite impressed how
> robust MobileOrg seems to be with respect to changes in Android
> versions.  I've been using it for quite a few years now and have gone
> through various phones/tablets and multiple versions of Android without
> any issues.
>
> The problem with Dropbox is due to Dropbox and not Android.
>
> --
> : Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-98-g0b8316
>



-- 
Leslie H. Watter

[O] Help with org related crash on OpenBSD

[Aaron Bieber]

Hola,

I am trying to track down an issue where emacs hangs on OpenBSD when
using org-capture. I happens with org 9.1.2 and 8.2.10 in emacs
25.3.1.

It seems that 3 out of 4 times, emacs completely hangs when adding a
Todo. I have tried setting (toggle-debug-on-quit) and
(toggle-debug-on-error), but once the hang happens emacs becomes
completely unresponsive. The one time that it doesn't hang, it takes
around 3 or 4 seconds to actually open up the gtd.org file.

I can't reproduce on non-OpenBSD systems

The config is fairly simple:

(require 'org)

(setq org-directory "~/new_org")
(setq org-agenda-files (file-expand-wildcards "~/new_org/*.org"))
(setq org-journal-dir "~/new_org/journal/")
(setq org-mobile-directory "~/new_org/MobileOrg")
(setq org-log-done 'time)

(setq org-capture-templates
  `(("t" "Todo"
 entry (file+headline "~/new_org/gtd.org" "TODOs")
 "* TODO %?\n  :PROPERTIES:\n  :LOGGING: TODO(!) WAIT(!) DONE(!) 
CANCELED(!)\n  :END:\n")
("j" "Journal"
 entry (file+olp+datetree "~/new_org/journal-%Y-%m.org")
 "* %?\nEntered on %U\n  %i\n  %a")))

(global-set-key "\C-cc" 'org-capture)
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cb" 'org-iswitchb)

Any suggestions would be greatly appreciated!

Cheers,
Aaron

--
PGP: 0x1F81112D62A9ADCE / 3586 3350 BFEA C101 DB1A  4AF0 1F81 112D 62A9 ADCE

Re: [O] Bug: org-encrypt-entry fails [9.1.2 (9.1.2-elpa @ /Users/dmm/.emacs.d/elpa/org-20171004/)]

[Nicolas Goaziou]

Hello,

David Maslen  writes:

> In the example below the words “test this” are not replaced by encrypted
> text.
> My previous experience is that the entire contents of a org subheading
> structure marked with the :crypt: tag would be encrypted/decrypted by the
> related org function.

I cannot reproduce it. The text is properly replaced by encrypted text
here.

Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] org-clock-in only in current buffer

[Matt Lundin]

"Julian M. Burgos"  writes:

> Dear org-moders,
>
> Until a recent update (or an unintended change in my configuration), I
> was able to clock in a task (org-clock-in) *without* org mode trying
> to find open clocks. I cannot figure out what changed, but now
> org-clock-in opens all my agenda buffers searching for open clocks,
> which is not very convenient as I have dozens of agenda files. What
> would be the best way to a) restrict the search of open clocks to the
> current buffer, or b) turn off the search of open clocks?
>

I believe you can set org-clock-auto-clock-resolution to nil to stop
the search for open clocks.

Best,
Matt

Re: [O] *Good* client for Android?

[Eric S Fraga]

On Friday, 13 Oct 2017 at 08:34, John Goerzen wrote:

[...]

> The bitrot is a big concern.  Android moves pretty fast, and something
> that was last updated in 2013 is likely to not play well with a phone on
> Oreo (such as mine).  I could be surprised, I suppose.

I agree with the concern but I must admit at being quite impressed how
robust MobileOrg seems to be with respect to changes in Android
versions.  I've been using it for quite a few years now and have gone
through various phones/tablets and multiple versions of Android without
any issues.

The problem with Dropbox is due to Dropbox and not Android.

-- 
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-98-g0b8316


signature.asc
Description: PGP signature

Re: [O] *Good* client for Android?

[John Goerzen]

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."
>>
>> Suggestions?
>
> I am not sure what you are asking for.  What is missing in MobileOrg?
> You say it is suffering from bitrot but it works just fine for me on a
> daily basis, with no issues having multiple Android devices using the
> same location.  Okay, it no longer works with Dropbox but it does work
> with a number of other media.

The bitrot is a big concern.  Android moves pretty fast, and something
that was last updated in 2013 is likely to not play well with a phone on
Oreo (such as mine).  I could be surprised, I suppose.

I want as conflict-free a setup as possible, with good resolution of
conflicts when they do occur.  MobileOrg seems to be good at this, just
from reading the manual.  I'm not convinced that, say, Orgzly would be.

The other is that there is a lack of support for encryption.  It is not
an absolute requirement for me, but is certainly very much a "nice to
have".  Storing unencrypted stuff on a server is not really ideal.

(None of the other mobile clients save MobileOrg for iOS seem to have
this feature either.)

> For instance, I have recently started playing with org-dropbox [1] for
> capturing notes from an Android device.  But I will keep using MobileOrg
> as I need Google calendar synchronisation.

That's an interesting project - thanks.

-- John

Re: [O] *Good* client for Android?

[John Goerzen]

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 the server, but this does
indeed sound appealing.

>
> I am enjoying the Orgzly UI on my phone, and I have similar org-mode usage to 
> you, in that l also already use a git repo to
> synchronize changes that l make on two separate laptops. So when that Orgzly 
> enhancement lands, I think it will be Ideal for me.
>
> Best wishes,
> Neil

[O] tiny bug in ox-koma-letter.el

[Alan Schmitt]

Hello,

I'm exporting a letter without a to-address, and it generates a spurious
"mbox" in the letter. I found that if I change line 708 of
ox-koma-letter.el from "mbox{}" to "\\mbox{}" the problem goes away.
Is this a (known) bug?

Thanks,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-09: 403.38, 2016-09: 401.03


signature.asc
Description: PGP signature

Re: [O] *Good* client for Android?

[Neil Jerram]

Hi John,There is a great discussion about adding git synchronization to Orgzly, in progress here: https://github.com/orgzly/orgzly-android/issues/24I am enjoying the Orgzly UI on my phone, and I have similar org-mode usage to you, in that l also already use a git repo to synchronize changes that l make on two separate laptops. So when that Orgzly enhancement lands, I think it will be Ideal for me.Best wishes,      Neil

Re: [O] *Good* client for Android?

[Eric S Fraga]

On Thursday, 12 Oct 2017 at 16:28, John Goerzen wrote:
> 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 store on a server.  This makes syncing and
> resolving conflicts easy (I move between the two throughout the day, so
> 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."
>
> Suggestions?

I am not sure what you are asking for.  What is missing in MobileOrg?
You say it is suffering from bitrot but it works just fine for me on a
daily basis, with no issues having multiple Android devices using the
same location.  Okay, it no longer works with Dropbox but it does work
with a number of other media.

Maybe I missed it but what is not clear is what features you actually
require that you don't have other than the encryption aspect mentioned
above.

For instance, I have recently started playing with org-dropbox [1] for
capturing notes from an Android device.  But I will keep using MobileOrg
as I need Google calendar synchronisation.

The only way to truly work with org on your phone would be to have Emacs
on your phone.  That *is* possible but the currently available solutions
are less than useful (IMO).  The second best is to ssh to a system
running Emacs (as has already been suggested).

My own full solution is to have a palm sized computer running Emacs: the
Pandora [2] which is (hopefully) soon to be replaced by the Pyra [3].

eric

Footnotes: 
[1]  https://github.com/heikkil/org-dropbox

[2]  https://en.wikipedia.org/wiki/Pandora_(console)

[3]  https://pyra-handheld.com/boards/pages/pyra/

-- 
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-98-g0b8316


signature.asc
Description: PGP signature