Re: [O] org-time-stamp, day format

[Eric S Fraga]

On Monday,  6 Feb 2017 at 22:33, Uwe Brauer wrote:

[...]

> No idea that is was set up like this do you know by change
> how and where can I change that?

No idea really but I suggest you look at update-locale and locale
commands.  Have a look at /etc/default/locale which should contain the
actual defaults created by update-locale.

I only have

#  File generated by update-locale
LANG="en_GB.UTF-8"
LANGUAGE="en_GB:en"

in my /etc/default/locale file and my environment has no LC_ variables
set, interestingly.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.3-262-g5210de


signature.asc
Description: PGP signature

[O] sub-files in org-mode problems

[Sharon Kimble]

I've now split my current working document up into four unequal parts
because although it was only 1.6mbs if I made virtually any mistake,
then emacs crashed! After it had crashed three times in very quick
succession I'd had enough and spilt it up.

And two things are causing problems.

- How can I have a file split into two parts where the first part starts
  with a chapter heading and then a minitoc, but the second part starts
  with a section heading. I wasn't able to get it to work so I had to
  create a new chapter heading which doesn't look right in the whole
  document. So how can I have the second part starting with a section
  heading please?

- I'm currently getting error reports like this "Warning (:warning):
  Bibtex-completion couldn't find entry with key "0340"." All my
  bibliographic references are numbered and it looks like the sub-file
  can't see or read the bibtex file, even though they're both in the
  same directory. So how can I stop these error reports happening at
  almost every key press please?

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1


signature.asc
Description: PGP signature

[O] Bug in ODT exporter

[Dimitri Minaev]

Hello,

The following minimal text produces a document that cannot be opened
with LibreOffice:

===
- list
  - nested list
| nested table |
===

The resulting 'content.xml' contains a closing tag 
that has no corresponding opening tag.

Org mode version 9.0.4
GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of
2016-04-17 on lgw01-04, modified by Debian

-- 
With best regards,
Dimitri Minaev

Re: [O] Encryption

[Bingo]

