Hi Texas,
Texas Cyberthal 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
Emacs has a giant normie-noob shaped hole in its intake funnel. The
warnings against using Emacs on Windows on the download page are good,
but not enough. Noobs need a positive recommendation of platform, and
a practical one, not ideological. It should say something like:
"If you've never coded,
That's a great idea. And if the Org tutorial included an easy option
to enable "PIM" mode for normie-noobs, so that Emacs starts behaving
like a PIM instead of an IDE, that would be even better. Someone who's
never coded before doesn't need IDE defaults.
On Fri, Feb 7, 2020 at 8:37 AM Corwin
Greetings,
On Thu, Feb 6, 2020 at 5:33 PM Texas Cyberthal
wrote:
> No, that isn't what I'm saying. I'm quite happy with Emacs, especially
> Spacemacs. However, I had a much harder adoption experience than
> necessary, and I find that the barriers to entry are preventing
> normie-noobs from
No, that isn't what I'm saying. I'm quite happy with Emacs, especially
Spacemacs. However, I had a much harder adoption experience than
necessary, and I find that the barriers to entry are preventing
normie-noobs from choosing Org as a PIM. So I intend to fix that.
On Fri, Feb 7, 2020 at 5:38 AM
Okay, I get it: Emacs (especially vanilla) just doesn't meet your
requirements. So be it! Horse for courses, as they say here in the
UK. All I can say is that I find most, if not all, other tools so
frustrating. I can never get them to work the way I want. With Emacs,
I can. Yes, this means
> I get this. My own approach is to simply use - at the start of the line and
> then each of these demi-paragraphs becomes a list item which are wrapped
> nicely (whether with visual or fill mode).
The cost of this approach is that one can't distinguish between
demi-paragraphs and actual
On Thursday, 6 Feb 2020 at 20:09, Texas Cyberthal wrote:
> 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:
I get this. My own approach is to simply use - at the start of the line
and then each of
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
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
auto-fill-mode is unsuitable for prose work, and especially for rough
notes which rely on demi paragraphs. Demi-paragraphs are important for
conveying uncertainty. Polished publishable prose can usually be
written with proper syntax and paragraphs separated by blank lines,
but the requisite
On Thursday, 6 Feb 2020 at 17:46, Texas Cyberthal wrote:
> auto-fill-mode definitely isn't what I want.
Why not? Just curious. Before I switched to visual-line-mode for all
org documents, I used auto-fill-mode for prose all the time. Together
with fill-paragraph (M-q), this did the job very
auto-fill-mode definitely isn't what I want. Beyond that I don't
understand your question.
I doubt it's productive to reiterate my legibility critiques since
I've concluded they're more appropriate for Spacemacs.
> the solution may simply be some example org mode hooks with, say, settings
> for
On Thursday, 6 Feb 2020 at 10:33, Texas Cyberthal wrote:
> Visual line mode is annoying and unnecessary; Spacemacs users do not
> need it because its defaults offer adequate paragraph navigation.
I'm not sure I understand the conflation of visual-line-mode with
paragraph navigation. Is it
Emacs is the tool that allows a non-technical user to bootstrap to
control over his IT environment. Within that, Org is the tool that
allows him to bootstrap to control of Emacs. So Org's defaults should
allow someone with no experience to learn the basic text manipulation
commands in the
> If I understand correctly, you're arguing that defaults should be changed
> because you don't understand how Emacs works, and since you use Spacemacs,
> you don't even care how it works.
You understand incorrectly. You incorrectly asserted that all users
must learn how visual line mode works.
Texas Cyberthal writes:
>> visual-line-mode and toggle-truncate-lines are basic Emacs commands
>> that all users should learn early.
>
> Visual lines, logical lines etc is a complicated mess that Spacemacs
> avoids entirely. I recall fiddling with it and never being satisfied,
> until adopting
should not have hit send on last email. meant to disengage
completely. will do so now. last email was not an invitation to
converse.
you do not know what every user needs.
i am feeling highly uncomfortable now.
On 2/4/20, Texas Cyberthal wrote:
>> many users need fully maximized emacs while still having legible paragraph
>> width.
>
> Splitting windows vertically creates narrower columns. Unlike
> truncation etc, window management actually is something all noobs
> many users need fully maximized emacs while still having legible paragraph
> width.
Splitting windows vertically creates narrower columns. Unlike
truncation etc, window management actually is something all noobs must
learn.
Narrower columns can increase reading speed, to a point. But wide
On 2/4/20, Texas Cyberthal wrote:
> Prose should wrap at
> window's edge
many users need fully maximized emacs while still having legible
paragraph width.
> visual-line-mode and toggle-truncate-lines are basic Emacs commands that all
> users should learn early.
Visual lines, logical lines etc is a complicated mess that Spacemacs
avoids entirely. I recall fiddling with it and never being satisfied,
until adopting Spacemacs solved it. Now I know
Texas Cyberthal writes:
> #+begin_src elisp
> (org-startup-truncated nil)
> #+end_src
>
> Line truncation is necessary for code but anathema for prose. Prose
> lines need visual wrap as windows resize, so that texts can be
> compared easily.
>
> Advanced Org uses such as large tables require
24 matches
Mail list logo
