From: Bastien <bzg@gnu.org>
To: Texas Cyberthal <texas.cyberthal@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-startup-truncated default should be nil [legibility 2/6]
Date: Mon, 10 Feb 2020 08:00:07 +0100 [thread overview]
Message-ID: <87lfpbapvs.fsf@gnu.org> (raw)
In-Reply-To: <CAMUm490OzKEPONm-qc8tATRF9+71JwFZLXXOeRsaKRKGkqOuhg@mail.gmail.com> (Texas Cyberthal's message of "Tue, 4 Feb 2020 12:08:35 +0800")
Hi Texas,
Texas Cyberthal <texas.cyberthal@gmail.com> writes:
> #+begin_src elisp
> (org-startup-truncated nil)
> #+end_src
I disagree.
The whole discussion about mixing prose and code in the same buffer is
interesting: ideas like mixing variable pitch fonts, truncating lines
for specific parts of the buffer, etc. are all worth experimenting,
but they are about *Emacs*, not just Org.
Your best luck is to discuss this on emacs-devel first.
Thanks,
--
Bastien
next prev parent reply other threads:[~2020-02-10 7:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 4:08 org-startup-truncated default should be nil [legibility 2/6] Texas Cyberthal
2020-02-04 7:05 ` Adam Porter
2020-02-10 7:00 ` Bastien [this message]
-- 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-06 2:33 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
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
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=87lfpbapvs.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=texas.cyberthal@gmail.com \
/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).