stardiviner writes:
> When I try to evaluate js src block code with session.
> I found it is suspended. After edebug, found the problem is on macro
> org-babel-comint-with-output.
>
> Here is a minimal reproduce code:
>
> #+begin_src emacs-lisp
> (org-babel-comint-with-output
> ("*skewer-r
roberthambr...@gmail.com writes:
> From: Robert Hambrock
>
> * lisp/ob-clojure.el (org-babel-execute:clojure): Implemented :target,
> which allows selection of connection.
> * lisp/ob-clojure.el (org-babel-execute:clojurescript): New
> ClojureScript interface that uses :target flag to specify `
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> Nicolas Goaziou writes:
>>
>> Hi, sorry for late response, because I'm a little lazy on give effort on
>> review my patch and improve it again. But now I finished it. Actually I
>> corrected my patch as soon as you replied email wit
Morning,
recently I tried to use ob-go and ran immediately into:
org-babel-execute:go: Invalid function: (results (org-babel-eval (format "%s
run %s \"%s\" %s" org-babel-go-command (mapconcat (quote identity)
(org-babel-go-as-list flags) " ") (org-babel-process-file-name tmp-src-file)
(mapconc
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> Garreau, Alexandre writes:
>>
>>> Why is there no syntax highlighting for *inline* source/code blocks?
>>>
>>> For instance, if I type the following:
>>>
>>> #+BEGIN_SRC org
>>> src_emacs-lisp{(foo bar (quux))}
>>> #+END_SRC
>>>
On Sat, Oct 13, 2018 at 1:56 AM Colin Baxter wrote:
>
> > Tom Burbage writes:
>
> > When I use simple lists, I would like to be able to mix in '!' and
> > '?' with '-' as these are sometimes more expressive of what the
> > list item represents. My request is that the list of cha
whether it is an example of it i am not sure, but the case in the
org-capture thread is typical of a class of buffer corruption bugs
that is common in org.
if you have found similar corruption in your org files and wondered
why, this is probably the cause. newlines that you didn't enter are
also
Eric S Fraga writes:
> On Wednesday, 24 Oct 2018 at 12:38, Roland Everaert wrote:
>> Pleased to see it was helpful. The funny thing is that I use that config
>> for, maybe, 10 years and never think about changing it.
>
> I've been using emacs for well over 30 years now. You would not believe t
Kaushal Modi writes:
> On Wed, Oct 24, 2018 at 2:04 AM Nicolas Goaziou
> wrote:
>>
>>
>> No objection from me. Thank you!
>
> Actually, before making this change, I started reading up on the HTML5
> spec on the b, strong, i, em tags, and now I am confused as ever.
>
> Facts:
>
> - b and i are
"Garreau, Alexandre" writes:
> Le 24/10/2018 à 18h15, Nicolas Goaziou a écrit :
>>
>> Note that orgstruct-mode, and orgstruct++-mode are removed from the code
>> base.
>
> No really? how sad! do anyone knows why?
You may want to browse the mailing list archives for discussions about
it. Essentia
Hello Nicolas,
Many thanks for your swift response!
On 2018-10-24, at 09:04 , Nicolas Goaziou wrote:
> [...]
> I see you are not including Latin1 export. Is there any reason to
> implement pure ASCII export? Wouldn't UTF-8 be sufficient?
>
> More generally, I wonder if, in 2018, it still makes
Le 24/10/2018 à 18h15, Nicolas Goaziou a écrit :
> "Garreau, Alexandre" writes:
>> On 2018-10-24 at 17:31, Garreau, Alexandre wrote:
>>> I finally found how people naturally made their mail with org, with
>>> orgstruct++-mode, that I just tried. However that triggers an infinite
>>> loop error (“
Hello,
"Garreau, Alexandre" writes:
> On 2018-10-24 at 17:31, Garreau, Alexandre wrote:
>> I finally found how people naturally made their mail with org, with
>> orgstruct++-mode, that I just tried. However that triggers an infinite
>> loop error (“car: Lisp nesting exceeds ‘max-lisp-eval-depth
On 2018-10-24 at 17:31, Garreau, Alexandre wrote:
> I finally found how people naturally made their mail with org, with
> orgstruct++-mode, that I just tried. However that triggers an infinite
> loop error (“car: Lisp nesting exceeds ‘max-lisp-eval-depth’”), because
> then indent-line-function ref
I finally found how people naturally made their mail with org, with
orgstruct++-mode, that I just tried. However that triggers an infinite
loop error (“car: Lisp nesting exceeds ‘max-lisp-eval-depth’”), because
then indent-line-function refers to org-indent-line, which when
orgstruct-is-++ is true
On Wed, Oct 24, 2018 at 2:04 AM Nicolas Goaziou wrote:
>
>
> No objection from me. Thank you!
Actually, before making this change, I started reading up on the HTML5
spec on the b, strong, i, em tags, and now I am confused as ever.
Facts:
- b and i are not deprecated
- b and strong are both vali
On Wednesday, 24 Oct 2018 at 09:12, Matt Price wrote:
> Eric, you seem to be replying to an email that I sometimes don't have -- I
> would love to see what @stardiviner wrote, do you stil lhave the email?
I've forwarded that email to you but it's strange that you missed it as
it was sent to the or
Eric, you seem to be replying to an email that I sometimes don't have -- I
would love to see what @stardiviner wrote, do you stil lhave the email?
On Tue, Oct 23, 2018 at 9:12 AM Eric S Fraga wrote:
> On Tuesday, 23 Oct 2018 at 19:48, stardiviner wrote:
> > This is really helpful for me, I use s
On Tue, Oct 23, 2018 at 4:34 PM John Kitchin
wrote:
>
> Matt Price writes:
>
> > On Tue, Oct 23, 2018 at 2:32 PM John Kitchin
> > wrote:
> >
> >> I think that what you really want to do here is modify org-mime-compose
> so
> >> that you can use the send-actions argument to message-mail. In
> >>
Le 24/10/2018 à 13h40, Nicolas Goaziou a écrit :
> "Garreau, Alexandre" writes:
>
>> As said in the previously mentioned stackoverflow question: helps
>> seeing where you are and how much sections are there. To me it is
>> especially useful to avoid writing manually the number of the section to
>
Hello,
stardiviner writes:
> Nicolas Goaziou writes:
>
> Hi, sorry for late response, because I'm a little lazy on give effort on
> review my patch and improve it again. But now I finished it. Actually I
> corrected my patch as soon as you replied email with mentioned. Today I
> pick up this ta
"Garreau, Alexandre" writes:
> As said in the previously mentioned stackoverflow question: helps
> seeing where you are and how much sections are there. To me it is
> especially useful to avoid writing manually the number of the section to
> know I’m currently in “exercice 8” or something alike.
On Wednesday, 24 Oct 2018 at 12:38, Roland Everaert wrote:
> Pleased to see it was helpful. The funny thing is that I use that config
> for, maybe, 10 years and never think about changing it.
I've been using emacs for well over 30 years now. You would not believe the
crud that has built up in my
I will borrow your config for the emphasis symbols, but for all the
paren-related symbols, I will keep the global mapping, so it will still
work when writing codes and the like ;)
Pleased to see it was helpful. The funny thing is that I use that config
for, maybe, 10 years and never think about
Le 24/10/2018 à 09h38, Nicolas Goaziou a écrit :
> Hello,
>
> "Garreau, Alexandre" writes:
>
>> But that doesn’t answer the question: why “doesn’t it exist”? shouldn’t
>> these functions be mainlined, if legally permitted?
>
> What kind of numbering are we talking about? A semi-permanent (i.e.,
>
Hello,
stardiviner writes:
> Garreau, Alexandre writes:
>
>> Why is there no syntax highlighting for *inline* source/code blocks?
>>
>> For instance, if I type the following:
>>
>> #+BEGIN_SRC org
>> src_emacs-lisp{(foo bar (quux))}
>> #+END_SRC
>>
>> The underscore is not displayed, “emacs”
Hello,
"Garreau, Alexandre" writes:
> But that doesn’t answer the question: why “doesn’t it exist”? shouldn’t
> these functions be mainlined, if legally permitted?
What kind of numbering are we talking about? A semi-permanent (i.e.,
togglable) naive numbering (e.g., not taking into account UNNU
Hello,
Martin Yrjölä writes:
> I have noticed my capture workflow breaking org document hierarchies.
> Here is an example:
>
> Start with the org document:
>
> * A
> * B
>
> An org capture template inserts a headline under A.
>
> * A
> ** [point here]
> * B
>
> When I navigate to the end of the
Hello,
Alexander Adolf writes:
> I was missing convert-region functions in the ox-ascii export back-end
> as are provided by the HTML, LaTeX, Texinfo, and MarkDown back-ends [1],
> and hence crafted my own (copied below) to go into my init file. My use
> case is composing emails using notmuch-me
29 matches
Mail list logo
