Re: [PATCH] Improve org-mouse support for checkboxes
On 9/18/2021 1:54 PM, Samuel Wales wrote: thanks for this. if tests are written, might be useful to include the case where half-checked are parents. I tested manually, and this behaves how I'd expect; not surprising, since it just calls `org-toggle-checkbox'. Maybe there's an argument that parent checkboxes shouldn't be clickable in the first place though. I don't think you can call `org-toggle-checkbox' on parent checkboxes (or if you can, I'm not sure what the trick is). My patch doesn't change that though, aside from having half-checked boxes be clickable in general. I could look into writing some automated tests for this, but I don't see any existing ones for org-mouse, and I'm not familiar with simulating mouse events for Emacs tests.
Re: [PATCH] Improve org-mouse support for checkboxes
thanks for this. if tests are written, might be useful to include the case where half-checked are parents. On 9/18/21, Jim Porter wrote: > While trying out `org-mouse', I noticed two semi-related issues with > checkboxes. First, intermediate-state checkboxes (like [-]) aren't > clickable. Second, if the checkboxes are inside a block and the theme > gives the block a background color, the block's background is removed > behind the checkbox. To see both of these in action: > >$ cat file.org >* Regular >- [X] Checked. >- [-] Half-checked. >- [ ] Not checked. >* In block >#+begin_src org >- [X] Checked. >- [-] Half-checked. >- [ ] Not checked. >#+end_src > >$ emacs -Q --eval '(progn (setq org-modules '"'"'(org-mouse)) > (custom-set-faces '"'"'(org-block ((t :background "green")' file.org > > The attached patch fixes both of these issues. For the first problem, > maybe it would be useful to put the regexp for checkboxes in a variable > somewhere so it doesn't get out of sync. I wasn't sure though, so I went > with the simpler solution for now. > > My FSF copyright assignment should be on file, but let me know if there > are any issues there. > -- The Kafka Pandemic Please learn what misopathy is. https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
Re: Citation not inserted as 1st item in footnote (using org-cite and org-ref-cite)
Elias - do you mean org-cite-insert won't allow this? [fn:1] [cite:@doe2019]. If yes, I don't see that; it inserts fine. I'm using bibtex-actions for the insert processor, but I don't think that should make any difference, since it's org-cite that's handling that. On Sat, Sep 18, 2021 at 4:23 PM Elias Bounatirou wrote: > > Hi, > When I try to insert a citation as the first item into a > non-inline-definition footnote, org-ref-cite refuses to insert the citation > returning in the minibuffer "Cannot insert citation here". The same problem > does not occur if the footnote has an inline definition. As for > non-inline-definition footnotes, if I copy the citation into the footnote, no > problem occurs, either. The citation is also properly exported to LaTeX. > Is this a problem of org-cite/org-mode in general or rather of org-ref-cite? > > Best regards, > Elias
Citation not inserted as 1st item in footnote (using org-cite and org-ref-cite)
Hi, When I try to insert a citation as the first item into a non-inline-definition footnote, org-ref-cite refuses to insert the citation returning in the minibuffer "Cannot insert citation here". The same problem does not occur if the footnote has an inline definition. As for non-inline-definition footnotes, if I copy the citation into the footnote, no problem occurs, either. The citation is also properly exported to LaTeX. Is this a problem of org-cite/org-mode in general or rather of org-ref-cite? Best regards, Elias
bug#50555: [PATCH] Re: bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
Younes Ben El writes:
> Daniel Fleischer writes:
>
> Here is the hint: since “minted” is using a python package (pygments) for
> the highlighting, one need to add the
> “-shell-escape” to the call. Other than that, everything works as
> planned. Since it’s a specific configuration for
> using “minted”, I’ll add a comment in the manual.
>
> If you feel that there is still an issue with the [], please provide an
> emacs -Q recipe that shows it, after adding
> the “-shell-escape” flag.
>
> Ah, That’s the deal. Updating The Manual Will do the trick Thanks for taking
> time and looking up at this issue .
>
Patch: comment suggesting the usage of the flag; many changes due to the
footnote numbering "push".
>From 64150d05e83b346969173134cbd237cc3aae7e15 Mon Sep 17 00:00:00 2001
From: Daniel Fleischer
Date: Sat, 18 Sep 2021 22:57:32 +0300
Subject: [PATCH] org-manual: comment about latex code-block export
* doc/org-manual.org: when using the latex Minted package, one needs to
set the '-shell-escape' flag in 'org-latex-pdf-process'.
Signed-off-by: Daniel Fleischer
---
doc/org-manual.org | 112 +++--
1 file changed, 58 insertions(+), 54 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 10813a812..9776abb76 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -13769,7 +13769,7 @@ *** Source blocks in LaTeX export
The LaTeX export back-end passes string values in =:options= to LaTeX
packages for customization of that specific source block. In the
example below, the =:options= are set for Minted. Minted is a source
-code highlighting LaTeX package with many configurable options.
+code highlighting LaTeX package with many configurable options[fn:134].
#+begin_example
,#+ATTR_LATEX: :options commentstyle=\bfseries
@@ -14021,7 +14021,7 @@ ** OpenDocument Text Export
The ODT export back-end handles creating of OpenDocument Text (ODT)
format. Documents created by this exporter use the
-{{{cite(OpenDocument-v1.2 specification)}}}[fn:134] and are compatible
+{{{cite(OpenDocument-v1.2 specification)}}}[fn:135] and are compatible
with LibreOffice 3.4.
*** Pre-requisites for ODT export
@@ -14422,7 +14422,7 @@ LaTeX math snippets
variables ~org-latex-to-mathml-convert-command~ and
~org-latex-to-mathml-jar-file~.
- If you prefer to use MathToWeb[fn:135] as your converter, you can
+ If you prefer to use MathToWeb[fn:136] as your converter, you can
configure the above variables as shown below.
#+begin_src emacs-lisp
@@ -14433,7 +14433,7 @@ LaTeX math snippets
#+end_src
#+texinfo: @noindent
- or, to use LaTeXML[fn:136] instead,
+ or, to use LaTeXML[fn:137] instead,
#+begin_src emacs-lisp
(setq org-latex-to-mathml-convert-command
@@ -14752,7 +14752,7 @@ Customizing tables in ODT export
tables, see [[*Tables in ODT export]].
This feature closely mimics the way table templates are defined in the
-OpenDocument-v1.2 specification[fn:137].
+OpenDocument-v1.2 specification[fn:138].
#+vindex: org-odt-table-styles
For quick preview of this feature, install the settings below and export the
@@ -14786,7 +14786,7 @@ Customizing tables in ODT export
To use this feature proceed as follows:
-1. Create a table template[fn:138].
+1. Create a table template[fn:139].
A table template is set of =table-cell= and =paragraph= styles for
each of the following table cell categories:
@@ -14825,7 +14825,7 @@ Customizing tables in ODT export
== element of the content template file
(see [[x-orgodtcontenttemplate-xml][Factory styles]]).
-2. Define a table style[fn:139].
+2. Define a table style[fn:140].
#+vindex: org-odt-table-styles
To define a table style, create an entry for the style in the
@@ -15939,7 +15939,7 @@ *** Publishing action
~org-org-publish-to-org~. This produces =file.org= and puts it in the
publishing directory. If you want a htmlized version of this file,
set the parameter ~:htmlized-source~ to ~t~. It produces
-=file.org.html= in the publishing directory[fn:140].
+=file.org.html= in the publishing directory[fn:141].
Other files like images only need to be copied to the publishing
destination; for this you can use ~org-publish-attachment~. For
@@ -17322,13 +17322,13 @@ *** How to evaluate source code
#+kindex: C-c C-v e
#+findex: org-babel-execute-src-block
Org provides many ways to execute code blocks. {{{kbd(C-c C-c)}}} or
-{{{kbd(C-c C-v e)}}} with the point on a code block[fn:141] calls the
+{{{kbd(C-c C-v e)}}} with the point on a code block[fn:142] calls the
~org-babel-execute-src-block~ function, which executes the code in the
block, collects the results, and inserts them in the buffer.
#+cindex: @samp{CALL}, keyword
#+vindex: org-babel-inline-result-wrap
-By calling a named code block[fn:142] from an Org mode buffer or
+By calling a named code block[fn:143] from an Org mode buffer or
a tab
bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
Daniel Fleischer writes: > Here is the hint: since "minted" is using a python package (pygments) for > the highlighting, one need to add the "-shell-escape" to the call. Other > than that, everything works as planned. Since it's a specific > configuration for using "minted", I'll add a comment in the manual. > > If you feel that there is still an issue with the [], please provide an > emacs -Q recipe that shows it, after adding the "-shell-escape" flag. Ah, That's the deal. Updating The Manual Will do the trick Thanks for taking time and looking up at this issue .
bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
I verified again, this time with emacs -Q; the empty argument list []
does NOT stop you from compiling org into PDF.
> (with-eval-after-load 'ox-latex
> (add-to-list 'org-latex-packages-alist '("" "minted"))
> (setq org-latex-listings 'minted)
> (setq org-latex-pdf-process
> '("pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %f"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %f"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory
> %o %f")))
>
Here is the hint: since "minted" is using a python package (pygments) for
the highlighting, one need to add the "-shell-escape" to the call. Other
than that, everything works as planned. Since it's a specific
configuration for using "minted", I'll add a comment in the manual.
If you feel that there is still an issue with the [], please provide an
emacs -Q recipe that shows it, after adding the "-shell-escape" flag.
--
Daniel Fleischer
[PATCH] Improve org-mouse support for checkboxes
While trying out `org-mouse', I noticed two semi-related issues with
checkboxes. First, intermediate-state checkboxes (like [-]) aren't
clickable. Second, if the checkboxes are inside a block and the theme
gives the block a background color, the block's background is removed
behind the checkbox. To see both of these in action:
$ cat file.org
* Regular
- [X] Checked.
- [-] Half-checked.
- [ ] Not checked.
* In block
#+begin_src org
- [X] Checked.
- [-] Half-checked.
- [ ] Not checked.
#+end_src
$ emacs -Q --eval '(progn (setq org-modules '"'"'(org-mouse))
(custom-set-faces '"'"'(org-block ((t :background "green")' file.org
The attached patch fixes both of these issues. For the first problem,
maybe it would be useful to put the regexp for checkboxes in a variable
somewhere so it doesn't get out of sync. I wasn't sure though, so I went
with the simpler solution for now.
My FSF copyright assignment should be on file, but let me know if there
are any issues there.
From b2bd5115a89b9b26107aca4b59e516dc7d64f0cc Mon Sep 17 00:00:00 2001
From: Jim Porter
Date: Sat, 18 Sep 2021 12:22:41 -0700
Subject: [PATCH] org-mouse: Support intermediate-state checkboxes
* lisp/org-mouse.el (org-mode-hook): Use regexp from
`org-set-font-lock-defaults' and set font-lock keywords more robustly.
---
lisp/org-mouse.el | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lisp/org-mouse.el b/lisp/org-mouse.el
index 4471d8e8d..eae6cd98f 100644
--- a/lisp/org-mouse.el
+++ b/lisp/org-mouse.el
@@ -890,8 +890,8 @@ This means, between the beginning of line and the point."
(when (memq 'activate-checkboxes org-mouse-features)
(font-lock-add-keywords
nil
- `(("^[ \t]*\\([-+*]\\|[0-9]+[.)]\\) +\\(\\[[ X]\\]\\)"
- (2 `(face org-checkbox keymap ,org-mouse-map mouse-face
highlight) t)))
+ `(("^[ \t]*\\(?:[-+*]\\|[0-9]+[.)]\\)[
\t]+\\(?:\\[@\\(?:start:\\)?[0-9]+\\][ \t]*\\)?\\(\\[[- X]\\]\\)"
+ (1 `(face nil keymap ,org-mouse-map mouse-face highlight)
prepend)))
t))
(defadvice org-open-at-point (around org-mouse-open-at-point
activate)
--
2.25.1
Manually/programmatically adding a state transition message
I am writing some code to change the state of an org headline. I have figured out that an error will pop up if I am automatically transitioning to a state that requires a note logged. How can I automatically add a state transition note? I know I can write this: (universal-argument) (universal-argument) (universal-argument) (org-todo "WAIT") and this will automatically skip note logging. I've looked at the code around adding a log-note and it looks like it might be automatable but there's a lot of pieces I don't know in there, so if there's a way to add just a state transition with a programmatically provided note, I'll take that, please :) Thanks, --Aldric
Re: Overlining troubles
Hi!
I use orgmode to read and study directly but I am not able to set up
LaTeX preview. So I need something "direct", but I can't renounce to
exporting it.
So that you have an idea of what I'm dealing with, I am able to set up
LaTeX exporting on my home computer, but I can't make it work at my work
computer. LaTeX preview is almost a dream to me.
Best regards
El 18/09/2021 a las 19:32, Timothy escribió:
Hi Ypo,
If you’re thinking of maths, why not just write inline LaTeX, e.g.
\(\bar{x}\) ?
All the best,
*Timothy*
*From*: Ypo <mailto:"Ypo"; >
*Subject*: Re: Overlining troubles
*To*: emacs-orgmode@gnu.org <mailto:"emacs-orgmode@gnu.org";
>
*Date*: Sun, 19 Sep 2021 01:14:52 +0800
Thanks, Timothy and Max. I'll try to explain myself better.
Overlining is quite useful in math expressions, for example I needed
it to represent the arithmetic mean.
I need to be able to overline text and to export it overlined. The
only dirty solution I found was to change the =verbatim= mark, but now
I can't use verbatim on orgmode, and the overlined text isn't
exported, so unsustainable "solution".
The perfect solution? To be able to add a new marker to overline text
that can be exported overlined.
Best regards
:-)
El 18/09/2021 a las 18:00, emacs-orgmode-requ...@gnu.org escribió:
Message: 7 Date: Sat, 18 Sep 2021 20:48:36 +0800 From: Timothy
To: Ypo Cc:
emacs-orgmode@gnu.org Subject: Re: Overlining troubles Message-ID:
<87ee9mdp5i@gmail.com> Content-Type: text/plain; charset="utf-8"
Hi Ypo, You’ll likely want to override `org-html-verbatim' and
`org-latex-verbatim' to produce overlines in exports. All the best,
Timothy -- next part ------ An HTML attachment
was scrubbed... URL:
<https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20210918/78086bf1/attachment.html>
-- Message: 8 Date: Sat, 18 Sep 2021
19:50:31 +0700 From: Max Nikulin To:
emacs-orgmode@gnu.org Subject: Re: Overlining troubles Message-ID:
Content-Type: text/plain; charset=utf-8;
format=flowed On 18/09/2021 15:14, Ypo wrote:
I have tried many times in different ways to "overline" text. I am able
to overline it on orgmode (I sacrificed the =verbatim= marker to achieve
it), but it doesn't export overlined (nor HTML, nor LaTeX).
I tried in the past to add it to "Org Emphasis Alist" but it didn't work.
Is it possible to add overlining and to export it?
Just to avoid confusion, `org-emphasis-alist' is not designed to change
or to*add* new markers:
https://orgmode.org/list/87blatodir@nicolasgoaziou.fr/ (Nicolas
Goaziou, Mon, 05 Apr 2021 01:06:52 +0200, Re: Using backticks for the
inline code delimeter?)
If you wish to export =verbatim= text as text with line above, perhaps,
you can define custom "verbatim" export filter
"info (org) Advanced Export Configuration"
https://orgmode.org/manual/Advanced-Export-Configuration.html
A macro expanded with markup for particular backend (e.g. @@latex:
...@@) may be a better option
"info (org) Macro Replacement"
https://orgmode.org/manual/Macro-Replacement.html
Some people experimenting with custom link types with associated
handlers for particular export backends:
https://orgmode.org/list/87mtq9zatr@posteo.net/ (Juan Manuel Macías,
Mon, 26 Jul 2021 09:25:04 +, Multilingual quotes inside paragraphs).
Unfortunately you described what you have tried in too general words to
suggest something more specific.
Re: Overlining troubles
Hi Ypo,
If you’re thinking of maths, why not just write inline LaTeX, e.g.
`\(\bar{x}\)' ?
All the best,
Timothy
Re: Overlining troubles
Thanks, Timothy and Max. I'll try to explain myself better. Overlining is quite useful in math expressions, for example I needed it to represent the arithmetic mean. I need to be able to overline text and to export it overlined. The only dirty solution I found was to change the =verbatim= mark, but now I can't use verbatim on orgmode, and the overlined text isn't exported, so unsustainable "solution". The perfect solution? To be able to add a new marker to overline text that can be exported overlined. Best regards :-) El 18/09/2021 a las 18:00, emacs-orgmode-requ...@gnu.org escribió: Message: 7 Date: Sat, 18 Sep 2021 20:48:36 +0800 From: Timothy To: Ypo Cc: emacs-orgmode@gnu.org Subject: Re: Overlining troubles Message-ID: <87ee9mdp5i@gmail.com> Content-Type: text/plain; charset="utf-8" Hi Ypo, You’ll likely want to override `org-html-verbatim' and `org-latex-verbatim' to produce overlines in exports. All the best, Timothy -- next part -- An HTML attachment was scrubbed... URL: <https://lists.gnu.org/archive/html/emacs-orgmode/attachments/20210918/78086bf1/attachment.html> -- Message: 8 Date: Sat, 18 Sep 2021 19:50:31 +0700 From: Max Nikulin To: emacs-orgmode@gnu.org Subject: Re: Overlining troubles Message-ID: Content-Type: text/plain; charset=utf-8; format=flowed On 18/09/2021 15:14, Ypo wrote: I have tried many times in different ways to "overline" text. I am able to overline it on orgmode (I sacrificed the =verbatim= marker to achieve it), but it doesn't export overlined (nor HTML, nor LaTeX). I tried in the past to add it to "Org Emphasis Alist" but it didn't work. Is it possible to add overlining and to export it? Just to avoid confusion, `org-emphasis-alist' is not designed to change or to*add* new markers: https://orgmode.org/list/87blatodir@nicolasgoaziou.fr/ (Nicolas Goaziou, Mon, 05 Apr 2021 01:06:52 +0200, Re: Using backticks for the inline code delimeter?) If you wish to export =verbatim= text as text with line above, perhaps, you can define custom "verbatim" export filter "info (org) Advanced Export Configuration" https://orgmode.org/manual/Advanced-Export-Configuration.html A macro expanded with markup for particular backend (e.g. @@latex: ...@@) may be a better option "info (org) Macro Replacement" https://orgmode.org/manual/Macro-Replacement.html Some people experimenting with custom link types with associated handlers for particular export backends: https://orgmode.org/list/87mtq9zatr@posteo.net/ (Juan Manuel Macías, Mon, 26 Jul 2021 09:25:04 +, Multilingual quotes inside paragraphs). Unfortunately you described what you have tried in too general words to suggest something more specific.
bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
I Apologize for the previous mail, seems like it didn't go through
correctly .
Actually it does compile and produces a pdf file , however there's some
issue with it as it doesn't display the code_block.
if we set our emacs config to
#+begin_src emacs-lisp
(require 'ox-latex)
(setq org-latex-listings 'minted)
#+end_src
Then Set In Our org file
#+begin_src org
#+LATEX_CLASS: article
#+LATEX_CLASS_OPTIONS: [letterpaper]
#+LATEX_HEADER: \usepackage{minted}
#+OPTIONS: toc:t
#+end_src
and edit our org file and then compile it , it will not produce a code_block.
probably because of empty options [] like i tested , after we remove them it
works.
Digging little into the issue, if we specfied a pdf-export-commands , it will
result into
the expected exported pdf.
#+begin_src emacs-lisp
(with-eval-after-load 'ox-latex
(add-to-list 'org-latex-packages-alist '("" "minted"))
(setq org-latex-listings 'minted)
(setq org-latex-pdf-process
'("pdflatex -shell-escape -interaction nonstopmode -output-directory %o
%f"
"pdflatex -shell-escape -interaction nonstopmode -output-directory %o
%f"
"pdflatex -shell-escape -interaction nonstopmode -output-directory %o
%f")))
#+end_src
Not sure why it needs these in order to export correctly.
Here's some screenshots of the
issue,[[https://i.imgur.com/VB1leIW.png][Exported_pdf]],[[https://i.imgur.com/x8lIIFW.png][org_file]],[[https://i.imgur.com/Tm0lzp4.png][exported_tex]],[[https://i.imgur.com/bxdI7Ja.png][Removing_Brackets]]
Re: behavior of (org-insert-heading-respect-content)
Victor! > Le 13 Sep 2021, Marco Wahl a écrit : > >> As far is I see it, the intended behavior of >> org-insert-heading-respect-content with point before the first heading >> is to >> >> - insert the new heading immediately before the first heading. Respect >> the content! > Hi Marco ! > > I agree with you. But this does not work. Say I have a buffer with this > content : > > put point HERE and C- > Some more stuff > * Heading > content > > > When point is at HERE and I C-, org inserts a new asterisk on > the after "stuff", but on the same line → not a proper heading. >> >> - If there is no heading at all in the file the heading shall be >> inserted at the bottom of the file. > > Yes. But I get the same behavior with > > put point HERE and C- > Some more stuff > > The asterisk is inserted right after "stuff", on the same line → not > a proper heading. > >> >> Do we agree on the desired behavior of >> org-insert-heading-respect-content? > > Yes, we do! >> >> With your proposition the respect for the content gets lost, >> doesn't it? > > Yes, you’re right. It currently does not respect the content before > first heading. Therefore it’s not a fix for the behavior of > org-insert-heading-respect-content. > It’s just the quickest workaround I’ve come up with to make my own > function work (in my use-case, when I call that function, either point > is at point-min in a brand new buffer, or point is below the first > heading). Okay, thanks for clarifying. Would be great if you could test the fix. Thank you!
Re: Overlining troubles
On 18/09/2021 15:14, Ypo wrote: I have tried many times in different ways to "overline" text. I am able to overline it on orgmode (I sacrificed the =verbatim= marker to achieve it), but it doesn't export overlined (nor HTML, nor LaTeX). I tried in the past to add it to "Org Emphasis Alist" but it didn't work. Is it possible to add overlining and to export it? Just to avoid confusion, `org-emphasis-alist' is not designed to change or to *add* new markers: https://orgmode.org/list/87blatodir@nicolasgoaziou.fr/ (Nicolas Goaziou, Mon, 05 Apr 2021 01:06:52 +0200, Re: Using backticks for the inline code delimeter?) If you wish to export =verbatim= text as text with line above, perhaps, you can define custom "verbatim" export filter "info (org) Advanced Export Configuration" https://orgmode.org/manual/Advanced-Export-Configuration.html A macro expanded with markup for particular backend (e.g. @@latex: ...@@) may be a better option "info (org) Macro Replacement" https://orgmode.org/manual/Macro-Replacement.html Some people experimenting with custom link types with associated handlers for particular export backends: https://orgmode.org/list/87mtq9zatr@posteo.net/ (Juan Manuel Macías, Mon, 26 Jul 2021 09:25:04 +, Multilingual quotes inside paragraphs). Unfortunately you described what you have tried in too general words to suggest something more specific.
Re: Overlining troubles
Hi Ypo, You’ll likely want to override `org-html-verbatim' and `org-latex-verbatim' to produce overlines in exports. All the best, Timothy
bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
Younes Ben El [2021-09-12 Sun 21:25] wrote: > When exporting from org to latex , src blocks are not handled correctly. > This happens when you specify a prog-language name after #+BEGIN_SRC > Which results to an extra *[]* in exported latex file thus when > compiling it to pdf , it won't display the code block. It's true that there are empty [] argument list for the minted package in the latex code; however I am able to compile your (and my) latex code into PDF with and without it so I'm not sure that something needs to be done in org-mode. Can you send the resulting latex file and/or specify why it's not compiling? -- Daniel Fleischer
Re: BUG Visibility Cycling with inline tasks
Sorry, I forgot: Org mode version 9.4.6 (9.4.6-gcf30f7 Am Sa., 18. Sept. 2021 um 10:27 Uhr schrieb Michael Dauer < mick.da...@gmail.com>: > Hi, > > Inline tasks are a great feature of org-mode, very useful to include tasks > in all sorts of documents without interfering with the document structure. > > But it seems that there are multiple issues with multiple org commands and > inline tasks (visibility, navigation, selection). > > For that reason I already suggested a while ago that the * END line would > be indented 1 level more then the * start of the inline task. By that it > would behave like a normal subtree for all org-commands. > > Here a minimal example of an issue with visibility cycling: > >>> > * Example > ** heading 1 > x > ** heading 2 > *** TODO Test access with provided credentials > x > *** END > ** heading 3 > *** TODO State "high value" targets > :@CB: > x > *** END > ** heading 4 > x > <<< > > Stating collapsed, pressing TAB on the heading 2 already shows the issue. > > IMO the suggested simple (but breaking (but easy to fix)) design change > would make inline tasks more compatible and stable, and even more intuitive > in the expanded visualization. > > Regards, > Michael >
BUG Visibility Cycling with inline tasks
Hi, Inline tasks are a great feature of org-mode, very useful to include tasks in all sorts of documents without interfering with the document structure. But it seems that there are multiple issues with multiple org commands and inline tasks (visibility, navigation, selection). For that reason I already suggested a while ago that the * END line would be indented 1 level more then the * start of the inline task. By that it would behave like a normal subtree for all org-commands. Here a minimal example of an issue with visibility cycling: >>> * Example ** heading 1 x ** heading 2 *** TODO Test access with provided credentials x *** END ** heading 3 *** TODO State "high value" targets :@CB: x *** END ** heading 4 x <<< Stating collapsed, pressing TAB on the heading 2 already shows the issue. IMO the suggested simple (but breaking (but easy to fix)) design change would make inline tasks more compatible and stable, and even more intuitive in the expanded visualization. Regards, Michael
Overlining troubles
Hi I have tried many times in different ways to "overline" text. I am able to overline it on orgmode (I sacrificed the =verbatim= marker to achieve it), but it doesn't export overlined (nor HTML, nor LaTeX). I tried in the past to add it to "Org Emphasis Alist" but it didn't work. Is it possible to add overlining and to export it? Best regards
