* Re: master d8da850: Document cairo-related fallout to font-backend settings [not found] ` <20200120162050.08A5421148@vcs0.savannah.gnu.org> @ 2020-01-20 21:05 ` Stefan Kangas 2020-01-20 21:50 ` Robert Pluim 0 siblings, 1 reply; 18+ messages in thread From: Stefan Kangas @ 2020-01-20 21:05 UTC (permalink / raw) To: Emacs developers, Robert Pluim Robert Pluim <rpluim@gmail.com> writes: > +Note also that 'FontBackend' settings in .Xdefaults or .Xresources, or > +'font-backend' frame parameter settings in your init files, may need > +to be adjusted, as 'xft' is no longer a valid backend when using > +Cairo. Use either 'ftcr' or 'ftcrhb' instead for FreeType and > +FreeType + HarfBuzz respectively. 'x' is still a valid backend. Should we say that FreeType + Harfbuzz is probably the correct choice for most users, and perhaps also why? My concern is that people might default to the shorter option and we could see unnecessary bug reports about incorrect composition, etc. Best regards, Stefan Kangas ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-20 21:05 ` master d8da850: Document cairo-related fallout to font-backend settings Stefan Kangas @ 2020-01-20 21:50 ` Robert Pluim 2020-01-20 23:12 ` Stefan Kangas 2020-01-21 17:04 ` Eli Zaretskii 0 siblings, 2 replies; 18+ messages in thread From: Robert Pluim @ 2020-01-20 21:50 UTC (permalink / raw) To: Stefan Kangas; +Cc: Emacs developers >>>>> On Mon, 20 Jan 2020 22:05:23 +0100, Stefan Kangas <stefan@marxist.se> said: Stefan> Robert Pluim <rpluim@gmail.com> writes: >> +Note also that 'FontBackend' settings in .Xdefaults or .Xresources, or >> +'font-backend' frame parameter settings in your init files, may need >> +to be adjusted, as 'xft' is no longer a valid backend when using >> +Cairo. Use either 'ftcr' or 'ftcrhb' instead for FreeType and >> +FreeType + HarfBuzz respectively. 'x' is still a valid backend. Stefan> Should we say that FreeType + Harfbuzz is probably the correct choice Stefan> for most users, and perhaps also why? My concern is that people might Stefan> default to the shorter option and we could see unnecessary bug reports Stefan> about incorrect composition, etc. The correct choice depends on how their Emacs has been built; ftcr and ftcrhb are mutually exclusive [1](see my earlier update to the elisp manual). I guess we could say something like this: diff --git a/etc/NEWS b/etc/NEWS index 6cc392970f..55cf59283c 100644 --- a/etc/NEWS +++ b/etc/NEWS @@ -34,9 +34,9 @@ your font settings. Note also that 'FontBackend' settings in .Xdefaults or .Xresources, or 'font-backend' frame parameter settings in your init files, may need to be adjusted, as 'xft' is no longer a valid backend when using -Cairo. Use either 'ftcr' or 'ftcrhb' instead for FreeType and -FreeType + HarfBuzz respectively. 'x' is still a valid backend. - +Cairo. Use 'ftcrhb' if your Emacs was built with HarfBuzz support, +and 'ftcr' otherwise. You can this determine by checking +'system-configuration-features'. 'x' is still a valid backend. --- ** The ftx font backend driver has been removed. Footnotes: [1] My master plan to remove as many different variations as possible seems to get shot down every time I suggest it :-) ^ permalink raw reply related [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-20 21:50 ` Robert Pluim @ 2020-01-20 23:12 ` Stefan Kangas 2020-01-21 7:44 ` Robert Pluim 2020-01-21 14:54 ` T.V Raman 2020-01-21 17:04 ` Eli Zaretskii 1 sibling, 2 replies; 18+ messages in thread From: Stefan Kangas @ 2020-01-20 23:12 UTC (permalink / raw) To: Robert Pluim; +Cc: Emacs developers Robert Pluim <rpluim@gmail.com> writes: > The correct choice depends on how their Emacs has been built; ftcr and > ftcrhb are mutually exclusive [1](see my earlier update to the elisp > manual). I guess we could say something like this: Indeed, I read that after I wrote the above. > -Cairo. Use either 'ftcr' or 'ftcrhb' instead for FreeType and > -FreeType + HarfBuzz respectively. 'x' is still a valid backend. > - > +Cairo. Use 'ftcrhb' if your Emacs was built with HarfBuzz support, > +and 'ftcr' otherwise. You can this determine by checking > +'system-configuration-features'. 'x' is still a valid backend. Thank you, that is much better. Please install. > [1] My master plan to remove as many different variations as possible > seems to get shot down every time I suggest it :-) BTW, if 'ftcr' only works when built without HarfBuzz, and 'ftcrhb' only works with HarfBuzz, can't we just use 'ftcr' and detect HarfBuzz automatically for the user? Best regards, Stefan Kangas ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-20 23:12 ` Stefan Kangas @ 2020-01-21 7:44 ` Robert Pluim 2020-01-21 15:32 ` Eli Zaretskii 2020-01-21 14:54 ` T.V Raman 1 sibling, 1 reply; 18+ messages in thread From: Robert Pluim @ 2020-01-21 7:44 UTC (permalink / raw) To: Stefan Kangas; +Cc: Emacs developers >>>>> On Tue, 21 Jan 2020 00:12:22 +0100, Stefan Kangas <stefan@marxist.se> said: Stefan> Thank you, that is much better. Please install. Done. >> [1] My master plan to remove as many different variations as possible >> seems to get shot down every time I suggest it :-) Stefan> BTW, if 'ftcr' only works when built without HarfBuzz, and 'ftcrhb' Stefan> only works with HarfBuzz, can't we just use 'ftcr' and detect HarfBuzz Stefan> automatically for the user? I see two options: 1. give the Qftcrhb symbol the same name as Qftcr, which might do the right thing, but would make it harder to work out whether HarfBuzz is actually being used. 2. just say "If youʼre going to be modern, be modern: Cairo requires HarfBuzz" (note that this is the path that Pango is taking). Robert ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-21 7:44 ` Robert Pluim @ 2020-01-21 15:32 ` Eli Zaretskii 2020-01-21 15:39 ` Robert Pluim 0 siblings, 1 reply; 18+ messages in thread From: Eli Zaretskii @ 2020-01-21 15:32 UTC (permalink / raw) To: Robert Pluim; +Cc: stefan, emacs-devel > From: Robert Pluim <rpluim@gmail.com> > Date: Tue, 21 Jan 2020 08:44:39 +0100 > Cc: Emacs developers <emacs-devel@gnu.org> > > I see two options: > > 1. give the Qftcrhb symbol the same name as Qftcr, which might do the > right thing, but would make it harder to work out whether HarfBuzz is > actually being used. > > 2. just say "If youʼre going to be modern, be modern: Cairo requires > HarfBuzz" (note that this is the path that Pango is taking). I think 2 is the best alternative right now. I don't think we should make more radical decisions based on such incomplete experience, both with the Cairo build and with HarfBuzz. ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-21 15:32 ` Eli Zaretskii @ 2020-01-21 15:39 ` Robert Pluim 2020-01-21 15:47 ` Eli Zaretskii 0 siblings, 1 reply; 18+ messages in thread From: Robert Pluim @ 2020-01-21 15:39 UTC (permalink / raw) To: Eli Zaretskii; +Cc: stefan, emacs-devel >>>>> On Tue, 21 Jan 2020 17:32:23 +0200, Eli Zaretskii <eliz@gnu.org> said: >> From: Robert Pluim <rpluim@gmail.com> >> Date: Tue, 21 Jan 2020 08:44:39 +0100 >> Cc: Emacs developers <emacs-devel@gnu.org> >> >> I see two options: >> >> 1. give the Qftcrhb symbol the same name as Qftcr, which might do the >> right thing, but would make it harder to work out whether HarfBuzz is >> actually being used. >> >> 2. just say "If youʼre going to be modern, be modern: Cairo requires >> HarfBuzz" (note that this is the path that Pango is taking). Eli> I think 2 is the best alternative right now. I don't think we should Eli> make more radical decisions based on such incomplete experience, both Eli> with the Cairo build and with HarfBuzz. So a configure.ac patch that says 'if cairo && ! harfbuzz error_out' is pre-approved? Or did you have something else in mind? Robert ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-21 15:39 ` Robert Pluim @ 2020-01-21 15:47 ` Eli Zaretskii 2020-01-22 7:22 ` Robert Pluim 0 siblings, 1 reply; 18+ messages in thread From: Eli Zaretskii @ 2020-01-21 15:47 UTC (permalink / raw) To: Robert Pluim; +Cc: stefan, emacs-devel > From: Robert Pluim <rpluim@gmail.com> > Cc: stefan@marxist.se, emacs-devel@gnu.org > Date: Tue, 21 Jan 2020 16:39:53 +0100 > > >> I see two options: > >> > >> 1. give the Qftcrhb symbol the same name as Qftcr, which might do the > >> right thing, but would make it harder to work out whether HarfBuzz is > >> actually being used. > >> > >> 2. just say "If youʼre going to be modern, be modern: Cairo requires > >> HarfBuzz" (note that this is the path that Pango is taking). > > Eli> I think 2 is the best alternative right now. I don't think we should > Eli> make more radical decisions based on such incomplete experience, both > Eli> with the Cairo build and with HarfBuzz. > > So a configure.ac patch that says 'if cairo && ! harfbuzz error_out' > is pre-approved? Or did you have something else in mind? No, I meant to say this in the docs. Sorry for being unclear. IOW, recommend that people build with Cairo and HarfBuzz as the main configuration. ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-21 15:47 ` Eli Zaretskii @ 2020-01-22 7:22 ` Robert Pluim 2020-01-22 15:52 ` Eli Zaretskii 2020-01-22 16:53 ` Eli Zaretskii 0 siblings, 2 replies; 18+ messages in thread From: Robert Pluim @ 2020-01-22 7:22 UTC (permalink / raw) To: Eli Zaretskii; +Cc: stefan, emacs-devel >>>>> On Tue, 21 Jan 2020 17:47:21 +0200, Eli Zaretskii <eliz@gnu.org> said: >> So a configure.ac patch that says 'if cairo && ! harfbuzz error_out' >> is pre-approved? Or did you have something else in mind? Eli> No, I meant to say this in the docs. Sorry for being unclear. IOW, Eli> recommend that people build with Cairo and HarfBuzz as the main Eli> configuration. Iʼve put some stuff in NEWS to that effect. Would you be ok with configure warning about Xft and about Cairo without HarfBuzz? Robert ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-22 7:22 ` Robert Pluim @ 2020-01-22 15:52 ` Eli Zaretskii 2020-01-22 16:11 ` Robert Pluim 2020-01-22 16:53 ` Eli Zaretskii 1 sibling, 1 reply; 18+ messages in thread From: Eli Zaretskii @ 2020-01-22 15:52 UTC (permalink / raw) To: Robert Pluim; +Cc: stefan, emacs-devel > From: Robert Pluim <rpluim@gmail.com> > Cc: stefan@marxist.se, emacs-devel@gnu.org > Date: Wed, 22 Jan 2020 08:22:29 +0100 > > Would you be ok with configure warning about Xft and about Cairo > without HarfBuzz? Can you show the proposed text of the warning? ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-22 15:52 ` Eli Zaretskii @ 2020-01-22 16:11 ` Robert Pluim 2020-01-22 16:55 ` Eli Zaretskii 0 siblings, 1 reply; 18+ messages in thread From: Robert Pluim @ 2020-01-22 16:11 UTC (permalink / raw) To: Eli Zaretskii; +Cc: stefan, emacs-devel >>>>> On Wed, 22 Jan 2020 17:52:49 +0200, Eli Zaretskii <eliz@gnu.org> said: >> From: Robert Pluim <rpluim@gmail.com> >> Cc: stefan@marxist.se, emacs-devel@gnu.org >> Date: Wed, 22 Jan 2020 08:22:29 +0100 >> >> Would you be ok with configure warning about Xft and about Cairo >> without HarfBuzz? Eli> Can you show the proposed text of the warning? if test "$with_xft" = yes; then AC_MSG_WARN([This configuration uses libXft, which has a number of font rendering issues, and is being considered for removal in the next release of Emacs. Please consider using Cairo + HarfBuzz instead (they are auto-detected if the relevant development headers are installed).]) fi if test "${HAVE_CAIRO}" = "yes" && test "${HAVE_HARFBUZZ}" = no; then AC_MSG_WARN([We recommend the use of HarfBuzz when using Cairo, please install HarfBuzz development packages]) fi ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-22 16:11 ` Robert Pluim @ 2020-01-22 16:55 ` Eli Zaretskii 0 siblings, 0 replies; 18+ messages in thread From: Eli Zaretskii @ 2020-01-22 16:55 UTC (permalink / raw) To: Robert Pluim; +Cc: stefan, emacs-devel > From: Robert Pluim <rpluim@gmail.com> > Cc: stefan@marxist.se, emacs-devel@gnu.org > Date: Wed, 22 Jan 2020 17:11:30 +0100 > > Eli> Can you show the proposed text of the warning? > > if test "$with_xft" = yes; then > AC_MSG_WARN([This configuration uses libXft, > which has a number of font rendering issues, and is being considered for > removal in the next release of Emacs. Please consider using Cairo + HarfBuzz > instead (they are auto-detected if the relevant development headers are > installed).]) > fi > > if test "${HAVE_CAIRO}" = "yes" && test "${HAVE_HARFBUZZ}" = no; then > AC_MSG_WARN([We recommend the use of HarfBuzz when using Cairo, > please install HarfBuzz development packages]) > fi Sounds good, thanks. ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-22 7:22 ` Robert Pluim 2020-01-22 15:52 ` Eli Zaretskii @ 2020-01-22 16:53 ` Eli Zaretskii 2020-01-22 16:59 ` Robert Pluim 1 sibling, 1 reply; 18+ messages in thread From: Eli Zaretskii @ 2020-01-22 16:53 UTC (permalink / raw) To: Robert Pluim; +Cc: stefan, emacs-devel > From: Robert Pluim <rpluim@gmail.com> > Date: Wed, 22 Jan 2020 08:22:29 +0100 > Cc: stefan@marxist.se, emacs-devel@gnu.org > > >>>>> On Tue, 21 Jan 2020 17:47:21 +0200, Eli Zaretskii <eliz@gnu.org> said: > >> So a configure.ac patch that says 'if cairo && ! harfbuzz error_out' > >> is pre-approved? Or did you have something else in mind? > > Eli> No, I meant to say this in the docs. Sorry for being unclear. IOW, > Eli> recommend that people build with Cairo and HarfBuzz as the main > Eli> configuration. > > Iʼve put some stuff in NEWS to that effect. It looks like you did that on master. Was that intentional? ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-22 16:53 ` Eli Zaretskii @ 2020-01-22 16:59 ` Robert Pluim 2020-01-22 17:38 ` Eli Zaretskii 0 siblings, 1 reply; 18+ messages in thread From: Robert Pluim @ 2020-01-22 16:59 UTC (permalink / raw) To: Eli Zaretskii; +Cc: stefan, emacs-devel >>>>> On Wed, 22 Jan 2020 18:53:46 +0200, Eli Zaretskii <eliz@gnu.org> said: >> From: Robert Pluim <rpluim@gmail.com> >> Date: Wed, 22 Jan 2020 08:22:29 +0100 >> Cc: stefan@marxist.se, emacs-devel@gnu.org >> >> >>>>> On Tue, 21 Jan 2020 17:47:21 +0200, Eli Zaretskii <eliz@gnu.org> said: >> >> So a configure.ac patch that says 'if cairo && ! harfbuzz error_out' >> >> is pre-approved? Or did you have something else in mind? >> Eli> No, I meant to say this in the docs. Sorry for being unclear. IOW, Eli> recommend that people build with Cairo and HarfBuzz as the main Eli> configuration. >> >> Iʼve put some stuff in NEWS to that effect. Eli> It looks like you did that on master. Was that intentional? Yes. Did you want it on emacs-27? Cairo is available but not enabled by default there. Robert ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-22 16:59 ` Robert Pluim @ 2020-01-22 17:38 ` Eli Zaretskii 0 siblings, 0 replies; 18+ messages in thread From: Eli Zaretskii @ 2020-01-22 17:38 UTC (permalink / raw) To: Robert Pluim; +Cc: stefan, emacs-devel > From: Robert Pluim <rpluim@gmail.com> > Cc: stefan@marxist.se, emacs-devel@gnu.org > Date: Wed, 22 Jan 2020 17:59:17 +0100 > > >> Iʼve put some stuff in NEWS to that effect. > > Eli> It looks like you did that on master. Was that intentional? > > Yes. Did you want it on emacs-27? Cairo is available but not enabled > by default there. Ah, okay then. I guess I succeeded to confuse myself. ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-20 23:12 ` Stefan Kangas 2020-01-21 7:44 ` Robert Pluim @ 2020-01-21 14:54 ` T.V Raman 2020-01-21 15:38 ` Robert Pluim 1 sibling, 1 reply; 18+ messages in thread From: T.V Raman @ 2020-01-21 14:54 UTC (permalink / raw) To: Stefan Kangas; +Cc: Robert Pluim, Emacs developers Stefan Kangas <stefan@marxist.se> writes: Also, perhaps update frames.texi to indicate that ftcr and ftcrhb are mutually incompatible. Having both doesn't appear to hurt right now, but might perhaps cause issues later?> Robert Pluim <rpluim@gmail.com> writes: > >> The correct choice depends on how their Emacs has been built; ftcr and >> ftcrhb are mutually exclusive [1](see my earlier update to the elisp >> manual). I guess we could say something like this: > > Indeed, I read that after I wrote the above. > >> -Cairo. Use either 'ftcr' or 'ftcrhb' instead for FreeType and >> -FreeType + HarfBuzz respectively. 'x' is still a valid backend. >> - >> +Cairo. Use 'ftcrhb' if your Emacs was built with HarfBuzz support, >> +and 'ftcr' otherwise. You can this determine by checking >> +'system-configuration-features'. 'x' is still a valid backend. > > Thank you, that is much better. Please install. > >> [1] My master plan to remove as many different variations as possible >> seems to get shot down every time I suggest it :-) > > BTW, if 'ftcr' only works when built without HarfBuzz, and 'ftcrhb' > only works with HarfBuzz, can't we just use 'ftcr' and detect HarfBuzz > automatically for the user? > > Best regards, > Stefan Kangas > -- ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-21 14:54 ` T.V Raman @ 2020-01-21 15:38 ` Robert Pluim 2020-01-21 16:54 ` Robert Pluim 0 siblings, 1 reply; 18+ messages in thread From: Robert Pluim @ 2020-01-21 15:38 UTC (permalink / raw) To: T.V Raman; +Cc: Stefan Kangas, Emacs developers >>>>> On Tue, 21 Jan 2020 06:54:36 -0800, "T.V Raman" <raman@google.com> said: TVR> Stefan Kangas <stefan@marxist.se> writes: TVR> Also, perhaps update frames.texi to indicate that ftcr and ftcrhb are TVR> mutually incompatible. Having both doesn't appear to hurt right now, but TVR> might perhaps cause issues later? I updated frames.texi on emacs-27 earlier in the week along those lines. Having both doesnʼt hurt, they're not incompatible, you just can only have one or the other (and you canʼt switch between them dynamically). Robert ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-21 15:38 ` Robert Pluim @ 2020-01-21 16:54 ` Robert Pluim 0 siblings, 0 replies; 18+ messages in thread From: Robert Pluim @ 2020-01-21 16:54 UTC (permalink / raw) To: T.V Raman; +Cc: Stefan Kangas, Emacs developers >>>>> On Tue, 21 Jan 2020 16:38:01 +0100, Robert Pluim <rpluim@gmail.com> said: >>>>> On Tue, 21 Jan 2020 06:54:36 -0800, "T.V Raman" <raman@google.com> said: TVR> Stefan Kangas <stefan@marxist.se> writes: TVR> Also, perhaps update frames.texi to indicate that ftcr and ftcrhb are TVR> mutually incompatible. Having both doesn't appear to hurt right now, but TVR> might perhaps cause issues later? Robert> I updated frames.texi on emacs-27 earlier in the week along those Robert> lines. Having both doesnʼt hurt, they're not incompatible, you just can Robert> only have one or the other (and you canʼt switch between them dynamically). Let me qualify that: you can in fact use the ftcr font backend even if your emacs is built with HarfBuzz, but you need to make that decision at frame creation time. Iʼll reword NEWS and frames.texi to that effect. Robert ^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: master d8da850: Document cairo-related fallout to font-backend settings 2020-01-20 21:50 ` Robert Pluim 2020-01-20 23:12 ` Stefan Kangas @ 2020-01-21 17:04 ` Eli Zaretskii 1 sibling, 0 replies; 18+ messages in thread From: Eli Zaretskii @ 2020-01-21 17:04 UTC (permalink / raw) To: Robert Pluim; +Cc: stefan, emacs-devel > From: Robert Pluim <rpluim@gmail.com> > Date: Mon, 20 Jan 2020 22:50:27 +0100 > Cc: Emacs developers <emacs-devel@gnu.org> > > +Cairo. Use 'ftcrhb' if your Emacs was built with HarfBuzz support, > +and 'ftcr' otherwise. You can this determine by checking > +'system-configuration-features'. 'x' is still a valid backend. LGTM, except that "You can this determine" needs to switch the order of words. Thanks. ^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2020-01-22 17:38 UTC | newest] Thread overview: 18+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <20200120162048.23970.80216@vcs0.savannah.gnu.org> [not found] ` <20200120162050.08A5421148@vcs0.savannah.gnu.org> 2020-01-20 21:05 ` master d8da850: Document cairo-related fallout to font-backend settings Stefan Kangas 2020-01-20 21:50 ` Robert Pluim 2020-01-20 23:12 ` Stefan Kangas 2020-01-21 7:44 ` Robert Pluim 2020-01-21 15:32 ` Eli Zaretskii 2020-01-21 15:39 ` Robert Pluim 2020-01-21 15:47 ` Eli Zaretskii 2020-01-22 7:22 ` Robert Pluim 2020-01-22 15:52 ` Eli Zaretskii 2020-01-22 16:11 ` Robert Pluim 2020-01-22 16:55 ` Eli Zaretskii 2020-01-22 16:53 ` Eli Zaretskii 2020-01-22 16:59 ` Robert Pluim 2020-01-22 17:38 ` Eli Zaretskii 2020-01-21 14:54 ` T.V Raman 2020-01-21 15:38 ` Robert Pluim 2020-01-21 16:54 ` Robert Pluim 2020-01-21 17:04 ` Eli Zaretskii
Code repositories for project(s) associated with this external index https://git.savannah.gnu.org/cgit/emacs.git https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.