Thanks for all your feedback.
On 2023-01-04 05:58 Tim Cross wrote:
> argue that =text= should be rendered as text
I did this before but then got them as paragraphs. Not sure how the
correct term of this is in HTML. pre is not inline but handled as an
own paragraph so that you have an extra line
David Masterson writes:
> "Fraga, Eric" writes:
>> On Sunday, 1 Jan 2023 at 13:43, Ihor Radchenko wrote:
>>> I think that it is not very clear how to use it.
>>> Abstract says that it is self-explaining, but it appears that not every
>>> pdf viewer supports showing the explanations.
>>
>> Yes, th
On 2023-01-03, at 19:29, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>> I see. I think I'll go another route then - in fact, I already started,
>> see https://mbork.pl/2023-01-02_Computing_Org_mode_TODO_stats :-)
>
> That will also work.
>
> But why `plist-get' + `org-element-at-point-
"Fraga, Eric" writes:
> On Monday, 2 Jan 2023 at 19:23, David Masterson wrote:
>> Um, when I viewed it in my Emacs pdfviewer, it appeared to look fine
>> *EXCEPT* that it appeared to be in Latin (good Latin, I think, but I
>> don't read Latin).
>
> it's not the text of the document that matters;
Hi Rudolf,
Rudolf Adamkovič writes:
> So, my use of Scheme drops from 8 hours per day to effectively 0,
> effective today. As a result, I would like to kindly ask you to revert
> the change, for without actively using something, I cannot maintain it.
Sure, done.
> That said, if my employer ch
Bastien Guerry writes:
> I just added you as the maintainer of ob-scheme.el.
A sudden turn of events:
My employer have just decided that we will convert all Scheme to Fennel,
a zero-runtime Lisp based on Lua, because it has a better bus factor,
meaning that, in the worst-case, the company can c
writes:
> Hi,
>
> in org you can have inline verbatim and code text elements like this.
>
> Example with =verbatim= and ~code~.
>
> I would like to understand what "verbatim" really means. What is the
> semantic behind it? What content should go in there?
>
>
> I'm aware of the separation o
Marcin Borkowski writes:
> I see. I think I'll go another route then - in fact, I already started,
> see https://mbork.pl/2023-01-02_Computing_Org_mode_TODO_stats :-)
That will also work.
But why `plist-get' + `org-element-at-point-no-context'?
You can instead use `org-element-property' + `or
On 2022-12-27, at 08:48, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>>> If you have interest, going through org-colview.el code would be
>>> helpful. It is a bit messy and deserves more cleaning and commenting.
>>
>> Since org-colview is pretty long, I decided to look into the manual
>
c.bu...@posteo.jp [2023-01-03 Tue 13:20] wrote:
> in org you can have inline verbatim and code text elements like this.
>
> Example with =verbatim= and ~code~.
>
> The org html export to create both with tag. So in HTML output
> there is no difference between verbatim and code anymore.
>
> I
release_9.6-193-g30314c
A right after 'M-x org-inlinetask-insert-task' adds a star to
the 15 already there; another , another star, and so on. Same
thing with cursor after a TODO keyword.
The behavior is the same if there is some content inside the
inlinetask (i.e., not on the 1st line).
--
Hi,
in org you can have inline verbatim and code text elements like this.
Example with =verbatim= and ~code~.
I would like to understand what "verbatim" really means. What is the
semantic behind it? What content should go in there?
I'm aware of the separation of content and its presentatio
On Tue, 03 Jan 2023 05:50:17 -0500 Ihor Radchenko wrote ---
> I was mostly worried about session states affecting subsequent test
> invocations. But I do agree that it may be better to keep them.
That makes sense. I tend to run tests one at a time unless I'm about to submit
patches
Ihor Radchenko writes:
> I am afraid that maintaining both etc/ORG-NEWS and also worg/news.org
> will be a bit too much.
Maintaining etc/ORG-NEWS is the responsability of maintainers.
Adding useful (possibly visual) informations on Worg is the task of
the community.
Of course, the work people
On Tue, 3 Jan 2023, 09:23 Max Nikulin, wrote:
> On 03/01/2023 17:01, Eduardo Ochs wrote:
> >
> > Can you send to me - here to the mailing list - a version of
> > `org-export-dispatch', and also of other functions if needed, in which
> > the parts that call `read-char-exclusive' are replaced by so
On 03/01/2023 17:01, Eduardo Ochs wrote:
Can you send to me - here to the mailing list - a version of
`org-export-dispatch', and also of other functions if needed, in which
the parts that call `read-char-exclusive' are replaced by something
non-blocking?
Eduardo, I am sorry, but from my opinio
Tim Cross writes:
> I would still like to get back to this, but right now, don't know where
> things are likely to be in the short term. There are some job related
> things which will be eitehr completed or stepped up to the next stage by
> mid Feb and I may have a clearer picture by then. For no
Tim Cross writes:
>> 1. Introduce a new customization `org-confirm-evaluate-safe-regexps'
>>listing regexps that are considered safe or cons cells
>>(src-body/header-arg/table/macro/diary . regexp)
>>
>> 2. Introduce a new customization `org-confirm-evaluate' that can be set
>>to t/ni
Matt writes:
> On Mon, 02 Jan 2023 04:47:10 -0500 Ihor Radchenko wrote ---
> > They will not be reliable when tests are executed interactively.
> > If the `should' condition fails, `kill-buffer' will never be executed
> > leaving dirty state, especially for sessions.
>
> From my persp
Bastien writes:
> To be sure that we are not miscommunicating, my point is that we can
> advertize https://orgmode.org/worg/org-orphanage.html as a place where
> anyone can document orphan Org packages, then once there are enough
> packages on this page, we can try solving the other problem, that
Bastien writes:
> Still, etc/ORG-NEWS should stick to being text only.
>
> What about a new worg/news.org file with a timeline with new stuff,
> along with pictures?
I am afraid that maintaining both etc/ORG-NEWS and also worg/news.org
will be a bit too much. Though maybe one can be a source for
On Tue, 3 Jan 2023 at 06:47, Ihor Radchenko wrote:
>
> Eduardo Ochs writes:
>
> > (3) _is_ my experience with the Org mailing list.
> >
> > What I meant by "the developers like your questions" was roughly:
> > "recognizing that that person deserves help, and giving him tools that
> > would let hi
Greg Minshall writes:
> one additional item (i don't *think* we discussed this before; apologies
> if i'm forgetting): tangling. if one is prompted to "merely" tangle ...
>
> #+begin_src sh :tangle /var/tmp/foo.org.tangled
> echo 'hi!'
> #+end_src
>
>
> one could imagine more siniste
Eduardo Ochs writes:
> (3) _is_ my experience with the Org mailing list.
>
> What I meant by "the developers like your questions" was roughly:
> "recognizing that that person deserves help, and giving him tools that
> would let him solve his problems in hours instead of in months or
> years".
>
>
Matt writes:
> On Sat, 31 Dec 2022 07:56:10 -0500 Ihor Radchenko wrote ---
> > As for being a macro, there will be not much gain - the convention is
> > mostly designed for things like `cl-defun' aimed to be used in the code.
> > `org-babel-shell-initialize' is only used by `org-babe
On Monday, 2 Jan 2023 at 19:23, David Masterson wrote:
> Um, when I viewed it in my Emacs pdfviewer, it appeared to look fine
> *EXCEPT* that it appeared to be in Latin (good Latin, I think, but I
> don't read Latin).
it's not the text of the document that matters; it's the popups that
describe h
Marc Nieper-Wißkirchen writes:
>> Thanks!
>> Note that your patch does not apply onto main.
>
> Rebased against the latest main. Please see the appended patch.
Hmm.
Not sure what is going on here, but I am getting
128 git … am --3way --
/tmp/0001-lisp-ob-scheme.el-Do-not-hide-Scheme-evaluatio
27 matches
Mail list logo
