From: Texas Cyberthal <texas.cyberthal@gmail.com>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-startup-truncated default should be nil [legibility 2/6]
Date: Thu, 6 Feb 2020 20:09:57 +0800 [thread overview]
Message-ID: <CAMUm493QTq1HE8Oup18QgY7BiFk5WkoyHxRMBp-15RbNSOJ3cg@mail.gmail.com> (raw)
In-Reply-To: <871rr83qxn.fsf@ucl.ac.uk>
No, I just didn't repeat everything.
A blank line is useful, yes. Use of demi-paragraphs implies use of
line breaks to signal stronger transitions. E.g., from my recent
workflow:
#+begin_quote
turning the mic off/on manually also causes a pop
so would need to pause recording first
simpler to just leave the mic on then
fair enough.
[2020-02-05 Wed 08:47]
seems I'm suffering from electet mic pop
which can be solved by adding a capacitor and resistor to the circuit?
[2020-02-05 Wed 08:52]
http://www.discovercircuits.com/H-Corner/popfree%20micophone%20switch.htm
pop-free microphone switch
could sample out the sound in audacity easily
#+end_quote
Single line breaks allow preservation of the chronological sequence of
thoughts, which is useful for e.g. debugging false assumptions.
The above was a simple example with short lines. But if they were long
and complex, vanilla Emac's defaults would make paragraph navigation
difficult.
> For writing and for intra-paragraph navigation, what is necessary beyond visual-line-mode, next-line (C-n, <down>), forward-word (M-f), forward sentence (M-e), and forward-paragraph (M-}), and equivalent for opposite direction?
What vanilla Emacs Org default visual-line-mode is missing for
informal prose notes:
- recognize sentences with a single space after terminal punctuation
- word wrap
- more line spacing and a variable pitch font
- denote single line breaks with the absence of continuation marks, as
truncate lines nil does
- C-a/e begin/end of line should still operate on logical lines.
It's easier to achieve the last two points without visual line mode,
since line-move-visual is t by default. Toggling truncation off is
enough.
visual-line-mode's minor luxury of slightly easier navigation to
arbitrary visual line endpoints doesn't compensate for loss of the
critical ability to identify logical lines with single line breaks,
and the loss of keybinds for quick navigation to their endpoints.
On Thu, Feb 6, 2020 at 7:17 PM Fraga, Eric <e.fraga@ucl.ac.uk> wrote:
>
> So, the only problem that you have, as far as I can tell, is that Emacs
> doesn't distinguish paragraphs by a single newline character but
> requires 2 instead? For me, a blank line between paragraphs is very
> useful to visually identify new paragraphs (or demi-paragraphs).
>
> For writing and for intra-paragraph navigation, what is necessary beyond
> visual-line-mode, next-line (C-n, <down>), forward-word (M-f), forward
> sentence (M-e), and forward-paragraph (M-}), and equivalent for opposite
> direction? (Okay, maybe a few others like begin/end of line, paging up
> and down, etc.) What does spacemacs provide that vanilla Emacs does
> not? (I've never used spacemacs so please excuse my ignorance.)
>
> --
> : Eric S Fraga via Emacs 28.0.50, Org release_9.3.2-233-gc2bc48
next prev parent reply other threads:[~2020-02-06 12:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 2:33 org-startup-truncated default should be nil [legibility 2/6] Texas Cyberthal
2020-02-06 6:55 ` Texas Cyberthal
2020-02-06 7:15 ` Fraga, Eric
2020-02-06 9:46 ` Texas Cyberthal
2020-02-06 10:16 ` Fraga, Eric
2020-02-06 10:51 ` Texas Cyberthal
2020-02-06 11:17 ` Fraga, Eric
2020-02-06 12:09 ` Texas Cyberthal [this message]
2020-02-06 12:40 ` Fraga, Eric
2020-02-06 21:21 ` Texas Cyberthal
2020-02-06 21:38 ` Fraga, Eric
2020-02-06 23:33 ` Texas Cyberthal
2020-02-07 0:37 ` Corwin Brust
2020-02-07 1:06 ` Texas Cyberthal
2020-02-07 4:27 ` Texas Cyberthal
-- strict thread matches above, loose matches on Subject: below --
2020-02-04 21:36 Texas Cyberthal
2020-02-04 23:26 ` Samuel Wales
2020-02-05 2:43 ` Texas Cyberthal
2020-02-05 3:49 ` Samuel Wales
2020-02-05 4:02 ` Samuel Wales
2020-02-05 4:09 ` Samuel Wales
2020-02-05 15:30 ` Adam Porter
2020-02-04 4:08 Texas Cyberthal
2020-02-04 7:05 ` Adam Porter
2020-02-10 7:00 ` 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=CAMUm493QTq1HE8Oup18QgY7BiFk5WkoyHxRMBp-15RbNSOJ3cg@mail.gmail.com \
--to=texas.cyberthal@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).