Re: [O] [bug] timed repeater shows up in wrong place

[Nicolas Goaziou]

Hello,

Samuel Wales  writes:

> On 11/27/16, Nicolas Goaziou  wrote:
>> I pushed a few more fixed in plain time-stamps and deadlines. Please
>> report if you find anything suspicious.
>
> please try this:
>
>   SCHEDULED: <2016-09-17 Sat .+2d>
>
> emacs -Q, with a 2-day span and show-all nil.

[...]

> in org 9:
>
>   1] it shows on both days
>   2] it shows 72x
>
> re 1, dunno if this was intended?

It is.

It shows first repeat. I assume you tested that yesterday, so you got
the repeat for today. Since the repeat didn't trigger "today" (which is
actually yesterday), it also displays a reminder for the scheduled item
there.

So, you have "72x" on "today" and a new repeat on the next day.

> re 2, org 9 is trying to do its counting from the original timestamp
> date.  i can understand the reasoning here, but do not want it for my
> use case.

It is, per 1-year old commit (3072cb28e8627066f465f1a4af85da88135d0549).
Details are given here:
.

> 72x gets buried.  it's a sudden pop up then a sudden drop off.  i want
> a gradual bubbling down like in org 8.  a .+30d repeater should show
> today, then tomorrow it should show 2x, then the next day it should
> show 3x.
>
> org 8 is nicer for showing the fact that 2d ago you were reminded to
> do it, and maybe did it but did not doneify or maybe were not able to
> do it.  it bubbles down slowly.

It's difficult to solve both problems. In any case, this will not happen
in Org 9.0.

