Re: exporting to PDF multi-lingual document
Hi. Stefan. > "Stefan" == Stefan Nobis writes: [...] Stefan> That's quite strange. I just re-tested with emacs -Q (Emacs 28.2 with integrated Org Stefan> 9.5.5). It generates the following tex file: [...] Stefan> Maybe there are some other configurations on the Emacs or LaTeX side on your system that Stefan> changes some of the defaults? I tested your tex file with lualatex from command line, and It gave an error about the font lmroman10-regular. So after installing 'otf-latin-modern' package. The pdf rendered with all the paragraphs. Thanks. Best Regards ps: lualatex is really slow compared with pdflatex. But It works which is the important part
Re: exporting to PDF multi-lingual document
Hi. Stefan. >>>>> "Stefan" == Stefan Nobis writes: Stefan> Hi. I got curious and it seems if you are willing to use lualatex (which is, I think, Stefan> currently the most actively developed engine and nowadays a really good choice), the Stefan> following solution should work: [...] I have tried the snippet. But It shows just Japanese and the other paragraphs are not present on the PDF. Best Regards Andrés Ramírez
Re: exporting to PDF multi-lingual document
Hi. Ihor.
>>>>> "Ihor" == Ihor Radchenko writes:
[...]
Ihor> We discussed a similar issue previously in
Ihor> https://list.orgmode.org/orgmode/87h6z7jq4o.fsf@localhost/
I have dowloaded de whole thread. And I got something that shows
'quotation marks' in place of Japanese characteres.
I think the problem is the font (probably a different font is
needed). So let me know If You know any hints:
--8<---cut here---start->8---
#+TITLE: Doc multi-lingual
#+options: author:nil email:nil toc:nil num:nil date:nil
#+LATEX_COMPILER: lualatex
#+LANGUAGE: jp
#+LaTeX_Header: \usepackage[AUTO]{polyglossia}
#+LaTeX_Header: \usepackage{fontspec}
#+LaTeX_Header: \setmainfont{FreeSerif}
* Español
Hola
* English
Hi
* French
Ceci c'est en Français
* Japanese
ダウンロード
--8<---cut here---end------->8---
Best Regards
Andrés Ramírez
Re: exporting to PDF multi-lingual document
Hi. Arne.
>>>>> "Arne" == Arne Babenhauserheide writes:
[...]
Arne> I think you have to solve this on the LaTeX-side: including packages
that support the
Arne> required unicode.
[...]
Thanks. That helped. It ended like this:
--8<---cut here---start->8---
#+TITLE: Doc multi-lingual
#+options: author:nil email:nil toc:nil num:nil date:nil
#+LATEX_HEADER: \usepackage{CJKutf8}
* Español
Hola
* English
Hi
* French
Ceci c'est en Français
* Japanese
@@latex:\begin{CJK}{UTF8}{min}@@
ダウンロード
@@latex:\end{CJK}@@
--8<---cut here---end------->8---
Best Regards
Andrés Ramírez
exporting to PDF multi-lingual document
Hi.
When exporting this document the Japanese characters do not appear in
the output.
--8<---cut here---start->8---
#+TITLE: Doc multi-lingual
#+options: author:nil email:nil toc:nil num:nil
#+LATEX_HEADER: \usepackage[french,japanese]{babel}
#+LaTeX_HEADER: \pagenumbering{gobble}
* Español
Hola
* English
Hi
* French and Japanese {JPN characters does not appear when rendering the
PDF}
Ceci c'est en Français
ダウンロード
Ceci c'est en Français
--8<---cut here---end--->8---
Could You address me to the proper sintax for the japanese characters to
appear in the output?.
Best Regards
Andrés Ramírez
Re: how to remove parentheses from the output of a source code block
Hi. Greg. > "Greg" == Greg Minshall writes: Greg> Andrés, this is maybe more of an e-lisp question, or, at least, here's more of an e-lisp Greg> answer. if you have the useful =s= package [1] installed, then will using =s-join= give Greg> you what you want? [...] Yest that elisp snippet help me. And It gave me what I was looking for. I just did: s/(s-join " " sqlcode)/(with-temp-buffer (insert (format "%s" sqlcode)) (delete-rectangle (point-min) (point-max)) (buffer-string))/ Best Regards
how to remove parentheses from the output of a source code block
Hi.
I have this file:
--8<---cut here---start->8---
* labels table
** work on this file then move the output to the required buffers
#+name: source-in-table
| ID | MACRO_SRC_CODE_HEADER | LANGUAGE1_HEADER | LANGUAGE2_HEADER |
|+---+--+--|
| 1 | LABEL_YES | Si | Yes |
| 2 | LABEL_NO | No | No |
** generate sql
#+BEGIN_SRC emacs-lisp :var table=source-in-table :results value raw
(let ((sqlcode (mapcar (lambda (row)
(concat "INSERT or ignore INTO labels_catalog (id,
macro, language1, language2) VALUES ("
(number-to-string (nth 0 row)) ", '" (nth 1
row) "', '" (nth 2 row) "', '"
(nth 3 row) "');\n")
) table)))
sqlcode)
#+END_SRC
--8<---cut here---end--->8---
The above file generates this output:
--8<---cut here---start->8---
#+RESULTS:
(INSERT or ignore INTO labels_catalog (id, macro, language1, language2) VALUES
(1, 'LABEL_YES', 'Si', 'Yes');
INSERT or ignore INTO labels_catalog (id, macro, language1, language2) VALUES
(2, 'LABEL_NO', 'No', 'No');
)
--8<---cut here---end--->8---
How could be removed the parentheses from the output?
Best Regards
Re: on picking diary-style timestamps or normal timestamps when adding agenda entries
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
[...]
Ihor> Not at all. You can as well do
--8<---cut here---start->8---
* PE
:PROPERTIES:
:CATEGORY: da.santi
:END:
** <2022-09-24 Sat 9:00-11:00> etiro.espiritual {collaborator.family} :DAVID:
** <2022-09-27 Tue> Another entry to be displayed in agenda. It inherits parent
category
--8<---cut here---end--->8---
That one looks promising. Could I omit the day-on-letters (three
letters) before the closing bracket?.
I remember there was a keybinding for picking the day from calendar. But I
noticed killing and yanking was quicker than using the calendar. I am a
viper-mode user. killing and yanking is just yyp.
Ihor> Note org-refile command. See "9.1 Refile and Copy" section of Org
manual.
Last time I tried org-refile I did not stick on my workflow, perhaps I
should try again.
Best Regards
Re: on picking diary-style timestamps or normal timestamps when adding agenda entries (was: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/s
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
[...]
--8<---cut here---start->8---
** PE etiro.espiritual {collaborator.family} :DAVID:
:PROPERTIES:
:CATEGORY: da.santi
:END:
<2022-09-24 Sat 9:00-11:00>
--8<---cut here---end--->8---
That above is an equivalent example using normal timestamps.
On my use case. I have seven categories on this file
for example: chores, work, home, family. I add entries for all this
categories every week (I just try to add entries once a week if possible
on the weekends).
In case I pick normal timestamps I would need to yank 5 lines and edit 2
lines one at the top and other at the bottom of the yanked region. On my
current worflow using diary-style timestamps I just need to add a line
at the bottom and edit that line.
The advantage of using normal timestamps is I could append the line at
the end of the file. On diary-style timestamps I should do occur for the
category and after it C-c C-n for appending at the end of the current subtree.
For my use case I should keep working with diary-style timestamps but
YMMV.
Thanks guys for the help, the tips and the explanation.
Best Regards
on picking diary-style timestamps or normal timestamps when adding agenda entries (was: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
[...]
Ihor> What about
--8<---cut here---start->8---
** PE :DAVID:
:PROPERTIES:
:CATEGORY: da.santi
:END:
<2022-10-01 Sat>
--8<---cut here---end--->8---
The only missing part from the given example was the message. The given
example was:
, [ ]
| ** PE :DAVID:
| :PROPERTIES:
| :CATEGORY: da.santi
| :END:
| %%(diary-block 10 1 2022 10 1 2022) 9:00-11:00 retiro.espiritual
{collaborator.family}
`
which one would the place for 'retiro.espiritual {collaborator.family}'?
Ihor> The long file name you are seeing in agenda is dictated by category in
Ihor> org-agenda-prefix-format:
Ihor>%c the category of the item, "Diary" for entries from the
diary, or as given by the
Ihor> CATEGORY keyword or derived from the file name
I started using org-mode on emacs-23. So I remember from that year until
now. Once I needed to reformat my agenda files (because CATEGORY was
needed for trying to mimic my previous behaviour of org-agenda). After
settle on that I have not examined that part of my workflow anymore. But
this is emacs 'trying to shave things of our workflow and improve our
daily tasks routines'. I am reviewing it now with You guys.
Best Regards
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Eric.
My comments below.
> "Fraga," == Fraga, Eric writes:
[...]
Fraga,> This would be simply be something along these lines:
--8<---cut here---start->8---
* retiro espiritual {collaborator.family}
<2022-08-01 Mon 09:00-11:00>
--8<---cut here---end--->8---
Fraga,> You only need to use diary block entries if you want to block out a
specific range of
Fraga,> dates but even then it is often easier to use multiple time stamps
instead.
I see. Thanks for the clarification. Then I think I saw it in the past. But
when You do it. the agenda
filename appears on the agenda buffer (the agenda filename is large on my case)
. So I prefer
give to the entry a short category.
This is my use case:
--8<---cut here---start->8---
** PE :DAVID:
:PROPERTIES:
:CATEGORY: da.santi
:END:
%%(diary-block 10 1 2022 10 1 2022) 9:00-11:00 retiro.espiritual
{collaborator.family}
--8<---cut here---end--->8---
so. the short label 'da.santi' is what appears on my agenda.
Best Regards
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
[...]
Ihor> You appear to have a large number of diary-style timestamps. This is
not common. Normal
Ihor> timestamps are generally much faster because we can construct a
matching regexp based on
Ihor> current agenda date instead of checking every single sexp.
I started using the org-agenda several years ago. When I add a new entry which
is
probably weekly. I just kill the previous line and yank and update the
new one on my agenda files. This is a tipical example of one of my
entries.
--8<---cut here---start->8---
%%(diary-block 8 1 2022 8 1 2022) 9:00-11:00 retiro.espiritual
{collaborator.family}
--8<---cut here---end--->8---
Pardon my ignorance. How could You translate it to a normal timestamp?.
Ihor> Having said that, I now have an idea how to avoid the overheads in
such scenarios. Just
Ihor> pushed the change upstream. Can you check? It should bypass most of
the slow checks in
Ihor> your use case.
Neat. Now it took 25s. It is really very near to emacs-27
performance. Congrats.
[...]
Ihor> We have a whole dedicated section in the manual: "A.8 Speeding Up
Your Agendas". Agenda
Ihor> performance is a well-known problem since years back. The coming
release (the current
Ihor> main branch) will have major improvements to performance in this
area, although I have
Ihor> mostly optimized it for timestamp-based agendas and todo agendas
before your report.
Thanks for the work.
Best Regards
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Ihor. > "Ihor" == Ihor Radchenko writes: [...] Ihor> Now, I see what went wrong. Just pushed a patch that should reduce the time taken by Ihor> `org-diary-sexp-entry' during rebuild. Thanks. Ihor> Can you update and try the profiling again? Done. <> Ihor> (If this last change works, I am out of ideas about easy ways to improve performance Ihor> further. The only one is a significant change in org-element-at-point internals, but it Ihor> will need to be tested carefully, and I do not plan to upstream it before the next Org Ihor> release). Do not worry. You have done more than enough. I have notice this delay from a long time. But nobody else reported it, which is weird. I am going to wait until emacs-29, for those changes. Is there any workaround or recomendacion for the emacs-28 users with the built-in org mode?. Or that should be mentioned on PROBLEMS? Best Regards
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Ihor. > "Ihor" == Ihor Radchenko writes: [...] Ihor> Thanks! Ihor> Something appears to be off: Ihor> 767 8% - org-diary-sexp-entry 407 4% + eval Ihor> I added caching of `org-diary-sexp-entry' results in Ihor> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4075662c298da7fa7e2ba19e0b8b36c58852cc0f Ihor> This caching should make `org-diary-sexp-entry' much faster when you rebuild the Ihor> agenda. But it is not the case in the profiler - `eval' branch of the code should be Ihor> executed when no cached result is found. Ihor> Could you please confirm that you are using the latest development version of Org? A few seconds ago. I have done git pull; make. This is my latest file <> Best Regards
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Ihor. > "Ihor" == Ihor Radchenko writes: Ihor> cpu+mem report should generate two reports: one for cpu time and one for memory. I meant Ihor> you to save both (there are two buffers). Sorry for not being clear. The two files on an archive <> Best Regards
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Ihor. > "Ihor" == Ihor Radchenko writes: [...] Ihor> Makes sense. If you want to squeeze maximum out of Emacs startup and do not update Ihor> frequently, you may look into Ihor> https://archive.casouri.cat/note/2020/painless-transition-to-portable-dumper/index.html Yes. That could be an alternative. on the emacs-28 I can not get 2 weeks of uptime because of this error. bug#57504 On the past on emacs-27 I got almost two months of uptime. About the cpu+mem profiler-report. [profiler-profile "28.1" memory #s(hash-table size 487 test equal rehash-size 1.5 rehash-threshold 0.8125 data ([timer-relative-time run-at-time execute-extended-command funcall-interactively call-interactively command-execute nil nil nil nil nil nil nil nil nil nil] 88 [timer--time-setter timer-set-time run-at-time execute-extended-command funcall-interactively call-interactively command-execute nil nil nil nil nil nil nil nil nil] 40 [timer--time-less-p timer--activate timer-activate run-at-time execute-extended-command funcall-interactively call-interactively command-execute nil nil nil nil nil nil nil nil] 128 [timer--time-setter timer-set-idle-time run-with-idle-timer eldoc-schedule-timer nil nil nil nil nil nil nil nil nil nil nil nil] 40 [timer--time-less-p timer--activate timer-activate-when-idle run-with-idle-timer eldoc-schedule-timer nil nil nil nil nil nil nil nil nil nil nil] 72 [nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil] 23892 [timer--time-less-p timer--activate timer-activate-when-idle timer-event-handler nil nil nil nil nil nil nil nil nil nil nil nil] 108 [execute-extended-command--shorter-1 execute-extended-command--shorter-1 execute-extended-command--shorter "#" apply timer-event-handler nil nil nil nil nil nil nil nil nil nil] 576 [completion-pcm--string->pattern completion-pcm--find-all-completions completion-pcm-try-completion "#" completion--some completion--nth-completion completion-try-completion execute-extended-command--shorter "#" apply timer-event-handler nil nil nil nil nil] 512 [completion-pcm--pattern->regex completion-pcm--all-completions completion-pcm--find-all-completions completion-pcm-try-completion "#" completion--some completion--nth-completion completion-try-completion execute-extended-command--shorter "#" apply timer-event-handler nil nil nil nil] 576 [completion-pcm--all-completions completion-pcm--find-all-completions completion-pcm-try-completion "#" completion--some completion--nth-completion completion-try-completion execute-extended-command--shorter "#" apply timer-event-handler nil nil nil nil nil] 1088 [completion-pcm--merge-completions completion-pcm--merge-try completion-pcm-try-completion "#" completion--some completion--nth-completion completion-try-completion execute-extended-command--shorter "#" apply timer-event-handler nil nil nil nil nil] 512 [completion-pcm--merge-try completion-pcm-try-completion "#" completion--some completion--nth-completion completion-try-completion execute-extended-command--shorter "#" apply timer-event-handler nil nil nil nil nil nil] 8188 [completing-read-default completing-read read-extended-command byte-code call-interactively command-execute nil nil nil nil nil nil nil nil nil nil] 20974 [timer-relative-time run-at-time undo-auto--boundary-ensure-timer undo-auto--undoable-change read-from-minibuffer completing-read-default completing-read read-extended-command byte-code call-interactively command-execute nil nil nil nil nil] 64 [timer--time-setter timer-set-time run-at-time undo-auto--boundary-ensure-timer undo-auto--undoable-change read-from-minibuffer completing-read-default completing-read read-extended-command byte-code call-interactively command-execute nil nil nil nil] 40 [timer--time-less-p timer--activate timer-activate run-at-time undo-auto--boundary-ensure-timer undo-auto--undoable-change read-from-minibuffer completing-read-default completing-read read-extended-command byte-code call-interactively command-execute nil nil nil] 48 [viper-minibuffer-post-command-hook read-from-minibuffer completing-read-default completing-read read-extended-command byte-code call-interactively command-execute nil nil nil nil nil nil nil nil] 760 [read-from-minibuffer completing-read-default completing-read read-extended-command byte-code call-interactively command-execute nil nil nil nil nil nil nil nil nil] 24594 [timer--time-less-p timer--activate timer-activate-when-idle timer-event-handler read-from-minibuffer completing-read-default completing-read read-extended-command byte-code call-interactively command-execute nil nil nil nil nil] 1296 [call-interactively command-execute read-from-minibuffer completing-read-default completing-read read-extended-command byte-code call-interactively command-execute nil nil nil nil nil nil nil] 152 ["#" "#" apply "#" apply self-insert-command funcall-interactively call-interactively command-execute
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Ihor > "Ihor" == Ihor Radchenko writes: [...] Ihor> Can you: 1. Load your agenda 2. Start 'cpu+mem profiler 3. Rebuild the agenda 4. Share the Ihor> obtained 'cpu _and_ 'mem reports I found an issue. --8<---cut here---start->8--- void-function org-looking-at --8<---cut here---end--->8--- Ihor> BTW, is your Emacs 28 using native-comp? >> >> NO. But on this lower-end machine there is no too much difference. Ihor> native-comp is improving things proportionally. It should actually have higher impact on Ihor> lower-end machine. I recommend native-comp unless you update frequently (and hence need to Ihor> re-compile using native-comp often). On my case. My distro which is archlinux-arm aka alarm for 32bits does not provide the compiled package libgccjit. So compiling it takes several hours on this little machine. cross-compiling it takes almost 1h, but preparing the machine for cross-compilation takes time also. So my conclusion is 'it does not worth the hassle'. Best Regards
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Ihor. > "Ihor" == Ihor Radchenko writes: [...] Ihor> Now, can you execute the following and let me know if the performance is back to Ihor> satisfactory? [...] I have tested your suggested changes. emacs28 with bundled org have recovered and it is a little bit quicker than emacs27 (around 17s). emacs28 with org 9.6 took 44 seconds. So on 9.6 performance is not satisfactory yet. second observation: on emacs28+bundled-org this very detailed line is shown: --8<---cut here---start->8--- bbdb: [[bbdb:erlinda massco][erlinda massco's 49th custom anniversary]] --8<---cut here---end--->8--- But. on emacs28+org9.6 this short detailed line is showed: --8<---cut here---start->8--- bbdb: custom --8<---cut here---end--->8--- Could this behaviour be restored on latest development?. Best Regards
Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi. Ihor. > "Ihor" == Ihor Radchenko writes: [...] Ihor> The slowdown is possible as a side-effect of some bugfixes. However, the newest Ihor> development version of Org should not have these performance issues. I have just tried 9.6. org-agenda-list generation time was 1m20s. More than one minute more than emacs-27. Best Regards ps: JIC org-9.6snapshot0.20220909.131646.tar
[BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Hi.
org-agenda-list generation time takes too much time compared with the
same setup with emacs27.
This is org-agenda-list output from 28. (takes aproximately 4m21s)
--8<---cut here---start->8---
10 days-agenda (W35-W37):
Sunday 4 September 2022
misc:8:00.. Glorious
:MISCELLANEOUS::
bd: 9:00-10:00 Carlita
:BIRTHDAY:
bd: 9:00-10:00 Regina 44,
:BIRTHDAY:
Monday 5 September 2022 W36
misc:8:00.. Joyful
:MISCELLANEOUS::
bd: 12:01.. Artesco 2,
:BIRTHDAY:
Diary: Labor Day
Tuesday 6 September 2022
misc:8:00.. Sorrowful
:MISCELLANEOUS::
Wednesday 7 September 2022
misc:8:00.. Glorious
:MISCELLANEOUS::
8:00..
10:00..
12:00..
14:00..
16:00..
16:45.. now - - - - - - - - - - - - - - - - - - - - - - - - -
18:00..
20:00..
refile.agenda:Sched.4167x: NEXT Weekly Review [0/8] {do not forget to touch
type}
Thursday8 September 2022
jl-diary.agenda: 7:30.. consagracion a la virgen (16: JL, DA)
jl-diary.agenda: 7:30.. nest cmary anniversary
misc:8:00.. Luminous
:MISCELLANEOUS::
event: 8:00-8:01 daewoo matiz revision tecnica
bd: 15:00-16:00 Jean Luc baptism; buy a Cake go to Church Location:
Xto Salvador :BIRTHDAY:
daaron.cmary.patriot:nidocm 30
Friday 9 September 2022
misc:8:00.. Sorrowful
:MISCELLANEOUS::
jl.santi: vale chipoco 16|loma umbrosa Mz E Lt
20|7247764|jose_antonio,cecilia|ceciespinoza at g :JEANLUC:
Saturday 10 September 2022
family.yengle: 5:00.. running time
:FAMILY::
misc:8:00.. Joyful
:MISCELLANEOUS::
Sunday 11 September 2022
misc:8:00.. Glorious
:MISCELLANEOUS::
Monday 12 September 2022 W37
misc:8:00.. Joyful
:MISCELLANEOUS::
refile.agenda:Scheduled: NEXT Weekly Review [0/8] {do not forget to touch
type}
bbdb: [[bbdb:erlinda massco][erlinda massco's 49th custom anniversary]]
Tuesday13 September 2022
misc:8:00.. Sorrowful
:MISCELLANEOUS::
bd: 10:00-11:00 tio Felipe Location: Tumbes
:BIRTHDAY:
pass.out: Manuela grand mother
--8<---cut here---end--->8---
This is org-agenda-list output from 27. (takes 15s)
--8<---cut here---start->8---
10 days-agenda (W35-W37):
Sunday 4 September 2022
misc:8:00.. Glorious
:MISCELLANEOUS::
bd: 9:00-10:00 Carlita
:BIRTHDAY:
bd: 9:00-10:00 Regina 44,
:BIRTHDAY:
Monday 5 September 2022 W36
misc:8:00.. Joyful
:MISCELLANEOUS::
bd: 12:01.. Artesco 2,
:BIRTHDAY:
Diary: Labor Day
Tuesday 6 September 2022
misc:8:00.. Sorrowful
:MISCELLANEOUS::
Wednesday 7 September 2022
misc:8:00.. Glorious
:MISCELLANEOUS::
8:00..
10:00..
12:00..
14:00..
16:00..
16:53.. now - - - - - - - - - - - - - - - - - - - - - - - - -
18:00..
20:00..
refile.agenda:Sched.4167x: NEXT Weekly Review [0/8] {do not forget to touch
type}
Thursday8 September 2022
jl-diary.agenda: 7:30.. consagracion a la virgen (16: JL, DA)
jl-diary.agenda:
Re: Custom beamer blocks for pros and cons list
Hi Ihor.
> "Ihor" == Ihor Radchenko writes:
Ihor> Axel Kielhorn writes:
>> #+begin_problock Pros @@latex:{Probloc}@@ - New. - Other Pro. -
Additional Pro.
>> #+end_problock
Ihor> Also, there is #+attr_latex:
Ihor> #+attr_latex: :options {Problock} #+begin_problock #+end_problock
Right. It works too.
Thanks
Re: Custom beamer blocks for pros and cons list
Hi. Axel.
> "Axel" == Axel Kielhorn writes:
[...]
>> #+LaTeX_Header: \newenvironment<>{problock}[1]{%
Axel> The =problock= environment takes 1 argument, but you supply none.
Thanks. That part would have been very difficult to realize for a
latex-beginner.
Axel> You can supply an argument #+begin_problock @@latex:{Probloc}@@
Tested. And works.
Axel> This will be ignored for non-LaTeX exporters.
Axel> But even here you have to block environments, the outer environment
generated by =***
Axel> Pros= and the inner problock environment.
Axel> You can get rid of the outer block environment by removing
Axel>:BEAMER_env: block
The other option could be pasing empty as parameter.
Thanks for the help.
Best Regards
Custom beamer blocks for pros and cons list
Hi.
I am adapting this example:
--8<---cut here---start->8---
https://tex.stackexchange.com/questions/28760/custom-beamer-blocks-for-pros-and-cons
--8<---cut here---end--->8---
This is my file:
--8<---cut here---start->8---
#+AUTHOR: Me
#+EMAIL:
#+DATE: 2022
#+DESCRIPTION:
#+KEYWORDS:
#+OPTIONS: toc:nil
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+startup: beamer
#+LaTeX_CLASS: beamer
#+LATEX_CLASS_OPTIONS: [bigger]
#+BEAMER_FRAME_LEVEL: 2
#+COLUMNS: %40ITEM %10BEAMER_env(Env) %9BEAMER_envargs(Env Args)
%4BEAMER_col(Col) %10BEAMER_extra(Extra)
#+LaTeX_Header: \beamertemplatenavigationsymbolsempty
#+LaTeX_Header: \newenvironment<>{problock}[1]{%
#+LaTeX_Header: \begin{actionenv}#2%
#+LaTeX_Header: \def\insertblocktitle{#1}%
#+LaTeX_Header: \par%
#+LaTeX_Header: \mode{%
#+LaTeX_Header: \setbeamercolor{block
title}{fg=white,bg=orange!20!black}
#+LaTeX_Header:\setbeamercolor{block body}{fg=black,bg=olive!50}
#+LaTeX_Header:\setbeamercolor{itemize item}{fg=orange!20!black}
#+LaTeX_Header:\setbeamertemplate{itemize item}[triangle]
#+LaTeX_Header: }%
#+LaTeX_Header: \usebeamertemplate{block begin}}
#+LaTeX_Header: {\par\usebeamertemplate{block end}\end{actionenv}}
** Comparisson
:PROPERTIES:
:BEAMER_envargs: [t]
:END:
*** Pros :BMCOL:B_block:
:PROPERTIES:
:BEAMER_col: 0.45
:BEAMER_env: block
:END:
#+begin_problock
- New.
- Other Pro.
- Additional Pro.
#+end_problock
*** Cons :BMCOL:B_block:
:PROPERTIES:
:BEAMER_col: 0.4
:BEAMER_env: block
:BEAMER_envargs: <2->
:END:
- Need Testing.
- Other Con.
- More Con.
--8<---cut here---end--->8---
I am getting an error and PDF is not generated.
Thanks.
Re: simple request letter - help
Hi. Juan. Mi comments below.
[...]
Juan> ID: #+end_signature
Adding that part:
--8<---cut here---start->8---
#+OPTIONS: date:nil author:nil timestamp:nil e:nil creator:nil toc:nil num:nil
title:nil
#+LaTeX_Header: \parindent=0em\parskip=\bigskipamount
#+LaTeX_Header:
\newenvironment{signature}{\vspace{2cm}\raggedright\makebox[1.5in]{\hrulefill}\newline}{\par}
*
Me John Doe with ID number request to install me the water service
I am sharing the payment receipt for the service in an attachment
Sincerely.
#+begin_signature
John Doe \\
ID:
#+end_signature
--8<---cut here---end--->8---
Thanks for your help
Best Regards
Re: simple request letter - help
Hi. Juan.
It ended this way:
--8<---cut here---start->8---
#+OPTIONS: date:nil author:nil timestamp:nil e:nil creator:nil toc:nil num:nil
title:nil
#+LaTeX_Header: \parindent=0em\parskip=\bigskipamount
*
Me John Doe with ID number request to install me the water service
I am sharing the payment receipt for the service in an attachment
Sincerely.
#+latex: \vspace{2cm}
#+BEGIN_EXPORT latex
\makebox[1.5in]{\hrulefill} \hspace {1.0in} \\
John Doe \\
ID:
#+END_EXPORT
--8<---cut here---end--->8---
Best Regards
[...]
Me> Right. It is giving me an error I have NOT noticed it because the pdf
is being generated.
Re: simple request letter - help
Hi. Juan.
My comments below.
> "Juan" == Juan Manuel Macías writes:
[...]
Juan> section is not indented. This is what is happening :):
That is good to know.
Juan> section no indent - indent -- indent --
[...]
Juan> is enough that you add this:
Juan> #+LaTeX_Header: \parindent=0em\parskip=\bigskipamount
It worked for most part of the document. But I Think I need the double
of space before the signature.
[...]
Juan> On the other hand, this code at the end does not give you an error?
Juan> \makebox[1.5in]{\hrulefill} \hspace {1.0in} \\ & John Doe \\ & ID:
\\
Right. It is giving me an error I have NOT noticed it because the pdf is
being generated.
Best Regards
Re: simple request letter - help
Hi. Juan.
My comments below.
>>>>> "Juan" == Juan Manuel Macías writes:
Juan> Can you please copy the contents of your .tex file here: `M-x
org-export-disptatch l l'?
--8<---cut here---start->8---
% Intended LaTeX compiler: pdflatex
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{wrapfig}
\usepackage{rotating}
\usepackage[normalem]{ulem}
\usepackage{amsmath}
\usepackage{amssymb}
\usepackage{capt-of}
\usepackage{hyperref}
\date{}
\title{}
\hypersetup{
pdfauthor={Andrés Ramírez},
pdftitle={},
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs 28.1 (Org mode 9.5.2)},
pdflang={English}}
\begin{document}
\section*{}
\label{sec:orgbc8783b}
Me John Doe with ID number request to install me the water service
\ldots{}.
\bigskip
I am sharing the payment receipt for the service in an attachment
\bigskip
Sincerely.
\makebox[1.5in]{\hrulefill} \hspace {1.0in} \\
& John Doe \\
& ID: \\
\end{document}
--8<---cut here---end--->8---
Best Regards
simple request letter - help
Hi.
I am trying to do a simple request letter. This is the content of the
file.
--8<---cut here---start->8---
#+OPTIONS: date:nil author:nil timestamp:nil e:nil creator:nil toc:nil num:nil
title:nil
*
Me John Doe with ID number request to install me the water service
#+latex: \bigskip
I am sharing the payment receipt for the service in an attachment
#+latex: \bigskip
Sincerely.
#+BEGIN_EXPORT latex
\makebox[1.5in]{\hrulefill} \hspace {1.0in} \\
& John Doe \\
& ID: \\
#+END_EXPORT
--8<---cut here---end--->8---
When I export the file M-x org-export-distpach l p
The second and third paragraph do nat have right alignment as the first
paragraph.
How Could I solve it?.
Best Regards
Re: printing org table landscape on complete page
Hi (Como estas). Juan. > "Juan" == Juan Manuel Macías writes: [...] Juan> #+ATTR_LaTeX: :float sideways :environment tabularx :width \textheigtht I have tried it (with M-x org-export-dispatch). This is the result: , [ ] | http://0x0.st/-Kgb.pdf ` It is centered. Also I got a second option: with this snippet and (M-x ps-print-buffer): --8<---cut here---start->8--- (setq ps-left-margin 0 ps-paper-type 'a4 ps-font-size 16.0 ps-print-header nil ps-landscape-mode t ps-number-of-columns 1 ps-printer-name "pdf") --8<---cut here---end--->8--- This is the result: , [ ] | http://0x0.st/-KgA.pdf ` The second option is going to be very useful when pdflatex is not available. But it is NOT so well centered as the first option. Thanks for your help. Best Regards
printing org table landscape on complete page
Hi. I want to print from emacs an org-table like this one: --8<---cut here---start->8--- |-+---+--+---+--+-| |DURATION | MONDAY| TUESDAY | WEDNESDAY | THURSDAY | FRIDAY | |-+---+--+---+--+-| | 08:30-09:30 | CyT | RELIGION | GERMAN| ENGLISH | ENGLISH | |-+---+--+---+--+-| | 09:50-10:50 | COMUNICAT | DPCC | COMUNICAT | COMUNIC | CyT | |-+---+--+---+--+-| | 11:10-12:10 | COMPUTERS | CyT | E.FISICA | ART | GERMAN | |-+---+--+---+--+-| | 12:30-13:30 | TUTORIA | MATH | MATH | CC.SS| MATH| --8<---cut here---end--->8--- on landscape on the content should enlarge to cover the full-page. Any ideas? Andrés Ramírez
Re: contact management in emacs
Hi. Eric. > "Eric" == Eric S Fraga writes: [...] Eric> How do you get these to appear? Or is the "could" a wish? This is my setup: --8<---cut here---start->8--- (setq org-agenda-files (directory-files "~/docs/org/deft/" t ".*agenda\.org$")) --8<---cut here---end--->8--- ~/docs/org/deft/bbdb-anniversary-trick.agenda.org: --8<---cut here---start->8--- * anniversary [isodate] :PROPERTIES: :CATEGORY: bbdb :END: %%(when (fboundp 'my/org-bbdb-anniversaries) (my/org-bbdb-anniversaries)) --8<---cut here---end--->8--- --8<---cut here---start->8--- (defun my/org-bbdb-anniversaries () "It does not work on emacs-23" (when (/= 23 emacs-major-version) (org-bbdb-anniversaries) ) ) --8<---cut here---end--->8--- the bbdb record should have the field anniversary: --8<---cut here---start->8--- anniversary: 1960-03-03 custom --8<---cut here---end--->8--- Best Regards
Re: contact management in emacs
Hi. Martin and Alan. >>>>> "Martin" == Martin Steffen writes: [...] Martin> Org is also bbdb-aware, insofar one can do those links: instead of [[file:][yyy]] Martin> one can use [[bbdb:somecriterion]]. bbdb anniversaries could also appear on agenda: --8<---cut here---start->8--- 10 days-agenda (W08-W09): Wednesday 24 February 2021 Thursday 25 February 2021 Friday 26 February 2021 Saturday 27 February 2021 Sunday 28 February 2021 Monday 1 March 2021 W09 Tuesday 2 March 2021 Wednesday 3 March 2021 bbdb: [[bbdb:Pedro ][Pedro 61st custom anniversary]] Thursday4 March 2021 Friday 5 March 2021 --8<---cut here-------end--->8--- Andrés Ramírez
Re: Bug: issue with babel and sqlite [9.3 (release_9.3 @ /usr/share/emacs/27.0.91/lisp/org/)]
Hi Bastien. Thanks for fixing this. > "Bastien" == Bastien writes: [...] Bastien> Can you instrument the `org-babel-read' function? I have done. But It has not failed with 27.1. Bastien> You can do this with C-h f org-babel-read RET and then C-u C-M-x on the function's Bastien> definition. Best Regards
Re: testing org-bbdb-anniversaries
Hi Nicolas. Nicolas> Sadly, yes. Like most diary-related stuff, it expects the Nicolas> `date' variable to be globally bound. Perhaps something about it on the help? --8<---cut here---start->8--- (defun org-bbdb-anniversaries () "Extract anniversaries from BBDB for display in the agenda In case of calling programatically. Like most diary-related stuff, it expects the `date' variable to be globally bound." (require 'bbdb) . ) --8<---cut here---end--->8--- Nicolas> Something like Nicolas> (let ((date '(2 29 2020))) (org-bbdb-anniversaries)) It helped. Thanks. BR
testing org-bbdb-anniversaries
Hi. Emacs 26.3, org 9.1.9 My bbdb anniversary entries are not being shown on my agenda. I would like to add warning on emacs startup when bbdb records are not being showed. I eval 'org-bbdb-anniversaries' that lead me to --8<---cut here---start->8--- Debugger entered--Lisp error: (void-variable date) (car date) (let* ((m (car date)) (d (nth 1 date)) (y (nth 2 date)) (annivs (gethash (list m d) org-bbdb-anniv-hash)) (text nil) rec recs) (if (and (= m 3) (= d 1) (not (null (gethash (list 2 29) org-bbdb-anniv-hash))) (not (calendar-leap-year-p y))) (progn (setq recs (gethash (list 2 29) org-bbdb-anniv-hash)) (while (setq rec (car-safe (prog1 recs (setq recs ... (setq annivs (cons rec annivs) (if annivs (progn (while (setq rec (car-safe (prog1 annivs (setq annivs ... (if rec (progn (let* (... ... ... ... ... ...) (org-add-props tmp nil ... name) (if text ... ...))) text) org-bbdb-anniversaries() eval((org-bbdb-anniversaries) nil) elisp--eval-last-sexp(nil) eval-last-sexp(nil) funcall-interactively(eval-last-sexp nil) call-interactively(eval-last-sexp nil nil) command-execute(eval-last-sexp) --8<---cut here---end--->8--- above is intended behaviour? I would like to to check an specific date on bbdb-records 2020-02-29 and that date should return me a result that would confirm me org-bbdb-anniversaries is loading my entries on agenda, otherwise a warning message should appear on emacs startup. Which is the right way of checking org-bbdb-anniversaries is loading my entries? BR
Re: [O] org-agenda list on other language than english
Hi Thomas. Thomas> Localised day and month names are taken from your (apparently Thomas> missing) calendar setup. Make sure that your startup file Thomas> setq's at least these two variables: Thomas> - calendar-month-name-array - calendar-day-name-array (starts Thomas> with $SUNDAY) Thomas> Also, it might be advisable to set calendar-date-style (to Thomas> 'european in my case). Thanks. That was what I was looking for. Best Regards
[O] org-agenda list on other language than english
Hi. Would it be possibe to render agenda in other language than English. Convert from this: --8<---cut here---start->8--- 10 days-agenda (W32-W33): Wednesday 7 August 2019 Thursday8 August 2019 Friday 9 August 2019 Saturday 10 August 2019 Sunday 11 August 2019 Monday 12 August 2019 W33 Tuesday13 August 2019 Wednesday 14 August 2019 Thursday 15 August 2019 Friday 16 August 2019 --8<---cut here---end--->8--- To this (Spanish): --8<---cut here---start->8--- 10 dias-agenda (W32-W33): Miercoles 7 Agosto 2019 Jueves 8 Agosto 2019 Viernes 9 Agosto 2019 Sabado 10 Agosto 2019 Domingo11 Agosto 2019 Lunes 12 Agosto 2019 W33 Martes 13 Agosto 2019 Miercoles 14 Agosto 2019 Jueves 15 Agosto 2019 Viernes16 Agosto 2019 --8<---cut here---end--->8--- If that is not implemented. Any suggestions where could I do the replacements?. BR
[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. > 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#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
