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 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 w
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 foretho
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-p
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
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 th
Hello,
I'm trying to create an org link to a specific place in an OCaml file. I
thought I would use some specific target in an OCaml comment, but it
does not work.
Here is an OCaml comment:
(* Object projection functions *)
Here is the link create by `org-store-link` (I put it here with no
desc
I think you need to do it like this:
#+BEGIN_SRC test.ml -r
(* Object projection functions *) (ref:opf)
#+END_SRC
[[file:2020-02-05.org::(opf)]]
The -r in the header removes the coderef when you run it.
John
---
Professor John Kitchin
Doherty Hall A207F
De
Hello John,
On 2020-02-06 09:58, John Kitchin writes:
> I think you need to do it like this:
>
> #+BEGIN_SRC test.ml -r
>
> (* Object projection functions *) (ref:opf)
>
>
> #+END_SRC
>
> [[file:2020-02-05.org::(opf)]]
>
> The -r in the header removes the coderef when you run it.
Thank you for
Hello,
Alan Schmitt writes:
> The strange part is that linking to arbitrary code works. It seems that
> the OCaml comment syntax is problematic here.
Link enclosed within parens meant coderef links, i.e., the syntax is
reserved. You can probably remove the closing parenthesis to avoid this.
Re
Hello,
I've found that some strange results when outputing html from R.
Do you have some insights on a potential solution?
Best regards,
Jeremie
Org mode version 9.3.4 (9.3.4-elpa @ /home/djj/.emacs.d/elpa/org-20200206/)
#+PROPERTY: header-args:R :eval yes :exports results :colname
Hello Nicolas,
On 2020-02-06 18:10, Nicolas Goaziou writes:
> Link enclosed within parens meant coderef links, i.e., the syntax is
> reserved. You can probably remove the closing parenthesis to avoid this.
Thank you for the explanation. Is there a way to either escape the
parentheses (maybe url
Hi Eric,
Great idea! I hadn't considered using the =script= command, it's a great
starting point.
Thanks!
--Diego
On Thu, Feb 6, 2020 at 7:55 AM Fraga, Eric wrote:
> On Wednesday, 5 Feb 2020 at 18:25, Diego Zamboni wrote:
> > tl;dr: is there a way to have ob-shell (or some similar mode) run
Hi again,
> -Original Message-
> From: Nicolas Goaziou
> Sent: den 5 februari 2020 17:54
> To: Gustav Wikström
> Cc: emacs-orgmode@gnu.org
> Subject: Re: attachment: link type export to HTML invalid attach dir
>
> > That was kind of what I was trying to do, by allowing subtyping, so
> >
> 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 bullet
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 t
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 F
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 choos
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 Brust
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, t
20 matches
Mail list logo
