Re: [O] Bug: Table does not align properly [9.1.13 (9.1.13-elpaplus @ /home/diogo/.emacs.d/elpa/org-plus-contrib-20180521/)]
Can I clone that version? On Thu, Jun 7, 2018 at 2:49 PM Nicolas Goaziou wrote: > Diogo Ferrari writes: > > > Would you know when the 9.2 is planned to be released? > > Very soon, or so I think. Bastien may have a definitive answer on the > subject. > > Regards, > -- Diogo Ferrari PhD Candidate University of Michigan, Ann Arbor Department of Political Science E-mail: dferr...@umich.edu Website: http://dioferrari.wordpress.com/ Open Source! Use R! Use Linux! Use Emacs! Use Python! "A vida é a arte de tirar conclusões suficientes de dados insuficientes"
Re: [O] Bug: Tables not aligning properly [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)]
Nicolas Goaziou writes: > Hello, > > Joao Pedro Pedroso writes: > >> This bug seems to be related to the presence >> of TAB characters in the table. > > Could you try master branch (yet to be release Org 9.2), as it may have > been fixed already. > > If it isn't fixed, could you provide an ECM? > The SE post says that whatever was broken was fixed in 9.1.6, but you still see it in 9.1.9? FWIW, I cannot reproduce it in Org mode version 9.1.13 (release_9.1.13-880-g120f87) ECM = exemple complet minimal = minimal complete example (aka MWE = minimal working example). -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: [O] Bug: problem with org-agenda and categories [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]
PSA:
This was discussed on the list and the outcome was that it is not a bug.
The OP misused the CATEGORY keyword in a way that has been deprecated since
2008.
Here's a version of the OP's file that behaves as expected.
More details about the CATEGORY changes and the deprecation can be found at
https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS#L1642
N.B. There are CATEGORY properties under each heading (and since
property drawers are only recognized immediately after a heading
(modulo scheduling information), the new headings are mandatory:
--8<---cut here---start->8---
* the world cup on my agenda
** group stage
:PROPERTIES:
:CATEGORY: groups
:END:
%%(diary-block 6 22 2018 6 22 2018) 7:00 wc: brazil - costa rica (sans
petersburgo){GE2}
%%(diary-block 6 22 2018 6 22 2018) 10:00 wc: nigeria - islanda
(volgogrado){GD2}
%%(diary-block 6 22 2018 6 22 2018) 13:00 wc: serbia - suiza (kaliningrado){GE2}
%%(diary-block 6 23 2018 6 23 2018) 07:00 wc: belgica - tunez (otkrytiye,
moscu){GG2}
%%(diary-block 6 23 2018 6 23 2018) 10:00 wc: mexico - korea (rostov){GF2}
%%(diary-block 6 23 2018 6 23 2018) 13:00 wc: alemania - suecia (sochi){GF2}
%%(diary-block 6 24 2018 6 24 2018) 07:00 wc: inglaterra - panama (nizhny){GG2}
%%(diary-block 6 24 2018 6 24 2018) 10:00 wc: japon - senegal
(ekaterimburgo){GH2}
%%(diary-block 6 24 2018 6 24 2018) 13:00 wc: colombia - polonia (kazán){GH2}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: uruguay - rusia (samara){GA3}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: egipto - arabia (volgogrado){GA3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: portugal - iran (saransk){GB3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: espanha - marruecos
(kaliningrado){GB3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: Dinamarca - francia (luzhniki,
moscu){GC3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: PERÙ - australia (sochi){GC3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: argentina - nigeria (san
petersburgo){GD3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: croacia - islandia (rostov){GD3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: corea - alemania (kazán){GF3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: mexico - suecia
(ekaterimburgo){GF3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: brazil - serbia (otkrytiye,
moscu){GE3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: suiza - costa rica (nizhny){GE3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: polonia - japon (volgogrado){GH3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: colombia - senegal (samara){GH3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: inglaterra - belgica
(kaliningrado){GG3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: panama - tunez (saransk){GG3}
** 16
:PROPERTIES:
:CATEGORY: 8
:END:
%%(diary-block 6 30 2018 6 30 2018) 09:00 wc: 1cFrancia - 2dArgentina
(kazán){16}
%%(diary-block 6 30 2018 6 30 2018) 13:00 wc: 1aUruguay -2bPortugal (sochi){16}
%%(diary-block 7 01 2018 7 01 2018) 09:00 wc: 2aRusia - 1bEspaña (moscu){16}
%%(diary-block 7 01 2018 7 01 2018) 13:00 wc: 2cDinamarca - 1dCroacia
(nizhny){16}
%%(diary-block 7 02 2018 7 02 2018) 09:00 wc: 1eBrazil - 2fMexico (samara){16}
%%(diary-block 7 02 2018 7 02 2018) 13:00 wc: 1gBelgica - 2hJapon (rostov){16}
%%(diary-block 7 03 2018 7 03 2018) 09:00 wc: 2eSuiza - 1fSuecia (san
petersburgo){16}
%%(diary-block 7 03 2018 7 03 2018) 13:00 wc: 2gInglaterra - 1hColombia
(moscu){16}
** 8
:PROPERTIES:
:CATEGORY: 4
:END:
%%(diary-block 7 06 2018 7 06 2018) 09:00 wc: 1qfFrancia - 2qfUruguay
(nizhny){4}
%%(diary-block 7 06 2018 7 06 2018) 13:00 wc: 5qfBrasil - 6qfBelgica (kazán){4}
%%(diary-block 7 07 2018 7 07 2018) 09:00 wc: 7qfRusia - 8qfCrocia (samara){4}
%%(diary-block 7 07 2018 7 07 2018) 13:00 wc: 3qfSuecia - 4qfInglaterra
(sochi){4}
** Semifinal
:PROPERTIES:
:CATEGORY: semi-final
:END:
%%(diary-block 7 10 2018 7 10 2018) 09:00 wc: 1sf - 2sf (san petersburgo){SF}
%%(diary-block 7 11 2018 7 11 2018) 09:00 wc: 3sf - 4sf (moscu){SF}
** Final
:PROPERTIES:
:CATEGORY: final
:END:
%%(diary-block 7 14 2018 7 14 2018) 09:00 wc: 1p - 2p (san petersburgo){F}
%%(diary-block 7 15 2018 7 15 2018) 09:00 wc: 1f - 2f (luzhniki, moscu){F}
--8<---cut here---end--->8---
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: [O] Bug: org-git-link to use SHA1 instead of master@{date} [9.1.13 (9.1.13-elpaplus @ /home/kvaneesh/.emacs.d/elpa/develop/org-plus-contrib-20180702/)]
aneesh.ku...@linux.vnet.ibm.com (Aneesh Kumar K.V) writes: > So my old org file when following git links is giving me error like > > "Log for master only goes back to 'x' date". Can we not refer a link > via git:/filename::sha1:: ? > AFAIK, there is no support for git links in Org mode. Perhaps you have installed an extension? There is an org-git-link.el in contrib/. Is that perhaps what you are using? If so, it might have bit-rotted a bit and might need some TLC to bring it up to snuff (the contrib/ stuff is just that: it's not part of Org mode proper, although the fact that the code is immediately available often - but *NOT* always - means that somebody will take a look and patch it.) -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: [O] malformed function
On Wed, Jul 11, 2018 at 11:35:14AM +0200, Joost Kremers wrote: > > Note that the documentation for `flet' says that it has been obsolete since > Emacs 24.3 and that you should be using `cl-flet' instead (or `cl-letf', but > that doesn't seem to be what you want). So best thing to do is to replace > `flet' with `cl-flet' and then add `(require 'cl-lib)' somewhere at the top > of your init file, and you should be good to go. Looks like that solved it. Thanks much! --hymie! http://lactose.homelinux.net/~hymiehy...@lactose.homelinux.net
Re: [O] Bug: Tables not aligning properly [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)]
Hello, Joao Pedro Pedroso writes: > This bug seems to be related to the presence > of TAB characters in the table. Could you try master branch (yet to be release Org 9.2), as it may have been fixed already. If it isn't fixed, could you provide an ECM? Thank you. Regards, -- Nicolas Goaziou
Re: [O] malformed function
On Wed, Jul 11 2018, Joost Kremers wrote: On Mon, Jul 09 2018, hymie! wrote: Greetings. I know this is technically Technically and practically. ;-) Actually, I just now noticed your code is coming from worg, so that makes it not completely off-topic, I'd say. -- Joost Kremers Life has its moments
Re: [O] malformed function
On Mon, Jul 09 2018, hymie! wrote: Greetings. I know this is technically Technically and practically. ;-) an emacs problem and not an Orgmode problem, but maybe you guys will see the error that I can't find. A better place to ask would probably be the mailing list help-gnu-emacs, but: I have two different machines. One is a Linux machine running Orgmode 9.1.13 under Emacs 25.3.1 , and one is a Windows 10 machine running Orgmode 9.1.13 under Emacs 24.5.1 . Both have the same .emacs file as far as I can tell. Try diff or ediff to make sure. The Linux machine is getting this error: Warning (bytecomp): ‘(extract-window (line) (let ((start (get-text-property 1 (quote time-of-day) line)) (dur (get-text-property 1 (quote duration) line))) (cond ((and start dur) (cons start (org-time-from-minutes (+ dur (org-time-to-minutes start) (start start) (t nil’ is a malformed function That means that the entire s-expr (extract-window ... nil is being interpreted as a function, which is caused by the fact that it is the first element of the list ((extract-window ... nil) (note extra pair of parens). Since such an s-expr cannot be a function, you get an error. The fact that it is interpreted as a function indicates that the byte compiler doesn't know that `flet' is a macro, which in turn indicates that you haven't loaded the required library. Note that the documentation for `flet' says that it has been obsolete since Emacs 24.3 and that you should be using `cl-flet' instead (or `cl-letf', but that doesn't seem to be what you want). So best thing to do is to replace `flet' with `cl-flet' and then add `(require 'cl-lib)' somewhere at the top of your init file, and you should be good to go. Why you're only getting this error on one machine isn't entirely clear to me. It could be that something changed between Emacs 24 and 25 that causes this, it could be that you're loading a package on the Windows machine that loads cl or cl-lib and that you don't use on Emacs. HTH -- Joost Kremers Life has its moments
[O] bug#32068: 26.1; problem with org-agenda and categories
Hi Nicolas.
> > I still think this is a bug. Let me explain You why.
>
> If you try "M-x org-lint" on your document, you'll discover what is your
> problem. In short, your usage of CATEGORY keyword is not possible
> anymore. It's a global keyword, like any other keyword.
I have tried org-lint it suggest me to use :CATEGORY: property. As I
have done on my example. But still It Does not work.
> Use headlines to separate your documents into parts with different
> categories.
I have created also headlines. But even with that. I can not get
previous behaviour.
see my modified file:
--8<---cut here---start->8---
* the world cup on my agenda
** groups
:CATEGORY: 0.6groups
%%(diary-block 6 22 2018 6 22 2018) 7:00 wc: brazil - costa rica (sans
petersburgo){GE2}
%%(diary-block 6 22 2018 6 22 2018) 10:00 wc: nigeria - islanda
(volgogrado){GD2}
%%(diary-block 6 22 2018 6 22 2018) 13:00 wc: serbia - suiza (kaliningrado){GE2}
%%(diary-block 6 23 2018 6 23 2018) 07:00 wc: belgica - tunez (otkrytiye,
moscu){GG2}
%%(diary-block 6 23 2018 6 23 2018) 10:00 wc: mexico - korea (rostov){GF2}
%%(diary-block 6 23 2018 6 23 2018) 13:00 wc: alemania - suecia (sochi){GF2}
%%(diary-block 6 24 2018 6 24 2018) 07:00 wc: inglaterra - panama (nizhny){GG2}
%%(diary-block 6 24 2018 6 24 2018) 10:00 wc: japon - senegal
(ekaterimburgo){GH2}
%%(diary-block 6 24 2018 6 24 2018) 13:00 wc: colombia - polonia (kazán){GH2}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: uruguay - rusia (samara){GA3}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: egipto - arabia (volgogrado){GA3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: portugal - iran (saransk){GB3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: espanha - marruecos
(kaliningrado){GB3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: Dinamarca - francia (luzhniki,
moscu){GC3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: PERÙ - australia (sochi){GC3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: argentina - nigeria (san
petersburgo){GD3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: croacia - islandia (rostov){GD3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: corea - alemania (kazán){GF3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: mexico - suecia
(ekaterimburgo){GF3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: brazil - serbia (otkrytiye,
moscu){GE3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: suiza - costa rica (nizhny){GE3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: polonia - japon (volgogrado){GH3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: colombia - senegal (samara){GH3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: inglaterra - belgica
(kaliningrado){GG3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: panama - tunez (saransk){GG3}
** dieciseis
:CATEGORY: hello
%%(diary-block 6 30 2018 6 30 2018) 09:00 wc: 1cFrancia - 2dArgentina
(kazán){16}
%%(diary-block 6 30 2018 6 30 2018) 13:00 wc: 1aUruguay -2bPortugal (sochi){16}
%%(diary-block 7 01 2018 7 01 2018) 09:00 wc: 2aRusia - 1bEspaña (moscu){16}
%%(diary-block 7 01 2018 7 01 2018) 13:00 wc: 2cDinamarca - 1dCroacia
(nizhny){16}
%%(diary-block 7 02 2018 7 02 2018) 09:00 wc: 1eBrazil - 2fMexico (samara){16}
%%(diary-block 7 02 2018 7 02 2018) 13:00 wc: 1gBelgica - 2hJapon (rostov){16}
%%(diary-block 7 03 2018 7 03 2018) 09:00 wc: 2eSuiza - 1fSuecia (san
petersburgo){16}
%%(diary-block 7 03 2018 7 03 2018) 13:00 wc: 2gInglaterra - 1hColombia
(moscu){16}
** octavos
:CATEGORY: 0.octavos
%%(diary-block 7 06 2018 7 06 2018) 09:00 wc: 1qfFrancia - 2qfUruguay
(nizhny){4}
%%(diary-block 7 06 2018 7 06 2018) 13:00 wc: 5qfBrasil - 6qfBelgica (kazán){4}
%%(diary-block 7 07 2018 7 07 2018) 09:00 wc: 7qfRusia - 8qfCrocia (samara){4}
%%(diary-block 7 07 2018 7 07 2018) 13:00 wc: 3qfSuecia - 4qfInglaterra
(sochi){4}
** semifinales
:CATEGORY: 0.6semifi
%%(diary-block 7 10 2018 7 10 2018) 09:00 wc: 1sf - 2sf (san petersburgo){SF}
%%(diary-block 7 11 2018 7 11 2018) 09:00 wc: 3sf - 4sf (moscu){SF}
** la final
:CATEGORY: 0.6final
%%(diary-block 7 14 2018 7 14 2018) 09:00 wc: 1p - 2p (san petersburgo){F}
%%(diary-block 7 15 2018 7 15 2018) 09:00 wc: 1f - 2f (luzhniki, moscu){F}
--8<---cut here---end--->8---
the output(incorrect) is:
--8<---cut here---start->8---
Week-agenda (W28):
Monday 9 July 2018 W28
Diary: Martyrdom of the Báb
Tuesday10 July 2018
jl-diary.agendatest: 9:00.. wc: 1sf - 2sf (san petersburgo){SF}
Wednesday 11 July 2018
jl-diary.agendatest: 9:00.. wc: 3sf - 4sf (moscu){SF}
Thursday 12 July 2018
Friday 13 July 2018
Saturday 14 July 2018
jl-diary.agendatest: 9:00.. wc: 1p - 2p (san petersburgo){F}
Sunday 15 July 2018
jl-diary.agendatest: 9:00.. wc: 1f - 2f (luzhniki, moscu){F}
--8<---cut here---end--->8---
Regards
[O] bug#32068: 26.1; problem with org-agenda and categories
Hi Nicolas.
I still think this is a bug. Let me explain You why.
On my shared on this thread agenda file(jl_diary.agendatest.org).
There are several categories on the items for being showed on the
org-agenda. But org-mode chooses the last (among the categories) for
showing on the agenda. In my opinion if something is bad my my agenda
file (jl_diary.agendatest.org). It should be signaled when loading the
agenda, as the org-agenda does when something is wrong with my agenda
files, like the one I have shared (jl_diary.agendatest.org).
>> I share my agenda among several devices with different emacs versions
>> ("23.4" "25.1" "26.1|26.2|master")
>
> Note that recent Org, i.e., Org 9.0+ do not support Emacs 23 anymore.
I just use the org bundled with emacs with every of this versions. And
everything was smooth just until 26.1
Regards
[O] org-capture: how to unindent %i?
Hi,
I'm using the org-caputre with a org-capture-templates which I want to use
capture a region. "%i" will apply the indent. Is there a %-escapes which will
not indent the content but just make a proper level header?
(add-to-list 'org-capture-templates
'("R" "check indent" entry
(file+headline "~/.emacs.d/.notes/.notes.org" "Notes")
"* %?\n%i\n\n%l\n%:type %:url\n%F\nAdded: %U" :empty-lines-before 1
:empty-lines-after 1))
1. "Notes" is the level 1 header, and captured content will become level 2
header under it, which means a "*" will be added at the begining, like "**
[cursor]"
2. %i is the indedted initial content. If I capture a marked region, e.g., "a
marked region" in a buffer, it will be caputred as initial content, and it
becomes:
** [cursor]
[space]a marked region
A space is added automatically as indentation because a "*" added to the
header. What I need is just to make a level 2 header, but not add a space to
the content, e.g.:
** [cursor]a marked region
Best Regards,
Shuguang
Re: [O] Bug: Tables not aligning properly [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)]
This bug seems to be related to the presence of TAB characters in the table. Thanks, J.P.Pedroso
[O] bug#32068: 26.1; problem with org-agenda and categories
Hi Nicolas. > It doesn't look like a bug. The OP may have missed > `org-agenda-time-grid' variable. ¿What is OP?. If I do the same on emacs 25.1 I get the expected behaviour. So something has changed between 25.1 and 26.1. ¿What is the change needed? for having the same result on both emacs versions 25.1 and 26.1. Regards
[O] bug#32068: 26.1; problem with org-agenda and categories
Hi Nicolas.
> > ¿What is OP?.
>
> Original poster: you.
Thanks for the explanation.
> Emacs 25.1 and 26.1 do not ship the same Org. `org-agenda-time-grid'
> changed between the two releases. You may want to double-check this
> variable.
on 25.1
--8<---cut here---start->8---
This is a list of three items
--8<---cut here---end--->8---
On 26.1
--8<---cut here---start->8---
This is a list of four items
--8<---cut here---end--->8---
It is possible for me to have the previous behaviour. on 26.1
¿What change should i do?.
- on the var
- or on the data
I share my agenda among several devices with different emacs versions
("23.4" "25.1" "26.1|26.2|master")
Regards
[O] bug#32068: obsolescense of #+CATEGORY on org-mode 9.x
Hi Nicolas. > > ¿What would have been the way a user should discover this incompatibility > > or obsolescense of the "#+CATEGORY"?. > > I would suggest that user to read the releases notes, located in > ORG-NEWS files, in particular the "Incompatible changes" sections. > > This particular change was announced in Org 8.3. > > Also, this feature (multiple CATEGORY keywords) was strongly deprecated, > as pointed out in the old manual, since Org 5.14 (2008). I see. Something is missing on that comment "Use org-lint for a hint about how to modify your agenda file". /usr/share/emacs/26.1/etc/ORG-NEWS emacs 25.1 has org-version 8.2.10 Debian still have 24.5 as default emacs on debian strech. So this issue is going to arise again in the future. So just for the notice of future users. this: --8<---cut here---start->8--- #+CATEGORY: world cup --8<---cut here---end--->8--- should be changed to: --8<---cut here---start->8--- ** world cup (not showed on agenda view) :PROPERTIES: :CATEGORY: world cup :END: --8<---cut here---end--->8--- Regards
[O] bug#32068: obsolescense of #+CATEGORY on org-mode 9.x (was: bug#32068: 26.1; problem with org-agenda and categories)
Hi Nicolas. > The correct syntax is > > ** groups > :PROPERTIES: > :CATEGORY: 0.6groups > :END: it worked. It also worked on emacs 23.4 with org-mode-version 6.33x > See (info "(org) Property Syntax") Thanks. For your help on solving this incompatibility. I would like to add a word here "discoverability". ¿What would have been the way a user should discover this incompatibility or obsolescense of the "#+CATEGORY"?. Actually I have seen this behaviour for more than two months time. because sometimes I use master. So this behaviour has more than two months or merged. But I think this could lead to an opportunity for explaning how a user should react to this change. On my case It have not been easy to find the right way of solving this. Regards
[O] Bug: problem with org-agenda and categories [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
When evaluating the snippet below:
--8<---cut here---start->8---
(eval-after-load "org"
'(progn
overwrite some settings
(setq org-startup-folded nil ;unfolded
org-agenda-show-all-dates t
org-confirm-elisp-link-function nil ;; 4 the scratch call
org-agenda-include-diary t
org-agenda-include-all-todo t
)
(when (file-directory-p "~/docs/org/deft/")
(setq org-agenda-files (directory-files "~/docs/org/deft/" t
".*agendatest\.org$"))
)
(define-key org-mode-map (kbd "M-a") nil)
))
(require 'org)
(funcall 'org-agenda-list)
--8<---cut here---end--->8---
I am getting (which is not fine):
--8<---cut here---start->8---
Week-agenda (W27):
Monday 2 July 2018 W27
final: 9:00.. wc: 1eBrazil - 2fMexico (samara){16}
final: 13:00.. wc: 1gBelgica - 2hJapon (rostov){16}
Tuesday 3 July 2018
final: 9:00.. wc: 2eSuiza - 1fSuecia (san petersburgo){16}
final: 13:00.. wc: 2gInglaterra - 1hColombia (moscu){16}
Wednesday 4 July 2018
Diary: Independence Day
Thursday5 July 2018
Friday 6 July 2018
0:38.. now - - - - - - - - - - - - - - - - - - - - - - - - -
8:00..
final: 9:00.. wc: 1qfFrancia - 2qfUruguay (nizhny){4}
10:00..
12:00..
final: 13:00.. wc: 5qfBrasil - 6qfBelgica (kazán){4}
14:00..
16:00..
18:00..
20:00..
Saturday7 July 2018
final: 9:00.. wc: 7qfRusia - 8qfCrocia (samara){4}
final: 13:00.. wc: 3qfSuecia - 4qfInglaterra (sochi){4}
Sunday 8 July 2018
--8<---cut here---end--->8---
the output should be:
--8<---cut here---start->8---
Week-agenda (W27):
Monday 2 July 2018 W27
8: 9:00.. wc: 1eBrazil - 2fMexico (samara){16}
8: 13:00.. wc: 1gBelgica - 2hJapon (rostov){16}
Tuesday 3 July 2018
8: 9:00.. wc: 2eSuiza - 1fSuecia (san petersburgo){16}
8: 13:00.. wc: 2gInglaterra - 1hColombia (moscu){16}
Wednesday 4 July 2018
Diary: Independence Day
Thursday5 July 2018
Friday 6 July 2018
4: 9:00.. wc: 1qfFrancia - 2qfUruguay (nizhny){4}
4: 13:00.. wc: 5qfBrasil - 6qfBelgica (kazán){4}
Saturday7 July 2018
4: 9:00.. wc: 7qfRusia - 8qfCrocia (samara){4}
4: 13:00.. wc: 3qfSuecia - 4qfInglaterra (sochi){4}
Sunday 8 July 2018
--8<---cut here---end--->8---
the file ~/docs/org/deft/jl-diary.agendatest.org:
--8<---cut here---start->8---
* the world cup on my agenda
#+CATEGORY: groups
%%(diary-block 6 22 2018 6 22 2018) 7:00 wc: brazil - costa rica (sans
petersburgo){GE2}
%%(diary-block 6 22 2018 6 22 2018) 10:00 wc: nigeria - islanda
(volgogrado){GD2}
%%(diary-block 6 22 2018 6 22 2018) 13:00 wc: serbia - suiza (kaliningrado){GE2}
%%(diary-block 6 23 2018 6 23 2018) 07:00 wc: belgica - tunez (otkrytiye,
moscu){GG2}
%%(diary-block 6 23 2018 6 23 2018) 10:00 wc: mexico - korea (rostov){GF2}
%%(diary-block 6 23 2018 6 23 2018) 13:00 wc: alemania - suecia (sochi){GF2}
%%(diary-block 6 24 2018 6 24 2018) 07:00 wc: inglaterra - panama (nizhny){GG2}
%%(diary-block 6 24 2018 6 24 2018) 10:00 wc: japon - senegal
(ekaterimburgo){GH2}
%%(diary-block 6 24 2018 6 24 2018) 13:00 wc: colombia - polonia (kazán){GH2}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: uruguay - rusia (samara){GA3}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: egipto - arabia (volgogrado){GA3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: portugal - iran (saransk){GB3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: espanha - marruecos
(kaliningrado){GB3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: Dinamarca - francia (luzhniki,
moscu){GC3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: PERÙ - australia (sochi){GC3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: argentina - nigeria (san
petersburgo){GD3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: croacia - islandia (rostov){GD3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: corea - alemania (kazán){GF3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: mexico - suecia
(ekaterimburgo){GF3}
%%(diary-block 6 27 2018 6 27
[O] Bug: org-git-link to use SHA1 instead of master@{date} [9.1.13 (9.1.13-elpaplus @ /home/kvaneesh/.emacs.d/elpa/develop/org-plus-contrib-20180702/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. So my old org file when following git links is giving me error like "Log for master only goes back to 'x' date". Can we not refer a link via git:/filename::sha1:: ? Emacs : GNU Emacs 26.1 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.22.30) of 2018-06-26 Package: Org mode version 9.1.13 (9.1.13-elpaplus @ /home/kvaneesh/.emacs.d/elpa/develop/org-plus-contrib-20180702/)
[O] Bug: Tables not aligning properly [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Since some versions ago, org-mode stopped aligning tables properly.
This has been commented in StackExchange:
https://emacs.stackexchange.com/questions/37828/org-mode-doesnt-align-column-bars-properly
Sincerely,
João Pedro Pedroso
--
Emacs : GNU Emacs 26.1 (build 1, x86_64-apple-darwin17.6.0, Carbon Version 158
AppKit 1561.4)
of 2018-06-11
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)
current state:
==
(setq
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-timer-default-timer 25
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-agenda-files '("~/private/GTD/work.org" "~/private/GTD/gtd.org"
"~/private/GTD/home.org")
org-modules '(org-timer org-w3m org-bbdb org-bibtex org-docview org-gnus
org-info org-irc org-mhe org-rmail)
org-mode-hook '((lambda nil (flyspell-mode) (visual-line-mode))
#[0 "\300\301\302\303\304$\207" [add-hook
change-major-mode-hook org-show-block-all append local] 5]
#[0 "\300\301\302\303\304$\207" [add-hook
change-major-mode-hook org-babel-show-result-all append local] 5]
org-babel-result-hide-spec org-babel-hide-all-hashes)
org-archive-hook '(org-attach-archive-delete-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn
ENTRY)"]
org-babel-pre-tangle-hook '(save-buffer)
org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-log-done t
org-occur-hook '(org-first-headline-recenter)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-support-shift-select 'always
org-speed-command-hook '(org-speed-command-activate
org-babel-speed-command-activate)
org-replace-disputed-keys t
org-return-follows-link t
org-clock-in-hook '((lambda nil (if (not org-timer-current-timer)
(org-timer-set-timer (quote (16))
org-confirm-shell-link-function 'yes-or-no-p
org-link-parameters '(("id" :follow org-id-open) ("rmail" :follow
org-rmail-open :store org-rmail-store-link)
("mhe" :follow org-mhe-open :store org-mhe-store-link)
("irc" :follow org-irc-visit :store org-irc-store-link)
("info" :follow org-info-open :export org-info-export
:store org-info-store-link)
("gnus" :follow org-gnus-open :store org-gnus-store-link)
("docview" :follow org-docview-open :export
org-docview-export :store org-docview-store-link)
("bibtex" :follow org-bibtex-open :store
org-bibtex-store-link)
("bbdb" :follow org-bbdb-open :export org-bbdb-export
:complete org-bbdb-complete-link :store
org-bbdb-store-link)
("w3m" :store org-w3m-store-link) ("file+sys")
("file+emacs") ("doi" :follow org--open-doi-link)
("elisp" :follow org--open-elisp-link) ("file" :complete
org-file-complete-link)
("ftp" :follow (lambda (path) (browse-url (concat "ftp:"
path ("help" :follow org--open-help-link)
("http" :follow (lambda (path) (browse-url (concat
"http:" path
("https" :follow (lambda (path) (browse-url (concat
"https:" path
("mailto" :follow (lambda (path) (browse-url (concat
"mailto:; path
("news" :follow (lambda (path) (browse-url (concat
"news:; path
("shell" :follow org--open-shell-link))
org-image-actual-width '(400)
org-agenda-custom-commands '(("w" todo "WAITING" nil) ("n" todo "NEXT" nil)
("d" "Agenda + Next Actions" ((agenda) (todo
"NEXT"
org-directory "~/private/ORG"
org-default-notes-file "~/private/ORG/notes.org"
org-list-allow-alphabetical t
)
[O] bug#32068: 26.1; problem with org-agenda and categories
Hi Eli. > > I am getting (which is not fine): > > Did you report this to the Org developers? If so, and if they said > this is a core Emacs bug, could you please point us to the relevant > discussions with Org developers? I have just done with org-submit-bug-report Thanks
