For some time I've been wishing for asynchronous Babel session
evaluation. So I've created an experimental branch implementing this. I
have an initial version working for R, so I thought it'd be a good time
to seek feedback and gauge interest.
To test the attached patch, add ":async yes" to an R
I wrote this template to capture my bills from mostly one shop, but it
has support for multiple shops and the important feature is that it
suggests previous item names and remembers last prices, that gives you
lot's of autocompletion if you repetetivly buy often the same stuff over
and over again.
Hi Nicolas,
> -Original Message-
> From: Nicolas Goaziou
> Sent: den 1 juni 2019 23:01
> To: Gustav Wikström
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Proposal for new document-level syntax
>
> I only skimmed over your proposal, as I don't have much time. I'm sorry
> if you answered
Hello,
Gustav Wikström writes:
> I propose to allow properties to be defined also as document property
> keywords. All keywords in the top of a buffer, before any non-comment
> line, are document-level keywords. In effect, they are properties that
> apply in exactly the same way as
>>> "UB" == Uwe Brauer writes:
>>> "UB" == Uwe Brauer writes:
> [Snip]...
>> But I would like to have
>> \begin{solution}[5cm]
>> How can I pass that parameter when exporting? Thanks
> According to
> https://emacs.stackexchange.com/questions/34751/org-mode-latex-environment-in-drawer
>
>>> "UB" == Uwe Brauer writes:
[Snip]...
> But I would like to have
> \begin{solution}[5cm]
> How can I pass that parameter when exporting? Thanks
According to
https://emacs.stackexchange.com/questions/34751/org-mode-latex-environment-in-drawer
#+ATTR_LATEX: options:
Hi
I have the following example of a org file
#+begin_solution
The result is as follows
#+begin_src matlab :results output raw :exports results :eval never-export
l=0.33;
mypois=poisspdf(0,l);
myres=1-poisspdf(0,l)-poisspdf(1,l);
disp('\begin{align*}')
fprintf('P(X\\geq
Hi Eric!
> -Original Message-
> From: Fraga, Eric
> Sent: den 1 juni 2019 15:18
> To: Gustav Wikström
> Cc: emacs-orgmode@gnu.org
> Subject: Re: [O] Proposal for new document-level syntax
>
> For me, however, your proposed structure would clash strongly with my
> usual working
Dear Dmitrii,
Regarding the question about buffer-lens interaction. Let's take even
more complicated example: To run the command, the user hits some key
combination, which happens to be bound to different commands in the main
buffer and in the lense buffer (i.e. the main buffer is in org-mode,
On Saturday, 1 Jun 2019 at 15:45, Achim Gratz wrote:
> If the customization data isn't visible by default, does that address
> your concerns?
It might indeed. Depends on how intrusive it is and how easy it is to
manage.
But having said this, and my previous email, don't take my views too
much
Fraga, Eric writes:
> For me, however, your proposed structure would clash strongly with my
> usual working practice. Specifically, I put all customizations and
> settings at the end of my documents, along with, for instance, Emacs
> file local variables. These are things I do not change often
On Saturday, 1 Jun 2019 at 10:15, Gustav Wikström wrote:
> I propose a "document" element in org-element, a property-drawer on
> document-level, a setting-drawer on document-level and
> property-keywords (slightly different than what already exist). And
> would like your comments
---
doc/org-manual.org | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 469e16402..583840a74 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -3081,7 +3081,7 @@ External links are URL-like locators. They start with a
PROPOSAL FOR NEW DOCUMENT-LEVEL SYNTAX
Gustav Wikström
Table of Contents
_
1. Summary
2. Background, details etc.
3.
14 matches
Mail list logo
