Jean Louis writes:
>> error in process sentinel: PLANTUML Preview failed: exited abnormally with
>> code 1
>>
>> The plantuml.el code seems to
>>
>>1. start a process and then
>>2. pass the plantuml string to the process.
>>
>> It is at step 2 that the error is issued.
>
> Maybe you
While we're on the subject of execution in the edit buffer, it is not
entirely clear what such execution would mean. Mirko's desire seems to
be to execute the buffer directly without org-babel as an
intermediary. However, the most consistent approach would be a command
to pop back to the source
+1 to this question. I have the exact same annoyance (would also be nice to
do some threading so it doesn't lock up emacs for a few seconds)
On Fri, Dec 4, 2020 at 2:28 PM Pankaj Jangid wrote:
> Mirko Vukovic writes:
>
> > My current workflow is
> >
> >1. Enter edit buffer (C-c ')
> >
* Mirko Vukovic [2020-12-04 22:00]:
> error in process sentinel: PLANTUML Preview failed: exited abnormally with
> code 1
>
> The plantuml.el code seems to
>
>1. start a process and then
>2. pass the plantuml string to the process.
>
> It is at step 2 that the error is issued.
Maybe
On Fri, Dec 4, 2020 at 12:41 PM Pankaj Jangid
wrote:
> Mirko Vukovic writes:
>
> > My current workflow is
> >
> >1. Enter edit buffer (C-c ')
> >2. Perform edits in the window
> >3. Exit edit mode (C-c ')
> >4. Evaluate code (C-c C-c)
> >5. Monitor changes to resulting png
Mirko Vukovic writes:
> My current workflow is
>
>1. Enter edit buffer (C-c ')
>2. Perform edits in the window
>3. Exit edit mode (C-c ')
>4. Evaluate code (C-c C-c)
>5. Monitor changes to resulting png file
>
> I would prefer instead to skip step 3, and evaluate the code
Jean Louis writes:
> * Mirko Vukovic [2020-12-04 16:59]:
>> Creating/editing UML diagrams using plantuml mode is an iterative process.
>> My current workflow is
>>
>>1. Enter edit buffer (C-c ')
>>2. Perform edits in the window
>>3. Exit edit mode (C-c ')
>>4. Evaluate code
On Friday, 4 Dec 2020 at 16:03, Jarmo Hurri wrote:
> I have an eerie feeling that this should be either
> a) fixed so that it works without inserting fragile, or
> b) written down somewhere in documentation.
> Any ideas?
This is a beamer issue and I think it is mentioned somewhere in the
beamer
* Mirko Vukovic [2020-12-04 16:59]:
> Hello,
>
> Creating/editing UML diagrams using plantuml mode is an iterative process.
> My current workflow is
>
>1. Enter edit buffer (C-c ')
>2. Perform edits in the window
>3. Exit edit mode (C-c ')
>4. Evaluate code (C-c C-c)
>5.
Hi there Eric.
Eric S Fraga writes:
>> I will take you up on that offer! Are you able to replicate the
>> difference between these two slides?
>
> Interesting. It seems that the use of =...= in one of the items makes
> org insert the "fragile" option for the frame and that allows the alltt
>
Hello,
Creating/editing UML diagrams using plantuml mode is an iterative process.
My current workflow is
1. Enter edit buffer (C-c ')
2. Perform edits in the window
3. Exit edit mode (C-c ')
4. Evaluate code (C-c C-c)
5. Monitor changes to resulting png file
I would prefer
* The issue
ob-js does not work for me, e.g.,
#+begin_src js
1 + 2
#+end_src
throws the error:
/private/var/folders/7f/s191h4q97p90374yw15ssrs0gn/T/babel-gBvsRp/js-script-zTHHhe:1
require('sys').print(require('sys').inspect(function(){
^
TypeError: require(...).print is not
When using org-capture with :clock-in or when starting the clock
manually when writing the note, then after canceling the note using
C-c C-k, the clock continues as can be seen in the modeline.
Reproduced also in a clean 'emacs -Q' setup.
Emacs : GNU Emacs 28.0.50 (build 1,
Hello,
On 2020-12-03 20:15, TRS-80 writes:
> I am also not someone who uses one of these "daily journal" workflows,
> so I can't help but wonder how you link these daily notes back to the
> underlying project that generated the event on the agenda in the first
> place. Becasue in my mind, I
Hello,
On 2020-12-03 12:01, Mikhail Skorzhisnkii writes:
> I'd suggest to use function "org-agenda-write". You can export
> your agenda views to org files too! However, the formatting will
> be different. Probably something like:
>
> * Event A
> SCHEDULED: <2020-12-03 Thu 10:00-12:00>
> *
15 matches
Mail list logo
