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 regressions:
> https://bzg.
Ihor Radchenko writes:
>> What's your opinion?
>
> I agree.
+1 (FWIW)
--
Bastien
Hi Daniel and Ihor,
Daniel Kraus writes:
> So that clarifies it for me and I do NOT indent with tabs in the
> future :)
We can progressively replace tab chars with spaces, thus re-indenting
correctly all files in the repository.
The Emacs convention is to *not* commit space-only changes as the
Ihor Radchenko writes:
> Bastien, could you please add Daniel as the maintainer of
> lisp/ob-sql.el?
Done in bd468136d. Thanks Daniel!
--
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
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
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 null character, I'd prefer
Ihor Radchenko writes:
> Let me know if there are any objections.
None on my side, thanks for this.
--
Bastien
Ihor Radchenko writes:
> Is the current news entry is sufficient?
The ORG-NEWS entry in the patch looks good, thanks.
> Or should we do something in
> addition to announce backwards-incompatible change?
I suggest to make this change visible on update.orgmode.org by sending
an announcement to
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
Timothy writes:
> Unfortunately I’m completely with you (and previous comments here). The
> meaning
> of “headline” is closer to “title” than “heading”. A document can have
> multiple
> headings but only a single headline (which is specifically the line at the
> top,
> e.g. “Newspaper headline
Ihor Radchenko writes:
> We probably need
> https://lists.gnu.org/mailman/listinfo/emacs-orgmode
Indeed, thanks for catching this, fixed.
--
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
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 dedic
Sorry for the delay.
Ihor Radchenko writes:
>> FYI, I have already cleared the FSF paperwork for an emacs patch.
>
> Bastien, could you kindly confirm?
Yes, I do confirm Pedro's FSF paperwork is in order.
Thanks!
--
Bastien
Ihor Radchenko writes:
> Bastien, could you please check Matt's copyright paperwork record in
> FSF?
Matt's copyright paperwork are OK, I added him as FSF-copyrighted
contributor on Worg.
> Does it mean that you are willing to maintain lisp/ob-shell.el?
Until Matt wants to be the maintainer fo
Hi Rudolf and Ihor,
Ihor Radchenko writes:
> Rudolf Adamkovič writes:
>
>> Ihor Radchenko writes:
>>
>>> Note that we currently have no maintainer for ob-scheme and hence can
>>> only provide very limited support. New features are hard for us
>>> without experience with scheme and geiser.
>>
>
Ihor Radchenko writes:
> Bastien, since the activity around org-info-js revived after a long
> delay, should we move the code out of worg into a separate repo?
Yes, definitely. David, would you like to set up a new repository
with the code from the org-info-js directory here:
https://git.sr.ht
Ihor Radchenko writes:
> I don't think we have an example.
> Probably, we can create etc/org-news-images folder, set :DIR: property
> in etc/ORG-NEWS to that folder, and then use attachments.
I suggest we don't go in that direction: I'd rather keep etc/ORG-NEWS
as a self-contained file.
Can we
Ihor Radchenko writes:
> Tom Gillespie writes:
>
>> From 4a78e1b5ea98dee569ff690037c661ab5c300194 Mon Sep 17 00:00:00 2001
>> From: Tom Gillespie
>> Date: Sat, 10 Dec 2022 12:11:17 -0800
>> Subject: [PATCH 1/2] ob-core: add org-confirm-babel-evaluate-cell custom
>> variable
>
> Bastien, may yo
I think it would make sense to convert Elisp lists into R lists
directly. Jeremie, would you be okay with this?
Ihor Radchenko writes:
> Or I may need to put a special clause regarding ob-R into the NEWS
> item.
... that way we don't need such a special clause regarding ob-R.
2 cts,
--
Bas
Hi Matthew,
Matt writes:
> You're correct, I've not contributed to core. I would love to
> maintain lisp/ob-shell.el.
Your wish has been granted:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e8ceb4a2
> I'm expecting life changes in the coming
> months and can't anticipate
So, based on Charles recent feedback:
>> If there are more complaints about that in the future, I'll
>> reconsider.
... let's do as Jeremie originally said: wait until someone complains.
> Note that my NEWS entry may not be accurate for ob-R then:
>
> ** List references in source block variable
Ihor Radchenko writes:
> We may, however, make `org-confirm-babel-evaluate' function value accept
> an extra third argument - context ('code or 'vars). This will retain the
> required flexibility without introducing an extra variable.
Yes, this is an interesting possibility.
> P.S. Considering
Ihor Radchenko writes:
> Bastien, may you take a look?
Applied, thanks Gerard.
--
Bastien
Tim Cross writes:
> A significant re-design of the worg styling is required in order to get
> a presentation which both looks good and which works with respect to
> accessibility requirements. I don't believe the current styles are
> workable. Someone with greater CSS fu than me might do better,
Hi,
Ihor Radchenko writes:
> I still don't understand why it was turned into a function since I
> cannot find the relevant discussion.
C-u C-c C-x d will call org-insert-property-drawer - I don't think
this function needs to be a command with its own keybinding.
The discussion is here:
https
Ihor Radchenko writes:
>> I'm not able to push to git://git.sv.gnu.org/emacs/org-mode.git.
My bad: I did not warn Emacs maintainers in time. Now it is done,
I will let you know when they grand you access to the Emacs project.
--
Bastien
Hi Greg,
Greg Minshall writes:
> but, recently i was looking at org-grep, and found its new home:
>
> https://github.com/emacsorphanage/org-grep
thanks - I added this to the org-orphanage.org page on Worg:
https://orgmode.org/worg/org-orphanage.html
Contributing to Worg is as easy as edit
Bastien writes:
> Shall I create https://git.sr.ht/~bzg/org-orphan-packages ?
Or better https://git.sr.ht/~org-orphanage/ as a new user, to where
Org orphan repos could be added.
This would mimick emacsorphanage, which is a GitHub organization.
--
Bastien
Ihor Radchenko writes:
> As for GCC-related assignment, I am not sure if it is sufficient.
I confirm that the copyright assignment should explicitely mention
EMACS as a GNU project.
--
Bastien
Hi Kaushal,
Kaushal Modi writes:
> Can a new version of Org be tagged from the bugfix branch?
Ihor, if you agree, I can release Org 9.6.1 today.
We can continue to work on Org 9.6.2 for later merge in Emacs.
The problem with `org-assert-version' can be dealt with later
on, even if many users
Ihor Radchenko writes:
> Bastien, please let me know if you have any objections.
None, thanks for taking action here.
--
Bastien
Hi,
Ihor Radchenko writes:
> Now, just waiting for confirmation from Bastien about your copyright
> status records.
Yes, I confirme Gautier's FSF copyright record is in order.
> AFAIU, the commit fixed a different scenario:
> https://orgmode.org/list/byapr07mb573496c31816fe64b71e9d70a5...@byap
Hi,
Ihor Radchenko writes:
> Bastien, could you please confirm the copyright status of Andreas
> Gerler?
I cannot find any entry with "Gerler" as a name, or with the email
"ba...@bundesbrandschatzamt.de".
Andreas, can you write me in private with a copy of the signed FSF
copyright assignment?
Hi,
Ihor Radchenko writes:
> Bastien, could you please confirm the copyright status of Andreas
> Gerler?
It was missing in the FSF copyright.list file, but it has been fixed
and Andreas can be added as a regular contributor.
Best,
--
Bastien
Hi Ihor,
Ihor Radchenko writes:
> I have recently been contacted by the current compat.el maintainer
> asking if we are willing to adapt compat.el in Org.
Very nice!
> WDYT?
As long as we keep our promise in terms of backward compatibility with
older Emacs versions, I'm all for it.
--
Bast
nfirm Damien's FSF record is in order.
--
Bastien Guerry
7;t work.
>
> AFAIK, we count separately. Org mode is a separate project, despite
> being distributed together with Emacs. At least, we usually only
> consider LOCs contributed to Org.
>
> Let me CC Bastien (the Org maintainer) to clarify.
Hopefully done, thanks!
--
Bastien Guerry
Ihor Radchenko writes:
>> 1. I have assigned my copyright for Emacs stuff to the FSF
>
> Bastien, may you please confirm?
I do, sorry for the delay.
--
Bastien Guerry
Hi,
Ihor Radchenko writes:
> Bastien, may you check the FSF records for Xi Lu?
I confirm Xi Lu FSF assignment is in order.
Thanks for contributing!
--
Bastien Guerry
Ihor Radchenko writes:
> Sure, but we need to confirm with FSF records first.
> Bastien, may you take a look?
Yes, I confirm Arash records are okay, sorry for the delay.
--
Bastien Guerry
Hi,
Ihor Radchenko writes:
> Though I do not see any commits associated with Nathaniel Nicandro or
> your email in Emacs git repo.
> Bastien, may you check FSF records?
Nathaniel's records are okay.
--
Bastien Guerry
llow
> https://orgmode.org/worg/org-maintenance.html#maintainer-role and create
> an account with write access to Org git sources.
I confirm Arne's FSF records are in order.
Thanks for your help!
--
Bastien Guerry
p with translations too.
Just let me know! And thanks in advance.
--
Bastien Guerry
he FSF copyright assignment is okay.
--
Bastien Guerry
-coded path,
>> `eval-buffer' would not be successful.
>
> Looks reasonable, but I will let Bastien decide on this. He is the
> author of this file.
LGTM too! Please go ahead, thanks,
--
Bastien Guerry
k...@akirakyle.com - please CC me if you write to Craig again so I
can follow up directly there.
Thanks!
--
Bastien Guerry
stien, may you confirm?
Yes I do, sorry for the delay.
--
Bastien Guerry
Hi Ihor,
Ihor Radchenko writes:
> Looks like accidental moderation slip.
Yes, probably, sorry for that.
I continue to moderate the list once a week.
I will ping the moderators to see if they are still available
to moderate this list or if we need to find new volunteers.
--
Bastien Guerry
Ihor Radchenko writes:
> Evgenii Klimov writes:
>
>>> Waiting for your copyright assignment before applying.
>>
>> Copyright assignment is complete.
>
> Bastien, may you confirm?
Yes I do! Thanks for the heads up.
--
Bastien Guerry
Hi Ihor and Jens,
Ihor Radchenko writes:
> Bastien, may your please check FSF records?
Done, Jens records are okay. Thanks for contributing!
--
Bastien Guerry
Ihor Radchenko writes:
> Mehmet Tekman writes:
>
>> Yep, signed and received May 10 2023, before I did my initial
>> patch submission
>>
>> RT: 1938590
>
> Bastien, may you please confirm?
Yes, I do confirm. Thanks Mehmet for contributing!
--
Bastien Guerry
Ihor Radchenko writes:
> I am attaching tentative patch that will revert demoting errors to
> messages. However, I do not fully understand the purpose of the original
> `condition-case' code in the publish.sh. Bastien?
Applied. I'm aware it only fixes part of the issue at hand, but I
believe th
oach I proposed?
> (where we export skipping errors first, upload, and then re-export,
> catching all errors this time just to trigger an email to notify about
> the failure).
Yes, let's do this.
--
Bastien Guerry
Ihor Radchenko writes:
> Akira, may I know if you managed to clear the FSF paperwork?
I've just checked and Akira's is a registered FSF contributor since
last may.
--
Bastien Guerry
the gnuplot dependency in the build manifest, hopefully
this fixes the last error I've seen.
--
Bastien Guerry
Hi Akira,
Akira Kyle writes:
> I have been informed that this document my university has
> provided is queued with the FSF legal team for eventual review.
Thanks for your answer.
I suggest we take this off-list and try to sort it out with the FSF
legal team directly.
--
Bastien Guerry
to Emacs and Org-mode. Probably your university disclaimer was enough.
--
Bastien Guerry
Ihor Radchenko writes:
> Should we try to make a call for maintenance at least for some of these
> libraries?
Definitely. We should probably prioritize files in this list, then
ask on this list *and* on the web.
Let's make sure we propose this as something fun to do, not a chore.
How do you w
oss
> examples?
Sure, please go ahead as you see fit!
--
Bastien Guerry
Ihor Radchenko writes:
> Bastien, may you please confirm Roshan's copyright status?
Yes, I do confirm Roshan is a FSF registered contributor for Emacs.
--
Bastien Guerry
Ihor Radchenko writes:
> Thanks for the clarification.
> Bastien, I think we should update the copyright status in WORG. Maybe
> also inform FSF?
I've updated the status in Worg.
--
Bastien
Ihor Radchenko writes:
> Max Nikulin writes:
>
>>> The proposed FAQ entry is overwhelming. It would work fine as a blog,
>>
>> A blog with a couple of posts a year has a little sense. Moreover it is
>> closer to a wiki article because it is supposed to be updated. That is
>> why I asked for an
luate some R code blocks, fails, and gives up.
Yes. I hope other Org/ESS/R users on this list will help fixing these
documentation issues on WORG.
--
Bastien Guerry
Ihor Radchenko writes:
> Max Nikulin writes:
>
>>> Sure. This is not by itself a big deal. A number of Elisp libraries,
>>> including built-in Emacs libraries are loaded with side effects.
>>
>> It is still violation of conventions:
>>
>> (info "(elisp) Coding Conventions")
>> https://www.gnu.or
correctness as an excuse.".
Defining new functions is a desirable "side-effect" of all Elisp
library, I don't think we should worry abou this.
--
Bastien Guerry
ed a set of links that are all to be inserted, or
>>>>such. although idk if the mechanism supports.
I'm in favor of option (2) as it deals with the above use-case, and
storing a link for each lines in the active region should be the
default behavior anyway, with no need for a prefix arg.
WDYT?
--
Bastien Guerry
me for features like org-mouse.el
and org-inlinetask.el and for core features like Babel libs and links.
For the former, a decision should be made relatively to the usefulness
of the feature; for the latter, loading libs (with side-effects on the
syntax) is required by the design of the core feature at hand (Babel
and links).
I'd focus on solving the problem with org-mouse and org-inlinetasks
first. Let's make a poll for org-mouse.el then for org-inlinetasks.el ?
--
Bastien Guerry
inner » » style to be correctly implemented in, say, HTML, and
since, even in LaTeX, babel-french defaults to the « “inner” » style,
I suggest we stick to the « “inner” » style (this is a defcustom and
users can change it.)
Thanks!
--
Bastien Guerry
Hi Ihor,
Thanks for bearing with me while I discuss something is done, required
time and work, and isn't probably a priority.
Ihor Radchenko writes:
> Bastien Guerry writes:
>
>> (1) by always store the latest link on top and remove old dups.
>>
>> (2) always sto
ODO inlinetask
> ***> TODO inlinetask
> ...
+1 on this one.
> *> TODO inlinetask
> Inlinetask contents
> *> END
-1 on this one -- I'd rather get rid of the
* TODO ...
* END
construct altogether.
--
Bastien Guerry
to the « “inner” » style (this is a defcustom and
>> users can change it.)
>
> Are you referring to `org-export-smart-quotes-alist'? It is a defconst.
Ah, indeed. I'd say using a defcustom here would be useful.
--
Bastien Guerry
hen relying on engrave-faces, which is maintained and also
handles LaTeX, instead of htmlize, sounds like a good idea.
2 cts,
--
Bastien Guerry
ces already does a better job than htmlize.el,
and does it for LaTeX too, I see no drawback in using engrave-faces as
a replacement of htmlize.el. Are there any?
--
Bastien Guerry
ed the
>> TINYCHANGE comment. The attached patch should finally work.
>
> Bastien, may you please check the FSF records?
I did, I'll provide more information offlist.
--
Bastien Guerry
Ihor Radchenko writes:
> Bastien Guerry writes:
>
>>> Are you referring to `org-export-smart-quotes-alist'? It is a defconst.
>>
>> Ah, indeed. I'd say using a defcustom here would be useful.
>
> Is changing defconst to defcustom ok for bugfix?
N
s more
> sense, IMHO.
Indeed.
So I was not that stupid when I added this C-u C-u C-u option :)
Thanks!
--
Bastien Guerry
Ihor Radchenko writes:
> Bastien Guerry writes:
>
>> If not, then relying on engrave-faces, which is maintained and also
>> handles LaTeX, instead of htmlize, sounds like a good idea.
>
> I'd like to hear Timothy's opinion on this. He is the author of
> e
Ihor Radchenko writes:
> I notice that the old https://orgmode.org/contribute.html is still lying
> around. Should we remove it? Or put a redirect?
I've put a redirect to https://orgmode.org/worg/org-contribute.html
and removed the old page.
Thanks!
--
Bastien Guerry
Ihor Radchenko writes:
> Applied, onto main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6954fe93e
Thanks!
--
Bastien Guerry
Ihor Radchenko writes:
> Bastien Guerry writes:
>
>>>>> Are you referring to `org-export-smart-quotes-alist'? It is a defconst.
>>>>
>>>> Ah, indeed. I'd say using a defcustom here would be useful.
>>>
>>> Is changing
How does that sound?
Sounds good to me too, I'm "bzg" on GitHub. Thanks!
--
Bastien Guerry
asks users will feel the same once they use drawers.
--
Bastien Guerry
oms.
Yes, sounds good!
--
Bastien Guerry
ask, but rather its "target", but inline task does
not seem to add much here.
--
Bastien Guerry
> Also, pdf export of such inlinetask will nicely mark the TODO item in
> the manuscript draft, so that I can print things, and still see what
> should be done in that particular location of the manuscript.
Yes, I see.
--
Bastien Guerry
ward when the
> section has multiple screens of text.
And what about this?
** Section X
<...>
*** TODO Task for paragraph N
<...>
<...>
--
Bastien Guerry
as for an
external module, not for something we support in Org's core IMHO.
--
Bastien Guerry
n: inline tasks _look like_ normal
tasks while behaving differently.
--
Bastien Guerry
ks are widely used,
and if so, for what specific purpose. Again, if the core feature is
to prevent some headings from being exported, then other approaches
can be explored.
--
Bastien Guerry
Jonas Bernoulli writes:
> Please make your "membership" public at
> https://github.com/orgs/emacsorphanage/people.
Done, thanks!
--
Bastien Guerry
pice.git in response to
>>>>> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
>>>>>
>>>>> But org-contrib still contains that file and the README at the new
>>>>> location still contains
>
> Bastien, it looks like we can now remove ob-spice from org-contrib.
> Please, confirm.
I do, thanks.
--
Bastien Guerry
Ihor Radchenko writes:
> Committed. Note that ob-spice was _not_ listed in the README.
> https://git.sr.ht/~bzg/org-contrib/commit/be51e9833b4f3393f4003c88131ba0a0a172c10d
Indeed!
> We may consider tagging a new release.
Yes, please go ahead as you see fit.
--
Bastien Guerry
Ihor Radchenko writes:
> Maske writes:
>
>> There are some links, that I am afraid don't work:
>> ...
>> ‘constants.el’ by Carsten Dominik [...]
>> http://www.astro.uva.nl/~dominik/Tools.
>>
>>
>> # That link is dead. Maybe this would be the correct one:
>> https://staff.fnwi.uva.nl/c.dominik/
I've updated the script so that
it now uses the hut utility (see https://git.sr.ht/~emersion/hut)
and tests are running again.
--
Bastien Guerry
Ihor Radchenko writes:
> Bastien Guerry writes:
>
>> I see no reason not to use
>> https://github.com/cdominik/constants-for-Emacs as the source for
>> constants.el, the package seems stable (as its name suggests...)
>
> I was mostly concerned that a pull request
Hi Ihor,
Ihor Radchenko writes:
> May you also check if new commits in Org repo still trigger the check?
New commits in Org repo don't trigger the checks directly.
Instead, there is a cron job running every three hours and running the
checks iff there are new commits.
> https://lists.sr.ht/~b
t, things are kept in sync every 3 hours.
--
Bastien Guerry
Ihor Radchenko writes:
> It does not look like there is any improvement.
Yes, something is wrong with cron. I'll have a look this week-end,
I don't have a stable connection right now.
--
Bastien Guerry
401 - 500 of 585 matches
Mail list logo
