Bastien Guerry writes:
> Ihor Radchenko writes:
>
>> I will merge them if there are no objections.
>
> Thanks! No objections. (Sorry I moved org-syntax.org from worg/dev/
> to worg/ right before reading this email, I hope that's okay.)
Apparently git is smart enough to rebase my commits onto
Norwid Behrnd writes:
> I seek a similar fence to document a pattern in Markdown. An example would be
> a nested list such as
>
> ```markdown
> * Item 1
> * Item 2
> - Item 2a
> + Item 2a1
> - Item 2b
> * Item 3
> ```
>
> Contrasting to my anticipation, neither `C-c C-, s` followed by
Jack Kamm writes:
> If python-mode support is removed, I'd be willing to help create a new
> ob-python-mode package
Indeed. A suggestion: can you or Ihor send a help request to the
list, explaining the issue at hand and asking if someone wants to
create and maintain ob-python-mode.el?
This
Ihor Radchenko writes:
> I will merge them if there are no objections.
Thanks! No objections. (Sorry I moved org-syntax.org from worg/dev/
to worg/ right before reading this email, I hope that's okay.)
Perhaps, on top of removing Tim's comments from org-syntax.org we can
store them in a
Ihor Radchenko writes:
> I think we need to use rewrite rule here in addition to moving the file.
> If we simply move the file, old links will be broken.
Done now, thanks.
--
Bastien
Bastien writes:
> A few suggestions:
>
> - Make it a description of the syntax of the latest stable Org. (For
> now let's consider 9.6 to be the latest stable as we are working on
> releasing it soon.) Perhaps this is already the case and I missed
> it?
Yes, it should be consistent with
Ihor Radchenko writes:
> Below, I am listing my further feedback on the document.
> I encourage other Org users to look into it as well.
> This is one of the big projects that need to be finished as a
> prerequisite for registering Org format in RFC:
I have addressed the most important comments
Ihor Radchenko writes:
> I am leaning towards announcing the deprecation in the coming
> release.
Agreed, let's move forward in this direction for the release.
--
Bastien
Bastien writes:
> - Promote the page to orgmode.org/worg/org-syntax.html: the /dev/ path
> in the current URL makes it read like it is the syntax for the "dev"
> version.
I think we need to use rewrite rule here in addition to moving the file.
If we simply move the file, old links will be
Ihor Radchenko writes:
> Should we deprecate the support altogether and not bother with the extra
> maintenance? Or maybe someone want to volunteer maintaining
> python-mode.el integration?
No objections have been received.
Also, python-mode support have been broken for a long time now and no
yuvallangerontheroad writes:
>> Extra [...] are redundant.
>> Please test the patch before submitting.
>
> Sorry. Removed redundant brackets.
Thanks.
It is also a good idea to add quotes around the command key. See the
example in 25.3 Substituting Key Bindings in Documentation
(I am honestly
Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>
>> :results none are not discarded. Just not inserted and not displayed.
>> Otherwise, they can still be used, for example, during noweb
>> expansion.
>
> Gotcha!
>
> So, what do we say instead of "silenced", to avoid the expected
> confusion
Rudolf Adamkovič writes:
>> Any objections?
>
> With the existing imprecise names, "silent" (that talks) and "none"
> (that exists), we should try for maximum precision to avoid further
> confusion. Looking at your documentation, the word "discard" conveys
> the meaning better than "ignore".
Max Nikulin writes:
>> However, I feel a bit lost about what to do on Org side.
>> We can put a disclaimer in the manual and all that, but it still feels
>> too complex.
>
> My current suggestion is to provide a fallback to `downcase' in the code
> and to explain in the manual that runtime
Ihor Radchenko writes:
> The attached is a fix for this discrepancy with the manual.
>
> However, it looks like at least ob-java already tried to work around the
> erroneous return value of org-babel-read-list.
>
> Hence, we at least need to announce this fix in ORG-NEWS.
>
> Or maybe there are
Ihor Radchenko writes:
> Any objections?
With the existing imprecise names, "silent" (that talks) and "none"
(that exists), we should try for maximum precision to avoid further
confusion. Looking at your documentation, the word "discard" conveys
the meaning better than "ignore". It says that
Ihor Radchenko writes:
> :results none are not discarded. Just not inserted and not displayed.
> Otherwise, they can still be used, for example, during noweb
> expansion.
Gotcha!
So, what do we say instead of "silenced", to avoid the expected
confusion with ":results silent"?
Some ideas:
-
Dear list,
based on previous experience to fence small snippets of code in org-mode e.g.,
for Fortran in a pattern like
```org
* example Fortran (not FORTRAN 77)
#+begin_src f90 :tangle echo.f90
program test
implicit none
write (*, '(A)') "Fortran"
end program test
#+end_src
```
I
On 25/11/2022 10:56, David Zelinsky wrote:
I wanted to have some text emphasized when immediately following a
comma.
In some cases it is possible to use shy hyphen,\-/instead/ of zero width
space.
On Friday, November 25th, 2022 at 16:52, Ihor Radchenko
wrote:
> yuvallangerontheroad yuvallangeronther...@proton.me writes:
>
> > + "Narrow buffer to the current subtree.
> > +Use the command \\[[widen]] to see the whole buffer again."
>
>
> Extra [...] are redundant.
> Please test the
yuvallangerontheroad writes:
> + "Narrow buffer to the current subtree.
> +Use the command \\[[widen]] to see the whole buffer again."
Extra [...] are redundant.
Please test the patch before submitting.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
On Friday, November 25th, 2022 at 16:32, Ihor Radchenko
wrote:
> But please use `\\[widen]' instead of M-x widen. Then, Emacs will
> automatically display the actual key binding for widen or "M-x widen" if
> no binding is present.
Thank you. The change is in the attachment.From
David Zelinsky writes:
> I wanted to have some text emphasized when immediately following a
> comma. I found in the manual the suggestion to use a zero-width space
> character. That works, except that it turns out that by default emacs
> actually displays the zero-width space as 1-pixel wide.
yuvallangerontheroad writes:
> I have added information on how to exit a narrowing. I could have used this
> information when I started using org-narrow-to-subtree.
> ...
> (defun org-narrow-to-subtree ( element)
> - "Narrow buffer to the current subtree."
> + "Narrow buffer to the current
I wanted to have some text emphasized when immediately following a
comma. I found in the manual the suggestion to use a zero-width space
character. That works, except that it turns out that by default emacs
actually displays the zero-width space as 1-pixel wide. That's not
noticeable in a
I have added information on how to exit a narrowing. I could have used this
information when I started using org-narrow-to-subtree.From 680fbfc0a91552c5d73e853effadeaa683266ec9 Mon Sep 17 00:00:00 2001
From: Yuval Langer
Date: Thu, 24 Nov 2022 19:27:00 +0200
Subject: [PATCH] Explain how to
alain.coch...@unistra.fr writes:
> The last paragraph of this docstring is:
>
>It is strongly recommended that you set ‘org-cycle-max-level’ not
>at all, or to a number smaller than this one. In fact, when
>‘org-cycle-max-level’ is not set, it will be assumed to be one less
>than
The last paragraph of this docstring is:
It is strongly recommended that you set ‘org-cycle-max-level’ not
at all, or to a number smaller than this one. In fact, when
‘org-cycle-max-level’ is not set, it will be assumed to be one less
than the value of smaller than the value of
28 matches
Mail list logo
