Ihor Radchenko writes:
> Will it be enough?
As long as we can point to a thread that contains all the information
and pointers that allows to quickly read Tim's comments, yes, fine.
--
Bastien
ode.el?
This way we can refer to this email on the list when announcing that
ob-python.el do not support python-mode.el anymore.
--
Bastien
hem in a dedicated Worg page? worg/dev/org-syntax-comments.org?
To make sure we can refer to a page when we want to discuss them.
--
Bastien
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
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
the resources for a project, which
I think will be (rightfully) rejected as not consistent.
Also, I believe the current state of information is okay.
--
Bastien
Ihor Radchenko writes:
> We probably need
> https://lists.gnu.org/mailman/listinfo/emacs-orgmode
Indeed, thanks for catching this, fixed.
--
Bastien
way the "Repositories" heading mentions the
main Savannah Org repository first. I hope it clarifies things a bit.
Thanks for bringing this up,
--
Bastien
t;? Other ideas?
We can announce this along with the Org 9.6 release.
Thanks,
--
Bastien
Hi Giovanni,
Giovanni Ridolfi writes:
> please find attached a patch updating the documentation file:
Sorry we overlooked this patch, thanks for it!
Applied as 225d58341 in the bugfix branch.
Best,
--
Bastien
Hi Nicolas,
Nicolas Graves via "General discussions about Org-mode."
writes:
> Patch to update some links.
Applied to worg as 9a082fc3, thanks.
--
Bastien
explicit enough: what about `org-element-heading-type-symbol'?
--
Bastien
> e.g. “Newspaper headline”).
Ah, thanks a lot for this very clear explanation!
--
Bastien
to "heading" *where it does not break anything* then see if
the proposed scenario above is workable.
In this case, I believe it's better to be partially correct (heading
where possible) than to be consistently wrong (headline everywhere) :)
WDYT?
--
Bastien
Ihor Radchenko writes:
> I came to the conclusion that it will, in fact, be easier to change all
> things to use "headline"
FWIW, I'm fine with such a change. I'm not a native english speaker,
but a "headline" sounds like it's a one-line heading, so it's okay.
--
Bastien
ouncement to the list using X-Woof-Change: 9.6 as a header.
--
Bastien
Philip Kaludercic writes:
> I am sorry, I know too little about Org and use it too superficially to
> be of much use here.
No problem, and thanks for the super quick feedback!
--
Bastien
Ihor Radchenko writes:
> Let me know if there are any objections.
None on my side, thanks for this.
--
Bastien
consider evolving
the tests so that they use Guix instead of Debian if it provides a
real benefit for our needs.
In the meantime, this test infrastructure has already proven very
useful IMHO.
Thanks,
--
Bastien
Hi,
Ihor Radchenko writes:
> Bastien, ob-asymptote is still a part of org-contrib [1].
> Should we just go ahead and change the maintainer now?
>
> [1] https://git.sr.ht/~bzg/org-contrib/tree/master/item/lisp/ob-asymptote.el
Yes, done. Thanks Jarmo for taking over the maintenance
Hi Ihor,
Ihor Radchenko writes:
> So, we should probably remove zero-width shenanigans from the code.
+1.
> Unless I miss something.
>
> Bastien, maybe you recall something about presence of null character in
> regexs?
No, I don't.
> P.S. If we decide to remove the n
Hi,
Ihor Radchenko writes:
>> In the meantime I have the paperwork done and have "it" :-)
>
> Bastien, could you please check FSF records?
Yes, I confirm Detlef is registered in the FSF records.
--
Bastien
Ihor Radchenko writes:
> Thanks for reporting!
> I am attaching tentative fix.
Applied, thanks.
> Bastien, I do not have access to orgweb repo.
Now you do :)
--
Bastien
Ihor Radchenko writes:
> Bastien, could you please add Daniel as the maintainer of
> lisp/ob-sql.el?
Done in bd468136d. Thanks Daniel!
--
Bastien
hanges as they may
create merge conflicts.
For files that do not have pending patches, we can do the replacement
with the next code-related change.
2 cts,
--
Bastien
Ihor Radchenko writes:
>> What's your opinion?
>
> I agree.
+1 (FWIW)
--
Bastien
Daniel Kraus writes:
> I think I'll go with the big `cond` above to auto-detect what's
> installed. That's probably the best out-of-the-box experience.
Indeed, thank you!
--
Bastien
Hi Ihor and Daniel,
Ihor Radchenko writes:
> If Bastien removed session support, and you do not see any justification,
> it was most likely an oversight.
>From memory, I removed session support in ob-clojure.el because it was
too buggy.
> We generally avoid feature regressi
Hi Ihor,
Ihor Radchenko writes:
> One month has passed, and I decided to apply the patch as is.
> https://git.sr.ht/~bzg/worg/commit/6fbe51dee6bf276584c24fa1e7ec673526c9326e
Thanks!
--
Bastien
ers it's cider etc?
I think this is acceptable magic: perhaps we should first check what
is done in other Babel languages and align with their level of magic
for guessing the correct executable -- but I suspect Clojure is a bit
special here, in that it has a lot of different options.
Thanks for taking care of this,
--
Bastien
Hi Daniel,
Daniel Kraus writes:
> Does anyone remember what's the status of ob-clojure session
> support?
I'm randomly connected for the next days so I won't risk a reply here,
I hope others can help.
--
Bastien
babashka is stable and
well established now, it is by far the most efficient way to run
Clojure code. Also, it is particularily suitable for Babel use.
What do you think?
--
Bastien
ore apparent to every user is still good.
--
Bastien
Hi Ihor,
Ihor Radchenko writes:
>> I have already signed the copyright assignment. (Though I used my
>> other email rudiwillalwayslove...@gmail.com when signing it.)
>
> Bastien, could you kindly check the FSF records?
Yes, I confirm the FSF record is here.
--
Bastien
n
with people implementing Org in various places (you ?).
I suggest to take this sequentially and not tackle the second work
before we're done with the first one.
2 cts,
--
Bastien
red to run the tests themselves before
submitting a patch: we don't rely on this new setup to test patches,
only to catch errors that may inadvertently slip through the cracks.
Thanks again to Christian and Ihor for setting this up!
--
Bastien
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?h=bugfix=58a46fab
I think it is good to remember that Network Theory Ltd. was the
original publisher of the printed manual, as people may find others
options online now.
--
Bastien
Ihor Radchenko writes:
> Bastien, could you take a look?
Now https://orgmode.org/orgcard.txt is back too.
--
Bastien
back in
the repo history before recreating the ASCII card.
--
Bastien
ower
vs upper case letters is way too frustrating.
But more complex rewrite rules (from old manual nodes to new ones) is
IMHO calling for trouble. What if we split the "Properties and Column"
manual page into "Properties" and "Columns"? Where to redirect?
--
Bastien
Max Nikulin writes:
> More:
Fixed, thanks!
https://git.sr.ht/~bzg/worg/commit/408f05a0
--
Bastien
Max Nikulin writes:
> rewrite /HTML-export-commands\.html HTML-export-commands.html
> permanent;
>
> Redirection loop
Fixed, thanks!
--
Bastien
Max Nikulin writes:
> Bastien, unfortunately you have not fix the problem.
You're right, I updated the nginx conf again.
Let me know if you find any remaining problem.
Thanks!
--
Bastien
Hi Max,
Max Nikulin writes:
> Bastien, I have not tried full configuration, but after a quick check
> I believe that it is a reasonable suggestion. It prevents 301
> redirection from valid URLs like
> https://orgmode.org/manual/Links-in-HTML-export.html
> to
> https://orgmo
Ihor Radchenko writes:
> AFAIK, our nginx configs are not public, but Bastien may privately share
> them if you are willing to help.
FWIW, I've shared the nginx.config here:
https://git.sr.ht/~bzg/worg/tree/master/item/nginx.conf
--
Bastien
Hi Ihor and Liu,
Ihor Radchenko writes:
>> I have signed the FSF
>> copyright assignment paper.
>
> Bastien, could you please confirm the FSF records?
I do confirm, I updated https://orgmode.org/worg/contributors.html
Liu, thanks in advance for contributing to Org!
Best,
--
Bastien
bf8e0f78ea28d63a686a286d2b2
Even better, thanks.
--
Bastien
ntries.
--
Bastien
kalathilvish...@gmail.com writes:
> Update the page on Literal Examples also 404s.
> https://orgmode.org/guide/Literal-Examples.html
Fixed too, thanks!
--
Bastien
Hi Vishal,
thanks for reporting this, this is fixed now.
Best,
--
Bastien
Fixed
--
Bastien
;every Org user out there").
It would be a good outcome to have such a forum: I'd be more comfy
recommending users to ask questions there iff they don't want/like
sharing questions on the ML than recommending them using reddit and
the like.
All best,
--
Bastien
ote about worg documentation for
> built-in babel backends. I did not even know it exist for a long time.
>
> WDYT?
+1 -- and also suggest adding tests, a part that I missed.
--
Bastien
a
few months, so that we can all focus on releasing Org 9.6.
--
Bastien
ard-like
PDF document for their libraries. But not for Org, where the refcard
is really good enough as it is, especially the Emacs sync constraints
we have right now.
Is that okay with you?
--
Bastien
ard and its
visual output.
--
Bastien
application.
> # text/x-org org;
> text/plain org;
> }
this is now done -- thanks for the reminder.
--
Bastien
to get feedback from Luc, maintainer of ob-asymptote.el
on org-contrib to decide who will maintain it, where to host it? It
seems like having ob-asymptote.el on GNU ELPA would be very good.
Let us know how it goes, thanks!
--
Bastien
depending on the time/energy you both have for
this, of course)?
Let us know how it goes!
--
Bastien
this to the existing maintainers.
> Upcoming Emacsconf may be a good opportunity.
We could also have an informal OrgConf as a one day gathering online
for bug squashing and discussing community topics like this one. :)
--
Bastien
Ihor Radchenko writes:
> Done now.
Thanks!
--
Bastien
Ihor Radchenko writes:
> The main question we need to answer is who is going to maintain that
> Discourse instance. AFAIU, Bastien is mainly concerned with the extra
> maintenance burden.
Not just this: I'm concerned with setting up a user-to-user discussion
space that reify a spli
community, please go for it -- we don't "own" the community.
We can advertize it like we do for SO and reddit here:
https://orgmode.org/worg/org-web-social.html
--
Bastien
essage should be reworked - see
https://orgmode.org/worg/org-contribute.html#commit-messages
I would recommend not using source blocks in the message.
I hope Thierry will have time to review it.
Thanks!
--
Bastien
n't think refcards should include custom keybindings.
--
Bastien
the Emacs group: https://savannah.gnu.org/git/?group=emacs
An Emacs maintainer will give you write access so that you can push
commits for ob-clojure.el directly.
When in doubt, just ask the mailing list :)
Cheers,
--
Bastien
adding the reddit/SO/X link in the
email, and mention that email in the commit message.
> If so, should this convention be added to
> https://orgmode.org/worg/org-contribute.html?
Yes, I added this on Worg as commit 1b5a8177.
--
Bastien
html/emacs-orgmode/ or
https://list.orgmode.org).
If a discussion on #org-mode or a GitHub repository is relevant for
Org development, it has to be referred to in a thread on the list,
which we can then be quoted for context in the commit message.
--
Bastien
spacemacs discord servers); for issues that are of importance for
Org core development, we should suggest them to send an email to the
list.
WDYT?
--
Bastien
Timothy writes:
> Done :)
Thanks!
--
Bastien
quot;... that's what matters in this discussion.
All best,
--
Bastien
w me to send an anonymous/pseudonymous message
to the Matrix room, right? That's what I'm talking about, that IRC
permits.
All best,
--
Bastien
stick to GNU conventions regarding creating refcards.
Also, maybe some improvements can be shared upstream against the Emacs
refcard?
--
Bastien
"Christopher M. Miles" writes:
> I agree this change too. This is more clear.
Applied on main as 52be6f0f4, thanks.
--
Bastien
Hi Christopher,
"Christopher M. Miles" writes:
> Thanks, Bastien.
(I know you sent a patch and I'll review it, no worry!)
>> Would you consider taking over the maintainance of ob-clojure.el?
>
> Thanks for invitation, I already maintained many org-mode related
> li
Ihor Radchenko writes:
> One valid option is 9.6-pre
Let's go for this one. I've add a note about our conventions for the
;; Version header in https://orgmode.org/worg/org-maintenance.html
--
Bastien
is detail.
Yes I did :)
Still, "Org mode version 9.6-pre (...)" is more accurate IMO.
--
Bastien
ding Org from a stable (ELPA) release
or from a local git repository.
WDYT?
> See the attached.
Tested and works fine, modulo the -dev part that we should keep.
Thanks!
--
Bastien
ation of trying to avoid GitHub for ethical reasons
and to be fine with working by email, the old way. Especially if we
have maintainers for small files: they certainly don't want to follow
everything in Org's development but agree to be cc'ed occasionally.
2 cts,
--
Bastien
connect to Matrix via Emacs: I will try this
myself soon.
All best,
--
Bastien
Tim Cross writes:
> FB is what their parents use and email is what their
> grandparents use!
So true, but quite painful to read on a mailing list ;)
--
Bastien
Ihor Radchenko writes:
> So, we may create a badge with an icon representing src code (maybe
> " | source code"?) that will point to
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/
+1
--
Bastien
stabilize what kind of info is expected on this
banner.
Thanks!
--
Bastien
val '(princ (lm-header "version"))'))
> GITVERSION ?= $(ORGVERSION)-g$(shell git rev-parse --short=6 HEAD)
>
> all the time.
>
> I do not know if more involved fix is required (because I am not
> familiar enough with the relevant code).
Can you provide a patch for the above suggestions? I'll test and see
if more fixes are needed, even though I'm also not that familiar with
the code either.
--
Bastien
redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
--
Bastien
/bbdb#n4750
If we can remove the complex Make machinery we have right now, I'd be
very happy. One reason for this machinery was to avoid merge conflict
(thanks to getting rid of the Version: header), but we do have these
conflicts (now that the header is back) and they are easy to solve.
--
Bastien
notes (some suggest changes in Org's grammar,
that might scare the readers a bit.)
- 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.
What do you think?
--
Bastien
n the manual to avoid such
> situations?
I propose to use inline footnotes for notes of one paragraph and to
use regular footnotes for notes spanning over more than one paragraph.
This will enhance both diffs readability and that of the manual's .org
source.
WDYT?
--
Bastien
Ihor Radchenko writes:
> s/Org-mode/Org mode
Done, thanks!
--
Bastien
Hi Timothy,
Timothy writes:
> https://github.com/tecosaur/OrgMode.jl
Great! I advertized this new parser on Worg:
https://orgmode.org/worg/org-tools/index.html
Thanks!
--
Bastien
ill the FSF copyright
assignment: https://orgmode.org/request-assign-future.txt
Thanks!
--
Bastien
g over the maintainance of ob-clojure.el?
--
Bastien
lists, having an
> infrastructure to customize list commands better will be a good thing to
> have.
Of course, I guess you can think of useful customization of list
commands -- perhaps that what we should think about first: would it be
a good thing to allow customization of list commands? what use-case?
2 cts,
--
Bastien
Ihor Radchenko writes:
> I am leaning towards removing `this-command' check, unless there are
> important reasons to keep it.
Yes, please go ahead.
--
Bastien
Ihor Radchenko writes:
> Then, I am inclined towards easing the version check to (org-version)
> instead of (org-git-version).
FWIW strong +1 here.
--
Bastien
Ihor Radchenko writes:
> May you clarify if we are following the FSF copyright assignment rules
> for test?
Yes, we should. Tests are just source code.
--
Bastien
he structure of the page while making it appear more cluttered.
IMHO if someone with UX/UI experience can/wants to interview real Org
newcomers, that will help us a lot for deciding about such tiny changes.
Best,
--
Bastien
Hi Max,
Max Nikulin writes:
> "Install from ELPA" without "GNU".
Fixed, thanks.
--
Bastien
> useful it is.
I don't know either...
Thanks,
--
Bastien
them off, insisting we should go on GitHub... but *anyone* can
send an email to a list, while only registered GitHub users can open
an issue. We certainly don't want to encourage anyone to register on
GitHub.)
--
Bastien
201 - 300 of 9927 matches
Mail list logo