On February 7, 2017 3:39:47 AM GMT+05:30, David Diem  wrote:
>Hi all,
>
>on Android, is there a combination of either
>
>1.a. mobileorg
>b. mobileorgNG 
>
>on the one hand and
>
>2.a. APG
>b. OpenKeyChain 
>c. GPG
>
>on the other, and 
>
>3.a. :crypt:
>b. header crypt comment
>
>in Emacs
>
>... that works for people here?
>
>I have tried all (combinations) over and over.
>
>Best wishes
>David (on CyanogenMod 13 and Lineage 14 on a bacon (1+1))
>
>
> Ursprüngliche Nachricht 
>Von: emacs-orgmode-requ...@gnu.org
>Gesendet: 6. Februar 2017 18:00:19 MEZ
>An: emacs-orgmode@gnu.org
>Betreff: Emacs-orgmode Digest, Vol 132, Issue 6
>
>Send Emacs-orgmode mailing list submissions to
>   emacs-orgmode@gnu.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.gnu.org/mailman/listinfo/emacs-orgmode
>or, via email, send a message with subject or body 'help' to
>   emacs-orgmode-requ...@gnu.org
>
>You can reach the person managing the list at
>   emacs-orgmode-ow...@gnu.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Emacs-orgmode digest..."
>
>
>Today's Topics:
>
>   1. Help checking orgcard.pdf (Kyle Meyer)
>   2. Behavior of `org-show-entry' (Eric Abrahamsen)
>   3. Re: Help checking orgcard.pdf (Kaushal Modi)
>   4. Re: Help checking orgcard.pdf (Kyle Meyer)
>   5. Re: Help checking orgcard.pdf (Kaushal Modi)
>   6. Re: Help checking orgcard.pdf (Kyle Meyer)
>   7. Re: Bug: org-agenda-only-exact-dates [9.0.4 (9.0.4-elpa @
> c:/Users/atamulis/.emacs.d/elpa/org-20170124/)] (Tamulis, Andrius)
>   8. Re: Behavior of `org-show-entry' (Kyle Meyer)
>   9. Re: Behavior of `org-show-entry' (Eric Abrahamsen)
>  10. Re: Bug in clocktable report with formula % (Andreas Mueller)
>  11. Re: Behavior of `org-show-entry' (Kyle Meyer)
>  12. org-time-stamp, day format (Uwe Brauer)
>  13. Re: Allowing multiple date trees in a single file
>  (Nicolas Goaziou)
>  14. Re: Behavior of `org-show-entry' (Nicolas Goaziou)
>  15. Re: Bug: org-agenda-only-exact-dates [9.0.4 (9.0.4-elpa @
>  c:/Users/atamulis/.emacs.d/elpa/org-20170124/)] (Nicolas Goaziou)
>  16. Re: Feature request: lists with letters (Rasmus)
>  17. No priority cookies in html export despite setting pri:t
>  option (Gez)
>  18. just saw this: orgzly code source available now on github
>  (Xebar Saram)
>  19. Re: Sync up the org in emacs master to org maint branch?
>  (Phillip Lord)
>  20. Re: just saw this: orgzly code source available now on github
>  (Kaushal Modi)
>
>
>--
>
>Message: 1
>Date: Sun, 05 Feb 2017 12:03:18 -0500
>From: Kyle Meyer 
>To: Org-mode 
>Subject: [O] Help checking orgcard.pdf
>Message-ID: <8760koh8o9@kyleam.com>
>Content-Type: text/plain; charset="us-ascii"
>
>Hello,
>
>On the maint branch, doc/orgcard.tex lists the Org version as 8.2.  I'd
>like to bump this to 9.
>
>It'd be helpful if a few people could look at a topic or two that they
>are familiar with and report back about whether things look up-to-date.
>The card on the website [*] is still stuck at 7.8.11, so I've attached
>one built from the maint branch.
>
>Thanks.
>
>[*] http://orgmode.org/orgcard.pdf
>
>-- next part --
>A non-text attachment was scrubbed...
>Name: orgcard.pdf
>Type: application/pdf
>Size: 118968 bytes
>Desc: not available
>URL:
>
>-- next part --

The data can be encrypted using :crypt: tag, saved  in emacs. Then it can be 
synced to mobileorg, copied to clipboard and pasted into openkeychain to be 
decrypted. I guess you would consider it inconvenient.

Is it necessary to use :crypt: mechanism, or would you be fine with whole file 
encryption? I've been using this for some time :

1. Capture in mobileorg. Sync.
2. In openkeychain, open the mobileorg.org file, encrypt it.
3. Save this encrypted mobileorg.org.gpg file in dropbox.
4. On the computer where dropbox client is running, use inotify to detect 
change in mobileorg.org.gpg. When change is detected - a script automatically 
runs steps 5-9 below :
5. Decrypt the file to mobileorg.org.
6. Run org-mobile-pull 
7. Run org-mobile-push
8. Zip up all org files.
9. Encrypt the zip, store in dropbox.
10. In mobile, within 2-3 minutes, dropbox is ready with the encrypted zip. 
Decrypt using openkeychain, unzip. (AndroZip has a handy one step unzip).
11. Mobileorg sync.

I side step dropbox when at home, directly using LAN copy to the computer using 
Estrongs file explorer, but rest of the steps remain similar.

Probably someone has a simpler suggestion than this.

Thanks
Bingo

Re: [O] Bug in clocktable report with formula %

[Nicolas Goaziou]

Hello,

Andreas Mueller  writes:

> I just noticed with updated org (org-20170124), although days are no
> longer ignored, the percentage calculation is still wrong.
>
> It looks to me like the problem is that org-effort-durations calculates
> minutes in a day with 8 hours per day (I assume the idea was to only
> plan for 8 hour workdays).
>
> Changing org-effort-durations to calculate with 24 hour days gives the
> correct result of 93% / 7%.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-time-stamp, day format

[Nick Dokos]

Eric S Fraga  writes:

> On Monday,  6 Feb 2017 at 22:33, Uwe Brauer wrote:
>
> [...]
>
>> No idea that is was set up like this do you know by change
>> how and where can I change that?
>
> No idea really but I suggest you look at update-locale and locale
> commands.  Have a look at /etc/default/locale which should contain the
> actual defaults created by update-locale.
>
> I only have
>
> #  File generated by update-locale
> LANG="en_GB.UTF-8"
> LANGUAGE="en_GB:en"
>
> in my /etc/default/locale file and my environment has no LC_ variables
> set, interestingly.

If LANG is set, that's enough: all the LC_* default to whatever LANG says,
but you can override them if you set them explicitly.

-- 
Nick

Re: [O] backporting changes to exported results for collaborative editing

[Charles C. Berry]

On Tue, 7 Feb 2017, Marcin Borkowski wrote:



On 2017-02-07, at 02:15, Samuel Wales  wrote:


suppose you export a subtree to ascii or html, and then a bunch of
people want to help you edit it.  obviously you want the changes back
in org.

obviously the best would be if you could give them the source,
complete with comments.  but assume that they are not computer people,
and not org people, and you don't want to give them your irrelevant
comments.

also assume you also don't want to give them your irrelevant tasks and
you do not use org-export-with-tasks.

it might be that i already know the answer: just do the best you can
with diff, and request small sets of changes at a time, or request
manual instructions for changes.  but perhaps you have ideas?


Maybe this could be automated a bit?  Like, org -> markdown, then
people's edits, then diff generating a patch, then some tool existing
only in my dreams currently that converts the md patch to an org patch,
and then apply that patch to the original org?  For small enough
changes, that could actually work, no?



Maybe, but this sequence might be easier:

- export subtree to md =edit-me.md= (body-only not needed but cleaner)

- distribute to editor and retrieve as =editted.md=

- in a shell run ~pandoc -o editted.org editted.md~

- M-x ediff-regions RET
  - select all of =editted.org=
  - select original subtree
  - Use `##' to skip the whitespace only diffs.
  - resolve the differences as appropriate and/or save the diffs.