I think the main problem is that you put too many things behind
`org-agenda-repeating-timestamp-show-all'. Its name is misleading.
I think we need a new variable, or to change this one, to have both
behaviours possible. Suggestions (and docstrings) are welcome, we can
implement them in master branch.


Regards,

-- 
Nicolas Goaziou

Re: [O] [bug] timed repeater shows up in wrong place

[Samuel Wales]

On 11/27/16, Nicolas Goaziou  wrote:
> I pushed a few more fixed in plain time-stamps and deadlines. Please
> report if you find anything suspicious.

please try this:

  SCHEDULED: <2016-09-17 Sat .+2d>

emacs -Q, with a 2-day span and show-all nil.

in org 8:

  1] it shows today
  2] it shows 2x

which is perfect for my use case.

in org 9:

  1] it shows on both days
  2] it shows 72x

re 1, dunno if this was intended?

re 2, org 9 is trying to do its counting from the original timestamp
date.  i can understand the reasoning here, but do not want it for my
use case.

72x gets buried.  it's a sudden pop up then a sudden drop off.  i want
a gradual bubbling down like in org 8.  a .+30d repeater should show
today, then tomorrow it should show 2x, then the next day it should
show 3x.

org 8 is nicer for showing the fact that 2d ago you were reminded to
do it, and maybe did it but did not doneify or maybe were not able to
do it.  it bubbles down slowly.

Re: [O] TODO keyword faces do not work when tags are globally set

[Maria Shinoto]

Hi,

Thanks for your answer.

It was another beginner's fault that happened during some polishing of 
my init file.


After all, the init file loaded my TODO file before before setting the 
TODO keywords and their faces; now the files are loaded in the end of 
the init process, and everything works again.


Sorry for bothering you!

Best,
Maria


PS I feel uneasy upgrading to 9.01 at the moment, since I am not yet 
comfortable with emacs and org mode and may explanations on the web 
still do not apply to 9.0, which changed a lot, as far as I understand.






Am 27.11.16 um 20:16 schrieb Nicolas Goaziou:

Hello,

Maria Shinoto  writes:


I have set TODO-keywords in my init.el file and also set colors etc.
for the different TODO keywords, works fine.

Today I wanted to set tags globally in the init file as well, but then
the TODO keywords do not seem to be recognized any more. They get the
same color and font face as the headline.

I simply set

   (setq org-tag-alist '("@haus" .))

and tried it both before setting the TODO keywords and the font faces
as well as afterwards.

I am working with Org-mode 8.3.6, and my emacs is 25.1


Could you try again with latest release (Org 9.0.1)?

Regards,

Re: [O] [bug] timed repeater shows up in wrong place

[Nicolas Goaziou]

Samuel Wales  writes:

> when show all is nil, i expect the second of a two-day span to not
> show the repeater if the first shows it.  org 8 seems more correct to
> me.

I pushed a few more fixed in plain time-stamps and deadlines. Please
report if you find anything suspicious.

Regards,

Re: [O] Bug: Capital lettered plain lists export as numbered

[Nicolas Goaziou]

Hello,

Scott Otterson  writes:

> In my org file, I have ordered capital lettered plain lists like this:
>
> A. Item A
> B. Item B
> a. subitem a
> b. submitem b
> C. Item C
>
>
> But when I export them to a pdf via latex, they look like this:
>
> 1. Item A
> 2. Item B
> (a) subitem a
> (b) submitem b
> 3. Item C
>
>
> Is this a bug or is it expected behavior?

It is the expected behaviour. Bullets used in an Org document are not
meant to control how the list is to be exported.

Regards,

-- 
Nicolas Goaziou

[O] Bug: Capital lettered plain lists export as numbered

[Scott Otterson]

In my org file, I have ordered capital lettered plain lists like this:

A. Item A
B. Item B
a. subitem a
b. submitem b
C. Item C


But when I export them to a pdf via latex, they look like this:

1. Item A
2. Item B
(a) subitem a
(b) submitem b
3. Item C


Is this a bug or is it expected behavior?

--- test .org file 

A. Item A
B. Item B
   a. subitem a
   b. submitem b
C. Item C

-- my setup 
Emacs  : GNU Emacs 25.1.1 (i686-w64-mingw32)
 of 2016-09-17
Package: Org mode version 9.0.1 (9.0.1-elpa @
c:/Users/scott/OneDrive/scotto/.emacs.d/elpa/org-20161118/)

Re: [O] Bug: Windows-unfriendly filename in org-preview-latex-process-alist customization

[Nicolas Goaziou]

Scott Otterson  writes:

> Happy to try it out.  Should I expect the change on elpa/org sometime
> soon?

If you cannot test it straight from Org repository, you need to wait
until tomorrow. It will then be included in the new Org ELPA package.

Regards,

Re: [O] Bug: Windows-unfriendly filename in org-preview-latex-process-alist customization

[Scott Otterson]

Happy to try it out.  Should I expect the change on elpa/org sometime soon?

Scott

On Sun, Nov 27, 2016 at 12:12 PM, Nicolas Goaziou 
wrote:

> Hello,
>
> Scott Otterson  writes:
>
> > Thanks Fabrice.  After more experimentation, I found that image-converter
> > field of the customization alist should be:
> >
> > ("dvipng -fg %F -bg %B -D %D -T tight -o \"%o%b\.png\" %f")
> >
> > If this also works for *nix, then I hope that the org-mode maintainers
> will
> > make this string the new default.  If it doesn't work on linux, then I
> hope
> > that it's possible to come up with a string that works in both OS
> families
> > (and that could be the new default).  I'll be back on Linux in a few
> > months, and would love to keep a simple, cross-platform .emacs file.
>
> I introduced %O, which is the absolute output file name, as
> a replacement for %o%b.extension.
>
> Could you confirm the bug is fixed?
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] Track time on day-to-day basis

[Joost Kremers]

Hi Oliver,

On Fri, Nov 25 2016, ngre...@gmx.net wrote:

I do reports on a day-to-day basis using clocktables:

#+BEGIN: clocktable :maxlevel 4 :block 2016-11 :scope 
("./Projekt01.org") :link t :step day :stepskip0


#+END:

Hope this helps.


Yes, that's exactly what I was looking for, thanks!

--
Joost Kremers
Life has its moments

Re: [O] [bug] timed repeater shows up in wrong place

[Samuel Wales]

On 11/27/16, Nicolas Goaziou  wrote:
> It sounds correct. With ".+1d" repeater, you expect to repeat the task
> every day.

when show all is nil, i expect the second of a two-day span to not
show the repeater if the first shows it.  org 8 seems more correct to
me.

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  And
ANYBODY can get it.

Denmark: free Karina Hansen NOW.
  UPDATE 2016-10: home, but not fully free

[O] org-open-at-point and buffer-name

[Fabrice Popineau]

Hi,

I have some foo.org file :

* Section
  This is a [[file:bar.org::#home][link]

and a bar.org file :

* Section
:PROPERTIES:
:CUSTOM_ID: home
:END:
Lorem ipsum ...

If I put the cursor in foo.org on the link ant I try to evaluate (M-:)
(progn (org-open-at-point) (buffer-name))
I get "foo.org" as a result.
However the window displays bar.org and my cursor is in in bar.org.
By which mystery ?

I am missing something here ... but what ?

Fabrice

[O] tangling files on export not working properly

[mcg]

Hello,

When exporting my document to latex I want org-mode to tangle a few code 
blocks.


#+NAME: tangle_files
#+BEGIN_SRC emacs-lisp :exports results :eval query-export

(org-babel-tangle-file "~/thesis/chapter/NH.org")

#+END_SRC

When I run the code block manually it works fine
*Messages*: "Tangled 2 code blocks from NH.org"

However, even though the is run on export, nothing gets tangled:
"Tangled 0 code blocks from 04.NH.org"

Is there any explanation for this? Anything I'm overlooking?

Re: [O] Frame-break with beamer

[Eric S Fraga]

On Sunday, 27 Nov 2016 at 15:03, Nicolas Goaziou wrote:

[...]

> Wouldn't setting :BEAMER_ENV: property to "frame" in each subheading
> solve OP's problem?

Interesting.  I am not sure what beamer does with a frame environment
inside another such environment.  Maybe the OP can tell us!

-- 
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)

Re: [O] Frame-break with beamer

[Nicolas Goaziou]

Hello,

Eric S Fraga  writes:

> On Saturday, 26 Nov 2016 at 13:34, Peter Sterner wrote:
>> Hi,
>>
>> I'm trying to export an org-file to a beamer presentation. I would
>> like to divide a frame into two or more frames.
>
> I don't think this is possible in org.  You could possibly manage it
> with some LaTeX magic (redefining the block environment temporarily to
> be a frame environment) but it would be quite fragile...  If the
> requirement is due to how you want to manipulate and view the org file,
> I would suggest re-thinking the layout more fundamentally maybe, such as
> using top level headlines as sections with frames at second level.

Wouldn't setting :BEAMER_ENV: property to "frame" in each subheading
solve OP's problem?


Regards,

-- 
Nicolas Goaziou

Re: [O] Frame-break with beamer

[Eric S Fraga]

On Saturday, 26 Nov 2016 at 13:34, Peter Sterner wrote:
> Hi,
>
> I'm trying to export an org-file to a beamer presentation. I would
> like to divide a frame into two or more frames.

I don't think this is possible in org.  You could possibly manage it
with some LaTeX magic (redefining the block environment temporarily to
be a frame environment) but it would be quite fragile...  If the
requirement is due to how you want to manipulate and view the org file,
I would suggest re-thinking the layout more fundamentally maybe, such as
using top level headlines as sections with frames at second level.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.1-49-ga43eac

Re: [O] TODO keyword faces do not work when tags are globally set

[Nicolas Goaziou]

Hello,

Maria Shinoto  writes:

> I have set TODO-keywords in my init.el file and also set colors etc.
> for the different TODO keywords, works fine.
>
> Today I wanted to set tags globally in the init file as well, but then
> the TODO keywords do not seem to be recognized any more. They get the
> same color and font face as the headline.
>
> I simply set
>
>(setq org-tag-alist '("@haus" .))
>
> and tried it both before setting the TODO keywords and the font faces
> as well as afterwards.
>
> I am working with Org-mode 8.3.6, and my emacs is 25.1

Could you try again with latest release (Org 9.0.1)?

Regards,

-- 
Nicolas Goaziou

Re: [O] [bug] timed repeater shows up in wrong place

[Nicolas Goaziou]

Hello,

Samuel Wales  writes:

> you recently fixed a few things from your patch.  dunno if it was
> supposed to or not, but it seems to have cleared up a lot of bugs.
>
> i found a lot of differences from org 8 to your patch, but only one
> from org 8 to your recent fixes: a bare ts like <2016-11-23 Wed 12:00
> .+1d> shows up twice in a 2-day span, but only showed up once in org
> 8.  i will post mce if needed.

It sounds correct. With ".+1d" repeater, you expect to repeat the task
every day.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: Windows-unfriendly filename in org-preview-latex-process-alist customization

[Nicolas Goaziou]

Hello,

Scott Otterson  writes:

> Thanks Fabrice.  After more experimentation, I found that image-converter
> field of the customization alist should be:
>
> ("dvipng -fg %F -bg %B -D %D -T tight -o \"%o%b\.png\" %f")
>
> If this also works for *nix, then I hope that the org-mode maintainers will
> make this string the new default.  If it doesn't work on linux, then I hope
> that it's possible to come up with a string that works in both OS families
> (and that could be the new default).  I'll be back on Linux in a few
> months, and would love to keep a simple, cross-platform .emacs file.

I introduced %O, which is the absolute output file name, as
a replacement for %o%b.extension.

Could you confirm the bug is fixed?

Regards,

-- 
Nicolas Goaziou

[O] TODO keyword faces do not work when tags are globally set

[Maria Shinoto]

Hi,

I have set TODO-keywords in my init.el file and also set colors etc. for 
the different TODO keywords, works fine.


Today I wanted to set tags globally in the init file as well, but then
the TODO keywords do not seem to be recognized any more. They get the 
same color and font face as the headline.


I simply set

   (setq org-tag-alist '("@haus" .))

and tried it both before setting the TODO keywords and the font faces as 
well as afterwards.


I am working with Org-mode 8.3.6, and my emacs is 25.1



Thanks for your help!

Maria

Re: [O] org-mode latex export - Links in multi-document files

[Nicolas Goaziou]

Hello,

mcg  writes:

> I sometimes make references to other sections which are in another
> section and document.
> In order to not compile all the document (3 minutes +) every time
> I just comment out all the documents I do not need to.
> If table and figure links are missing it exports fine (getting
> question marks in the pdf). However, the section links cause the
> compilation to stop entirely. Is there any workaround for that? Can
> I tell the exporter to ignore such minor missing crossreferences?

See `org-export-with-broken-links' (org 9.0).

Regards,

-- 
Nicolas Goaziou