emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: emacs-orgmode@gnu.org
Subject: Re: Survey: changing a few default settings for Org 9.4
Date: Wed, 19 Feb 2020 17:16:44 +0100	[thread overview]
Message-ID: <87k14i1rir.fsf@fastmail.fm> (raw)
In-Reply-To: <87blpu37q6.fsf@fastmail.fm>


On Wed, Feb 19 2020, Matthew Lundin wrote:
>> - org-hide-emphasis-markers => t
>> - org-hide-macro-markers => t
[...]
> I have a few concerns about this. I believe that markup syntax, 
> as a
> rule, should be visible. Most markdown editors do not hide 
> markup by
> default. I realize that there are some exceptions in Org (e.g., 
> links).
> But editing around the invisible boundaries of links can be in 
> Org can
> be fussy (sometimes I have to do M-x visible-mode when editing 
> near the
> edges of links). So I'd recommend not changing the default here,
> especially for emphasis markers.

I was going to say the same thing. I set 
`org-hide-emphasis-markers` to t when I started out using Org, but 
at some point changed it to `nil` because editing at the 
beginning/end of words in emphasis markers was just too 
unpredictable. Same with links, BTW.

What I'm wondering, though, is why Org doesn't make hidden markup 
visible when the cursor moves into it. `prettify-symbols-mode` can 
do this, and AUCTeX does it by default (IINM) in folded macros and 
preview snippets, so it's definitely doable.

So my suggestion would be to keep it off unless/until such 
make-visible-at-point functionality is implemented.

-- 
Joost Kremers
Life has its moments

  reply	other threads:[~2020-02-19 16:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19  7:39 Survey: changing a few default settings for Org 9.4 Bastien
2020-02-19  8:57 ` Samuel Wales
2020-02-19  9:01   ` Bastien
2020-02-19 20:02   ` Samuel Wales
2020-02-19 20:15     ` Marcin Borkowski
2020-02-19 21:35       ` Bastien
2020-02-19 22:06         ` Samuel Wales
2020-02-19 11:03 ` Marco Wahl
2020-02-19 11:41   ` Bastien
2020-02-19 13:21     ` Marco Wahl
2020-02-19 13:39       ` Bastien
2020-02-19 17:57         ` Marco Wahl
2020-02-19 20:44           ` Bastien
2020-02-20  4:11       ` Adam Porter
2020-02-19 11:30 ` Nicolas Goaziou
2020-02-19 11:57   ` Bastien
2020-02-19 14:07     ` Nicolas Goaziou
2020-02-19 17:24       ` Bastien
2020-02-19 23:23         ` Vladimir Lomov
2020-02-19 23:53           ` Bastien
2020-02-20  0:20             ` Samuel Wales
2020-02-19 12:58   ` Tim Cross
2020-02-19 13:22     ` Bastien
2020-02-19 15:06       ` Tim Cross
2020-02-19 13:03   ` AW
2020-02-19 15:41 ` Matthew Lundin
2020-02-19 16:16   ` Joost Kremers [this message]
2020-02-19 17:13     ` Bastien
2020-02-19 16:50   ` Detlef Steuer
2020-02-19 17:14     ` Bastien
2020-02-20  4:07 ` Adam Porter
2020-02-20  7:10   ` Bastien
2020-02-20 14:10     ` Kaushal Modi
2020-02-21 15:49 ` Bastien
2020-02-21 19:36   ` Diego Zamboni
2020-02-21 21:28     ` Archenoth
2020-02-22  9:38       ` Bastien
2020-02-22 12:45         ` Nicolas Goaziou
2020-02-22 13:31           ` Bastien
2020-02-22 18:57           ` Archenoth
2020-03-18  2:20 ` Mark E. Shoulson
2020-03-18  8:58   ` Norman Tovey-Walsh
2020-03-18 20:47     ` Hiding emphasis markers Mark E. Shoulson
2020-05-22 16:47       ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k14i1rir.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).