On Sat, Nov 05 2022, Ihor Radchenko wrote:
> Mmm.. By manually checking magit log. It can provide extra highlight for
> things that have been changed and also moved around (which is more
> accurate than raw LOC count from git).
>
> And I missed one of the aikrahguzar's commits. With f41befa,
Joost Kremers writes:
>> aikrahguzar -- TINYCHANGE
>
> How did you determine this, if I may ask? aikrahguzar's contribution at first
> sight seems more involved, though I admit part of those changes is stuff being
> moved around.
Mmm.. By manually checking magit log. It can provide extra
On Thu, Nov 03 2022, Ihor Radchenko wrote:
> The rules are in
> https://www.gnu.org/prep/maintain/maintain.html#Legally-Significant
>
> Shuguang Sun contributed TINYCHANGE (no need for copyright assignment;
>though he contributed ~15LOC and it is on the edge)
> Martin R. Albrecht also
Joost Kremers writes:
> On Sun, Oct 30 2022, Ihor Radchenko wrote:
>> May I know if there is any update on the copyright assignment situation?
>> If you need any help, we can provide it.
>
> I have signed the form and sent it in, and I have received the counter-signed
> form back from the FSF.
On Sun, Oct 30 2022, Ihor Radchenko wrote:
> May I know if there is any update on the copyright assignment situation?
> If you need any help, we can provide it.
I have signed the form and sent it in, and I have received the counter-signed
form back from the FSF.
Parsebib's Github page mentions
Joost writes:
> On Thu, 28 Jul 2022, at 14:12, Ihor Radchenko wrote:
>> Did you manage to get the copyright form from FSF?
>> They are supposed to respond within 5 working days.
>
> Yeah, I have the form. I signed it and scanned it, just haven't sent it off
> yet...
May I know if there is any
alain.coch...@unistra.fr writes:
> alain.coch...@unistra.fr writes on Sat 9 Jul 2022 08:10:
>
> > the examples I found on this mailing list did not work for me).
>
> I think I now understand why this was so: because latexmk was not
> installed on my system. In this case the docstring of
>
On Thu, 28 Jul 2022, at 14:12, Ihor Radchenko wrote:
> Did you manage to get the copyright form from FSF?
> They are supposed to respond within 5 working days.
Yeah, I have the form. I signed it and scanned it, just haven't sent it off
yet...
--
Joost Kremers
Life has its moments
Joost Kremers writes:
> On Tue, Jul 19 2022, Bruce D'Arcus wrote:
>>> So does this mean there is no longer any reason to add parsebib to (Non-)GNU
>>> ELPA?
>>
>> No, since parsebib is an important dependency for citeproc-el, and
>> Ihor was suggesting Andras try to get that in ELPA.
>
> Ok,
On Tue, Jul 19 2022, Bruce D'Arcus wrote:
>> So does this mean there is no longer any reason to add parsebib to (Non-)GNU
>> ELPA?
>
> No, since parsebib is an important dependency for citeproc-el, and
> Ihor was suggesting Andras try to get that in ELPA.
Ok, thanks. Sending my copyright
On Tue, Jul 19, 2022 at 4:37 PM Joost Kremers wrote:
>
>
> On Sun, Jul 17 2022, Ihor Radchenko wrote:
> > alain.coch...@unistra.fr writes:
> >
> >> My .bib file is
> >>
> >>@string{jgr="J. Geophys. Res."}
> >>@ARTICLE{chouet88,
> >>journal=jgr,
> >>author={Chouet, B.},
On Sun, Jul 17 2022, Ihor Radchenko wrote:
> alain.coch...@unistra.fr writes:
>
>> My .bib file is
>>
>>@string{jgr="J. Geophys. Res."}
>>@ARTICLE{chouet88,
>>journal=jgr,
>>author={Chouet, B.}, title={Resonance of a fluid-driven crack: [...]},
>>year={1988}, volume={93},
Ihor Radchenko writes on Sun 17 Jul 2022 16:26:
> Fixed on main via c550a4290.
>
> After discussion with Emacs devs, it turned out that there is a way to
> make bibtex.el parse and substitute @string abbreviations.
I don't know what "Fixed on main via c550a4290" means, but I just made
a
alain.coch...@unistra.fr writes:
> My .bib file is
>
>@string{jgr="J. Geophys. Res."}
>@ARTICLE{chouet88,
>journal=jgr,
>author={Chouet, B.}, title={Resonance of a fluid-driven crack: [...]},
>year={1988}, volume={93}, number={B5}, pages={4375-4400}
Fixed on main via
alain.coch...@unistra.fr writes on Sat 9 Jul 2022 08:10:
> the examples I found on this mailing list did not work for me).
I think I now understand why this was so: because latexmk was not
installed on my system. In this case the docstring of
org-latex-pdf-process says that
Its value is
On Tue, 12 Jul 2022 at 13:36, John Kitchin wrote:
> Maybe it is still needed so the tooltip looks nice.
currently, oc-basic.el contains the single activation (fontification)
processor (called "basic") shipped with Org, the other oc-*.el files
provide only export processors.
best wishes,
Maybe it is still needed so the tooltip looks nice.
On Tue, Jul 12, 2022 at 7:15 AM András Simonyi
wrote:
> Dear All,
>
> On Sun, 10 Jul 2022 at 09:17, Ihor Radchenko wrote:
>
> > AFAIU, oc-natbib/oc-bibtex also do not support @string because they also
> > rely upon the built-in Emacs parser
Dear All,
On Sun, 10 Jul 2022 at 09:17, Ihor Radchenko wrote:
> AFAIU, oc-natbib/oc-bibtex also do not support @string because they also
> rely upon the built-in Emacs parser for bib files.
> I have submitted a bug report to Emacs devs [1]. Hopefully it can be
> fixed on Emacs side without a
Dear All,
On Mon, 11 Jul 2022 at 04:05, Ihor Radchenko wrote:
> >> Then, I am wondering if parsebib can be added to ELPA or at least
> >> non-GNU ELPA. The same can be said for all other dependencies of
> >> citeproc.el and for citeproc itself.
> non-GNU ELPA is also fine. The idea is to avoid
Joost Kremers writes:
>>> looking into the source code (parsebib.el), the library seems to be
>>> under a BSD-type license.
>
> Yes, it is. It's a single file and the license is at the top. I can add a
> separate license file if that's necessary.
It is not required. Just a bit confusing -
On Sun, Jul 10 2022, Ihor Radchenko wrote:
> András Simonyi writes:
>
>>> The problem with parsebib is that it does not even have license
>>> (I do not see any in https://github.com/joostkremers/parsebib). If
>>> parsebib were a part of Emacs core or at least a part of ELPA, we would
>>> also
András Simonyi writes:
>> The problem with parsebib is that it does not even have license
>> (I do not see any in https://github.com/joostkremers/parsebib). If
>> parsebib were a part of Emacs core or at least a part of ELPA, we would
>> also be able to use it in Org core.
>
> looking into the
alain.coch...@unistra.fr writes:
> Is someone using natbib/bibtex (say) expected to never ever use
> 'basic'? (I don't know.) If so, perhaps there is indeed no need to
> implement the feature. Otherwise, it seems to me that not
> implementing it amounts to having to give up on @string
On Sat, Jul 9, 2022 at 2:10 AM wrote:
> I take the opportunity to say that I think that the simple
> self-contained example
>
>#+bibliography: references.bib
>[cite:@key]
>#+print_bibliography:
>
> should be part of the manual, especially since the
> 2021-07-31-citations post does
Dear All,
On Sat, 9 Jul 2022 at 05:55, Ihor Radchenko wrote:
> The problem with parsebib is that it does not even have license
> (I do not see any in https://github.com/joostkremers/parsebib). If
> parsebib were a part of Emacs core or at least a part of ELPA, we would
> also be able to use it
Bruce D'Arcus writes on Fri 8 Jul 2022 08:05:
> On Fri, Jul 8, 2022 at 7:25 AM wrote:
>
> > As I do not know which of these alternatives
> >
> >- it is normal, this feature should not be there,
> >- it is an oversight,
> >- this feature is not implemented yet,
>
> I
"Bruce D'Arcus" writes:
> On Fri, Jul 8, 2022 at 7:25 AM wrote:
>
>> As I do not know which of these alternatives
>>
>>- it is normal, this feature should not be there,
>>- it is an oversight,
>>- this feature is not implemented yet,
>
> I believe this is the answer, and it's
On Fri, Jul 8, 2022 at 7:25 AM wrote:
> As I do not know which of these alternatives
>
>- it is normal, this feature should not be there,
>- it is an oversight,
>- this feature is not implemented yet,
I believe this is the answer, and it's arguable (I have no opinion,
and could see
Hello.
As I do not know which of these alternatives
- it is normal, this feature should not be there,
- it is an oversight,
- this feature is not implemented yet,
- it does not work for me for some reason,
- other,
is valid, I decided to report this minor issue.
Specifically, I
29 matches
Mail list logo
