Re: [PATCH v2] Re: Bug in 9.5.3 org--file-default-apps

2022-05-28 Thread Max Nikulin
Ihor, Your patch may be an improvement, but it requires an additional fix, see below. However, in my opinion, it does not address original Craig's issue. The patch improves handling of *non-text* files requiring *external* viewers, while Craig complained that behavior for shell script is in

Re: # Comments export

2022-05-28 Thread Ihor Radchenko
Ypo writes: > I wanted to export my # comments so I could share my notes with more people, > using HTML export. I would export all of them. > > But, as it seems not possible, I think I will use footnotes. I liked # > comments more, because their face can be customized and because they are > ne

Re: # Comments export

2022-05-28 Thread Ypo
Hi, Timothy I wanted to export my # comments so I could share my notes with more people, using HTML export. I would export all of them. But, as it seems not possible, I think I will use footnotes. I liked # comments more, because their face can be customized and because they are nearer to the

Re: # Comments export

2022-05-28 Thread Samuel Wales
to op: do you mean to sometimes export comments and sometimes not? On 5/28/22, Timothy wrote: > Hi Ypo, > > Well, `#+begin_comment' is for content you /don’t/ want exported, but if you > want to > add a note to be included in exports, try `#+begin_note'. > > All the best, > Timothy > -- The K

Re: # Comments export

2022-05-28 Thread Timothy
Hi Ypo, Well, `#+begin_comment' is for content you /don’t/ want exported, but if you want to add a note to be included in exports, try `#+begin_note'. All the best, Timothy

Re: # Comments export

2022-05-28 Thread Ypo
Thanks, Timothy Do you mean blocks like #+BEGIN_COMMENT ? Does that kind of blocks already exist? https://i.ibb.co/xHJDgCR/Captura.jpg Ypo El 28/05/2022 a las 17:44, Timothy escribió: Hi Ypo, As I understand it, the whole point of comments is that they’re not exported. Perhaps you’re lo

Re: # Comments export

2022-05-28 Thread Timothy
Hi Ypo, As I understand it, the whole point of comments is that they’re not exported. Perhaps you’re looking for note blocks instead? All the best, Timothy

# Comments export

2022-05-28 Thread Ypo
Is it possible to export the (# comments)? I haven't seen that option in org export general customization. I am making some (# comments) to texts, and I would like to export them when I export the subtree to HTML. Best regards, Ypo

Re: [PATCH] Re: Change in `org-cycle-hook' breaks behavior

2022-05-28 Thread Tor Kringeland
Ihor Radchenko writes: > If you want all the drawers in all the children to be opened, you can > instead do the following: > > (let* ((headline (save-excursion (org-back-to-heading) > (org-element-at-point > (when headline > (org-fold-region > (org-element-property :begin headline

Re: [PATCH] Re: Change in `org-cycle-hook' breaks behavior

2022-05-28 Thread Ihor Radchenko
Tor Kringeland writes: > Ihor Radchenko writes: > >> Sure. Now, you need to call a different function to open all the drawers >> unconditionally. That function is: >> > Thanks! This almost imitates the old behavior, except that all drawers > (i.e., including sub-headlines) would be opened when

Re: [PATCH] Re: Change in `org-cycle-hook' breaks behavior

2022-05-28 Thread Tor Kringeland
Tor Kringeland writes: > a part of was opened. (So pressing TAB multiple times would first show > the outline with the first headline open, then the next would show > sub-headlines with their drawers open.) Correction: it wouldn't show the drawer of the headline on the first TAB press. But on

Re: [PATCH] Re: Change in `org-cycle-hook' breaks behavior

2022-05-28 Thread Tor Kringeland
Ihor Radchenko writes: > Sure. Now, you need to call a different function to open all the drawers > unconditionally. That function is: > > (let* ((headline (save-excursion (org-back-to-heading) > (org-element-at-point))) >(section (org-element-lineage >(org-element-at-poi

Re: how to export an org file, to 2 different locations (in to different formats)

2022-05-28 Thread Juan Manuel Macías
Uwe Brauer writes: > I have also to confess, that I usually am I bit hesitant to use > defadvice since it changes the vanilla function, and might cause > problems, but maybe this is just me. You are absolutely right, and I confess that I would have the same precautions :-). Also, the defadvice co

Re: [tip] org-publish to work with (very) large books

2022-05-28 Thread Juan Manuel Macías
Ihor Radchenko writes: > A more advanced approach would be using > \include + \includeonly instead of \input: > > https://web.archive.org/web/20160627050806/http://www.howtotex.com/tips-tricks/faster-latex-part-i-compile-only-parts/ Yeah, \include and \includeonly save the .aux files for each par

Re: how to export an org file, to 2 different locations (in to different formats)

2022-05-28 Thread Uwe Brauer
>>> "JMM" == Juan Manuel Macías writes: > Uwe Brauer writes: >> When I run it I obtain >> if: Symbol’s value as variable is void: my-latex-export-path >> >> Another point is if I decide to export it to ods, I need to modify that >> advice, but I agree the new function is more convenient. > You

Re: how to export an org file, to 2 different locations (in to different formats)

2022-05-28 Thread Juan Manuel Macías
Uwe Brauer writes: > When I run it I obtain > if: Symbol’s value as variable is void: my-latex-export-path > > Another point is if I decide to export it to ods, I need to modify that > advice, but I agree the new function is more convenient. You must add the variables to the document as local va

Re: Eev-wconfig.el etc etc, or: "Exercise: Learn Org!"

2022-05-28 Thread Eduardo Ochs
On Sat, 28 May 2022 at 01:52, Ihor Radchenko wrote: > (...) Hi Ihor, I think that you are underestimating how alien eev is for most people. Let me suppose that what you mean by your comments is this: "I've spent N minutes watching this video - for N big - and I feel that I've learned very