Juri Linkov writes:
> Subject: [PATCH] ob-ruby.el: Don't reuse the same buffer among different named
> sessions
>
> * lisp/ob-ruby.el (org-babel-ruby-initiate-session): Instead of
> run-ruby that always insists on using the existing buffer, use
> run-ruby-or-pop-to-buffer that allows using the
Daniele Nicolodi writes:
> On 25/11/2020 05:37, Kyle Meyer wrote:
>> Daniele Nicolodi writes:
[...]
>>> Would it be worth to mention org-sbe in the same section of the manual?
>>
>> Yeah, it looks like there's no mention of org-sbe in the manual, so I
>> think so (as a separate patch).
>
> After
Florian Dufour writes:
> Hi!
>
> I noticed one typo in org-manual.org: 'month' value for 'tree-type'
> property should not be @code{month} but only 'month'.
Good catch.
> Moreover, I added this 'month' value to org-capture-templates
> description in org-capture.el.
And this too. It looks like
Isn't the #+NAME tag used to label things below it? I think that would
explain why it doesn't work when there's nothing directly below it.
If you want to link to the heading, perhaps you should try something
like [[* heading][link]]?
On 11/22/20 3:44 PM, Dima Kogan wrote:
Hi. I'm using the
Tim,
> At the end of the day, this is essentially a supply chain problem. To
> really have confidence, you need confidence in the whole supply chain,
> not just the distribution centre.
that makes sense. thanks.
Greg
* David Rogers [2020-11-27 02:10]:
> Nothing was mentioned about keeping Org-mode simple.
Good point.
> In my opinion, this kind of “simple vs complex” discussion is like
> discussing the quality of competitive sports teams. It’s simple at one level
> Org-mode is a clever way of “leveraging”
* Ihor Radchenko [2020-11-24 10:25]:
:PROPERTIES:
:CREATED: [2020-11-27 Fri 05:40]
:ID: 7caa9f79-d5c2-4e00-8b34-60055025240e
:END:
> > Side note: there shall be feature in Org that quickly
> > captures the full link to the heading. Maybe it already
> > exists. Instead of
* Tim Cross [2020-11-27 01:21]:
>
> Greg Minshall writes:
>
> > Tim,
> >
> >> It could, but to get that level of assurance, you not only have to
> >> verify the signature is valid (something which is automated if
> >> enabled), you also need to verify that both packages have the exact
> >>
David Rogers writes:
> Jean Louis writes:
>
>> * Ihor Radchenko [2020-11-23 17:18]:
>> :PROPERTIES:
>> :CREATED: [2020-11-23 Mon 18:42]
>> :ID: edebb3e7-e755-4ecc-a5e8-a3353a3f5fd0
>> :END:
>>> Dear Jean Louis,
>>>
>>> Your description of the database reminds me how org-roam
Jean Louis writes:
* Ihor Radchenko [2020-11-23 17:18]:
:PROPERTIES:
:CREATED: [2020-11-23 Mon 18:42]
:ID: edebb3e7-e755-4ecc-a5e8-a3353a3f5fd0
:END:
Dear Jean Louis,
Your description of the database reminds me how org-roam
handles the
files - it also uses an external
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Greg Minshall writes:
> Tim,
>
>> It could, but to get that level of assurance, you not only have to
>> verify the signature is valid (something which is automated if
>> enabled), you also need to verify that both packages have the exact
>> same signature, which is pretty much a manual
Hi Jean,
Yes, Textmind is a rock tumbler for natural language thoughts. An SME
CRM treats people like widgets. The former does many small thoughtful
touches, the latter does few robotic touches. Excessive widget volume
chokes Textmind.
Sure, I will subscribe you when I have a mailing list.
Ihor Radchenko writes:
>> Only philosophy I know is that it is plain text. Is there any official
>> philosophy? I have no idea, at least manual does not give me
>> references. I cannot find "philosophy", send me references.
>
> You are right. There is no official "philosophy" in org. In my
* Texas Cyberthal [2020-11-26 19:05]:
> Hi Jean,
>
> Yes, Textmind is a rock tumbler for natural language thoughts. An SME
> CRM treats people like widgets. The former does many small thoughtful
> touches, the latter does few robotic touches. Excessive widget volume
> chokes Textmind.
>
>
On Wed, 25 Nov 2020 at 05:20, ian martins wrote:
> Something I've found challenging is the inconsistency between babel
> languages. It makes it difficult for a babel user to get a source
> block to do what they want, or for a babel developer to even know what
> correct behavior is.
>
> I'm not
> Sorry for that vague expression. Let us say I open Completions buffer
> I can switch into it, inspect it, ask for defined keys, evaluate with
> M-:, Emacs allows me to remain in the window and go to other
> window. Agenda buffer does not do that, this is probably because it
> just waits for any
* Ihor Radchenko [2020-11-25 14:48]:
> > When I do C-c a it runs (org-agenda) but I do not have "g" and I am on
> > development version. The C-c a window is made so that I cannot go with
> > cursor inside and that I cannot even expect the key map neither invoke
> > command by M-x and I cannot
* Ihor Radchenko [2020-11-26 06:34]:
> > Can I automated the execution of Babel code upon opening of the Org
> > file?
>
> Adding to other suggestions, you can always add a custom function to
> org-mode-hook instead of playing with file-local variables.
>
> > Then we comes to actual execution
Tim,
> It could, but to get that level of assurance, you not only have to
> verify the signature is valid (something which is automated if
> enabled), you also need to verify that both packages have the exact
> same signature, which is pretty much a manual process. So in addition
> to telling you
* Detlef Steuer [2020-11-26 14:46]:
> Am Thu, 26 Nov 2020 08:31:29 +0300
> schrieb Jean Louis :
>
> > That is not fair choice. It pushes user to finally ! apply and accept
> > it, but does not give chance to permanently ignore it.
> >
> >
> > Do you want to apply it? You can type
> > y -- to
Am Thu, 26 Nov 2020 08:31:29 +0300
schrieb Jean Louis :
> That is not fair choice. It pushes user to finally ! apply and accept
> it, but does not give chance to permanently ignore it.
>
>
> Do you want to apply it? You can type
> y -- to apply the local variables list.
> n -- to ignore the
On Wed, 25 Nov 2020 at 05:20, ian martins wrote:
> Something I've found challenging is the inconsistency between babel
> languages. It makes it difficult for a babel user to get a source
> block to do what they want, or for a babel developer to even know what
> correct behavior is.
>
> I'm not
* Tom Gillespie [2020-11-26 09:19]:
> > As there is the option ! to "apply local variables and permanently
> > mark these values" but there is no option "not to apply local
> > variables and permanently mark these values".
>
> I have a longer reply that I will send tomorrow, but wanted to
* Ihor Radchenko [2020-11-26 06:09]:
> Texas Cyberthal :
> > By philosophy, I mean the dev consensus on the correct way to do
> > things, and coded configuration and usability biases.
>
> According to my experience with org-mode development (I am not talking
> about third-party packages here),
* Greg Minshall [2020-11-26 08:29]:
> Tim,
>
> > I think you missed my point. There is no benefit in MELPA adopting
> > signed packages because there is no formal code review and no vetting
> > of the individuals who submit the code.
>
> it occurs to me there might be one benefit: if George,
* Greg Minshall [2020-11-26 08:34]:
> Tom,
>
> > 2. If mutt is launching Emacs, you can pass --eval "(setq
> >enable-local-eval nil)" on the command line and all file local
> >variables will be ignored and treated as plain text.
>
> maybe that is one thing that could really help here.
Located Eric's message and can confirm the same for mu4e (no query about
setting/evaluating anything upon opening the message).
cm
Eric S Fraga writes:
> On Wednesday, 25 Nov 2020 at 15:38, Jean Louis wrote:
>> I have not configured anything. In fact I have opened the email and I
>> was
28 matches
Mail list logo