Babel blocks/results are *not* be handled seamlessly, so more would
need to be done if your editor wants to revise them. Otherwise, just
skip them.

I guess this might work with ascii or html, but I've not tried it.


Chuck

[O] org manual not updating when pulling from git

[Charles Millar]

When pulling from git, shouldn't the manual be updated if for no other 
reason than to refelct the most recent org version?


Up unitl two or three days ago, this was my experience. Now, however, 
none of the documentation seems to be updating, e g.


current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @ 
/usr/local/share/emacs/site-lisp/org-mode/lisp/)


pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)

As far as I know I have not changed any settings on my end.

Charlie MIllar

Re: [O] org manual not updating when pulling from git

[Nick Dokos]

Charles Millar  writes:

> When pulling from git, shouldn't the manual be updated if for no other
> reason than to refelct the most recent org version?
>

It depends on what you mean by "the manual" - the texinfo source is updated,
but any derived files (info, pdf) are not: they are not under source control
at all.

> Up unitl two or three days ago, this was my experience. Now, however,
> none of the documentation seems to be updating, e g.
>
> current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @
> /usr/local/share/emacs/site-lisp/org-mode/lisp/)
>
> pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)
>

"make doc" or "make pdf" will update the PDF file. If you use one of
the update targets in the makefile, it may have been updating the pdf
doc under the covers. Taking a look through recent commits, the only one
that might be relevant seems to be this:

,
| commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
| Author: Marco Wahl 
| Date:   Wed Feb 1 11:16:16 2017 +0100
| 
| targets.mk: Drop the rule to clean at every compile
| 
| Rationale: 1. Save time and energy.  2. Use the make tool for what
| it's been made.
`

So, how do you update?

-- 
Nick

Re: [O] org manual not updating when pulling from git

[Achim Gratz]

Nick Dokos writes:
> "make doc" or "make pdf" will update the PDF file. If you use one of
> the update targets in the makefile, it may have been updating the pdf
> doc under the covers. Taking a look through recent commits, the only one
> that might be relevant seems to be this:
>
> ,
> | commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
> | Author: Marco Wahl 
> | Date:   Wed Feb 1 11:16:16 2017 +0100
> | 
> | targets.mk: Drop the rule to clean at every compile
> | 
> | Rationale: 1. Save time and energy.  2. Use the make tool for what
> | it's been made.
> `

That commit should probably be reverted.  The make tool can't do what
it's been made for in this case since some of the dependencies can not
be correctly determined.  You can still skip the clean if you want to by
using the compile-dirty target.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: [O] org manual not updating when pulling from git

[Marco Wahl]

Hi!

Achim Gratz  writes:

> Nick Dokos writes:
>> "make doc" or "make pdf" will update the PDF file. If you use one of
>> the update targets in the makefile, it may have been updating the pdf
>> doc under the covers. Taking a look through recent commits, the only one
>> that might be relevant seems to be this:
>>
>> ,
>> | commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
>> | Author: Marco Wahl 
>> | Date:   Wed Feb 1 11:16:16 2017 +0100
>> |
>> | targets.mk: Drop the rule to clean at every compile
>> |
>> | Rationale: 1. Save time and energy.  2. Use the make tool for what
>> | it's been made.
>> `
>
> That commit should probably be reverted.  The make tool can't do what
> it's been made for in this case since some of the dependencies can not
> be correctly determined.  You can still skip the clean if you want to by
> using the compile-dirty target.

Ah!  I didn't see target 'compile-dirty'.  Thank you for the hint.

So for now I'm happy with the build process with the existence of

make compile-dirty

and further

make test-dirty

Also the names are well chosen AFAICT.

I agree that the commit should be reverted and I already did the revert.
Please accept my apology for the irritation about the build behavior.


Best regards

   Marco
   

Re: [O] org manual not updating when pulling from git

[Charles Millar]

Hi,


On 02/07/2017 02:41 PM, Nick Dokos wrote:

Charles Millar  writes:


When pulling from git, shouldn't the manual be updated if for no other
reason than to refelct the most recent org version?


It depends on what you mean by "the manual" - the texinfo source is updated,
but any derived files (info, pdf) are not: they are not under source control
at all.


Up unitl two or three days ago, this was my experience. Now, however,
none of the documentation seems to be updating, e g.

current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @
/usr/local/share/emacs/site-lisp/org-mode/lisp/)

pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)


"make doc" or "make pdf" will update the PDF file. If you use one of
the update targets in the makefile, it may have been updating the pdf
doc under the covers. Taking a look through recent commits, the only one
that might be relevant seems to be this:

,
| commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
| Author: Marco Wahl 
| Date:   Wed Feb 1 11:16:16 2017 +0100
|
| targets.mk: Drop the rule to clean at every compile
|
| Rationale: 1. Save time and energy.  2. Use the make tool for what
| it's been made.
`

So, how do you update?

I forgot about make doc; in the past I used it whenever I had to 
recompile org from source; after that the pdf "just updated" each time I 
pulled from git.


Charlie