Add option to disable strikthrough highlighting with + +

[gerazov]

Does this feature exist in Emacs orgmode core?

N/A

Orgmode link

No response

Feature value

It's convenient to use + when writing tasks or even when writing maths, e.g.

- the tool provides fast use + robustness to user input + community support

or

- total: 100 + 20 + 30 = 150

And this gets things striked through which is not really good as it becomes less readable.

I know that orgmode defines this for markup, and we're trying to stick to the specs, but it would be really useful to be able to turn it off.

In general, with checkboxes [X] and marking tasks as DONE, having the ability to strikethrough might be redundant. Not to say that I never have really needed to strikethrough something (and not just in orgmode :sweat_smile: )

Additional context

Also / for italic is bit problematic as it's in websites and file paths, but it's less intrusive.

As a side note I have a cool snippet that allows me to do calculations using qalc on selected maths - it might be worth having it somewhere in the docs :slightly_smiling_face:

"calculate selected formula
"take current line and run it through qalc
nnoremap <leader>sc yy:read !qalc "<C-R>""<CR>kdd 
" take current selection and run through qalc
vnoremap <leader>sc y:read !qalc "<C-R>""<CR>f="ay$ddk$a <Esc>"ap

[jgollenz]

Yeah, that happened to me to. We should expose that as an option: org_strikethrough_sequence.

Regarding that snippet: perhaps not directly in the docs, but we could establish a place for cool nvim-orgmode tweaks / oneliners / whatever that may be usefull to others. Similar to how nushell does this

[gerazov]

Cool idea! Maybe we can have a snippets section on https://nvim-orgmode.github.io/ ?

[kristijanhusak]

Are you using latest master? This should not be happening if there spaces around the + sign, I fixed that some time ago:

[gerazov]

I just updated and I get the same behavior :thinking:

[kristijanhusak]

How are you exactly setting up orgmode? I reproduced it with minimal_init.lua when I ran it, but this minimal_init also runs packer each time and loads the plugin manually. Once I updated minimal init to not run packer, since it installed everything first time, it started working fine.

Try replacing last tree lines:

load_plugins()
require('packer').sync()
vim.cmd [[autocmd User PackerCompileDone ++once lua load_config()]]

with this

load_plugins()
load_config()

and see if it works.

Edit: Try updated minimal_init https://github.com/nvim-orgmode/orgmode/blob/master/scripts/minimal_init.lua

[gerazov]

I'm using Vim Plug ... I'll look into it :+1:

[jgollenz]

@gerazov is this issue still relevant?

[gerazov]

Yeah, I changed to packer recently and the problem persists.

With the minimal config as instructed by @kristijanhusak it's ok.

So I don't know what's wrong, maybe close for now :slightly_smiling_face:

[jgollenz]

Weird. Sadly the only way to be sure what's going would be to toggle your other plugins on individually and see which one is the culprit :(

[kristijanhusak]

These issues should be solved. If it happens it's probably caused by some conflicting plugin.

[gerazov]

Still persists on my side but I'm ok with cleaning it up - it seems I'm the only one experiencing it and it's no biggy :+1: