* Re: 23.0.60; gs.el - This code is experimental. Don't use it.
@ 2008-12-09 23:51 Chong Yidong
2009-01-10 5:10 ` bug#1524: " Leo
2009-01-10 5:10 ` Leo
0 siblings, 2 replies; 14+ messages in thread
From: Chong Yidong @ 2008-12-09 23:51 UTC (permalink / raw
To: emacs-devel; +Cc: 1524, Leo
> I really have no idea what gs.el does. The code looks sketchy leading me
> to believe the comment in its header actually is true.
>
> This code is experimental. Don't use it.
Looks like cruft to me too.
Does anyone object to removing this file?
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#1524: 23.0.60; gs.el - This code is experimental. Don't use it. 2008-12-09 23:51 23.0.60; gs.el - This code is experimental. Don't use it Chong Yidong @ 2009-01-10 5:10 ` Leo 2009-01-10 5:10 ` Leo 1 sibling, 0 replies; 14+ messages in thread From: Leo @ 2009-01-10 5:10 UTC (permalink / raw To: Chong Yidong; +Cc: 1524, emacs-devel On 2008-12-09 23:51 +0000, Chong Yidong wrote: >> I really have no idea what gs.el does. The code looks sketchy leading me >> to believe the comment in its header actually is true. >> >> This code is experimental. Don't use it. > > Looks like cruft to me too. > > Does anyone object to removing this file? I think it is safe to remove (info "(elisp)PostScript Images") and gs.el now that over a month has passed. Best, Leo ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: 23.0.60; gs.el - This code is experimental. Don't use it. 2008-12-09 23:51 23.0.60; gs.el - This code is experimental. Don't use it Chong Yidong 2009-01-10 5:10 ` bug#1524: " Leo @ 2009-01-10 5:10 ` Leo 2009-01-10 13:22 ` Chong Yidong 2009-01-10 13:22 ` Chong Yidong 1 sibling, 2 replies; 14+ messages in thread From: Leo @ 2009-01-10 5:10 UTC (permalink / raw To: Chong Yidong; +Cc: 1524, emacs-devel On 2008-12-09 23:51 +0000, Chong Yidong wrote: >> I really have no idea what gs.el does. The code looks sketchy leading me >> to believe the comment in its header actually is true. >> >> This code is experimental. Don't use it. > > Looks like cruft to me too. > > Does anyone object to removing this file? I think it is safe to remove (info "(elisp)PostScript Images") and gs.el now that over a month has passed. Best, Leo ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-10 5:10 ` Leo @ 2009-01-10 13:22 ` Chong Yidong 2009-01-11 3:51 ` Leo 2009-01-11 3:51 ` Leo 2009-01-10 13:22 ` Chong Yidong 1 sibling, 2 replies; 14+ messages in thread From: Chong Yidong @ 2009-01-10 13:22 UTC (permalink / raw To: Leo; +Cc: 1524, emacs-devel Leo <sdl.web@gmail.com> writes: > I think it is safe to remove (info "(elisp)PostScript Images") and > gs.el now that over a month has passed. It's used in image.c. We should probably try to fix it if it doesn't work properly. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-10 13:22 ` Chong Yidong @ 2009-01-11 3:51 ` Leo 2009-01-11 14:57 ` bug#1524: " Stefan Monnier 2009-01-11 14:57 ` Stefan Monnier 2009-01-11 3:51 ` Leo 1 sibling, 2 replies; 14+ messages in thread From: Leo @ 2009-01-11 3:51 UTC (permalink / raw To: Chong Yidong; +Cc: 1524, emacs-devel On 2009-01-10 13:22 +0000, Chong Yidong wrote: > Leo <sdl.web@gmail.com> writes: > >> I think it is safe to remove (info "(elisp)PostScript Images") and >> gs.el now that over a month has passed. > > It's used in image.c. We should probably try to fix it if it doesn't > work properly. I don't use it so I don't know whether it has bugs. I suspect it has. But I'm mostly concerned by the comment in the source which advise users not to use it. Best, Leo ^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#1524: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-11 3:51 ` Leo @ 2009-01-11 14:57 ` Stefan Monnier 2009-01-11 14:57 ` Stefan Monnier 1 sibling, 0 replies; 14+ messages in thread From: Stefan Monnier @ 2009-01-11 14:57 UTC (permalink / raw To: Leo; +Cc: Chong Yidong, kastrup, 1524, emacs-devel >>> I think it is safe to remove (info "(elisp)PostScript Images") and >>> gs.el now that over a month has passed. >> It's used in image.c. We should probably try to fix it if it doesn't >> work properly. > I don't use it so I don't know whether it has bugs. I suspect it > has. But I'm mostly concerned by the comment in the source which advise > users not to use it. IIRC David Kastrup would know how broken it is. Stefan ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-11 3:51 ` Leo 2009-01-11 14:57 ` bug#1524: " Stefan Monnier @ 2009-01-11 14:57 ` Stefan Monnier 2009-02-04 15:56 ` Leo ` (3 more replies) 1 sibling, 4 replies; 14+ messages in thread From: Stefan Monnier @ 2009-01-11 14:57 UTC (permalink / raw To: Leo; +Cc: Chong Yidong, kastrup, 1524, emacs-devel >>> I think it is safe to remove (info "(elisp)PostScript Images") and >>> gs.el now that over a month has passed. >> It's used in image.c. We should probably try to fix it if it doesn't >> work properly. > I don't use it so I don't know whether it has bugs. I suspect it > has. But I'm mostly concerned by the comment in the source which advise > users not to use it. IIRC David Kastrup would know how broken it is. Stefan ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-11 14:57 ` Stefan Monnier @ 2009-02-04 15:56 ` Leo 2009-02-04 15:56 ` bug#1524: " Leo ` (2 subsequent siblings) 3 siblings, 0 replies; 14+ messages in thread From: Leo @ 2009-02-04 15:56 UTC (permalink / raw To: Stefan Monnier; +Cc: Chong Yidong, 1524, kastrup, Leo, emacs-devel 2009/1/11 Stefan Monnier <monnier@iro.umontreal.ca>: >>>> I think it is safe to remove (info "(elisp)PostScript Images") and >>>> gs.el now that over a month has passed. >>> It's used in image.c. We should probably try to fix it if it doesn't >>> work properly. >> I don't use it so I don't know whether it has bugs. I suspect it >> has. But I'm mostly concerned by the comment in the source which advise >> users not to use it. > > IIRC David Kastrup would know how broken it is. Ping? > Stefan > ^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#1524: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-11 14:57 ` Stefan Monnier 2009-02-04 15:56 ` Leo @ 2009-02-04 15:56 ` Leo 2009-02-04 16:16 ` Leo 2009-02-04 16:16 ` Leo 3 siblings, 0 replies; 14+ messages in thread From: Leo @ 2009-02-04 15:56 UTC (permalink / raw To: Stefan Monnier; +Cc: Chong Yidong, 1524, kastrup, Leo, emacs-devel 2009/1/11 Stefan Monnier <monnier@iro.umontreal.ca>: >>>> I think it is safe to remove (info "(elisp)PostScript Images") and >>>> gs.el now that over a month has passed. >>> It's used in image.c. We should probably try to fix it if it doesn't >>> work properly. >> I don't use it so I don't know whether it has bugs. I suspect it >> has. But I'm mostly concerned by the comment in the source which advise >> users not to use it. > > IIRC David Kastrup would know how broken it is. Ping? > Stefan > ^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#1524: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-11 14:57 ` Stefan Monnier 2009-02-04 15:56 ` Leo 2009-02-04 15:56 ` bug#1524: " Leo @ 2009-02-04 16:16 ` Leo 2009-02-04 16:16 ` Leo 3 siblings, 0 replies; 14+ messages in thread From: Leo @ 2009-02-04 16:16 UTC (permalink / raw To: Stefan Monnier; +Cc: Chong Yidong, dak, 1524, emacs-devel On 2009-01-11 14:57 +0000, Stefan Monnier wrote: [...] > IIRC David Kastrup would know how broken it is. Here is David's response. ------------------------------------------------ Leo <sdl.web@googlemail.com> writes: > 2009/1/11 Stefan Monnier <monnier@iro.umontreal.ca>: >>>>> I think it is safe to remove (info "(elisp)PostScript Images") and >>>>> gs.el now that over a month has passed. >>>> It's used in image.c. We should probably try to fix it if it >doesn't >>>> work properly. >>> I don't use it so I don't know whether it has bugs. I suspect it >>> has. But I'm mostly concerned by the comment in the source which >advise >>> users not to use it. >> >> IIRC David Kastrup would know how broken it is. > > Stefan's email sent an email address of yours which is no longer in > use. Could you comment this in emacs-devel mailing list? Pass it on if you want to. There are a lot of problems due to Ghostscript rendering directly to Pixmaps. Every image is rendered with its own Ghostscript process, but the parameter passing requires X properties as a global resource. This is done once per Ghostscript session and includes the display dimensions, so it can't really be extended to multiple image rendering without further Ghostscript API changes. The display code triggering the display is rather asynchronous: I've not been able figuring out how it is rooted in the bowels of the display engine. In practice, it worked more or less for a single image rendering per Emacs session. It doesn't scale at all. Serious work both in Ghostscript as well as in Emacs would be required to make this a smooth working feature, and I see no candidate for either. ------------------------------------------------ ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-11 14:57 ` Stefan Monnier ` (2 preceding siblings ...) 2009-02-04 16:16 ` Leo @ 2009-02-04 16:16 ` Leo 2016-12-12 22:20 ` bug#1524: " Glenn Morris 3 siblings, 1 reply; 14+ messages in thread From: Leo @ 2009-02-04 16:16 UTC (permalink / raw To: Stefan Monnier; +Cc: Chong Yidong, dak, 1524, emacs-devel On 2009-01-11 14:57 +0000, Stefan Monnier wrote: [...] > IIRC David Kastrup would know how broken it is. Here is David's response. ------------------------------------------------ Leo <sdl.web@googlemail.com> writes: > 2009/1/11 Stefan Monnier <monnier@iro.umontreal.ca>: >>>>> I think it is safe to remove (info "(elisp)PostScript Images") and >>>>> gs.el now that over a month has passed. >>>> It's used in image.c. We should probably try to fix it if it >doesn't >>>> work properly. >>> I don't use it so I don't know whether it has bugs. I suspect it >>> has. But I'm mostly concerned by the comment in the source which >advise >>> users not to use it. >> >> IIRC David Kastrup would know how broken it is. > > Stefan's email sent an email address of yours which is no longer in > use. Could you comment this in emacs-devel mailing list? Pass it on if you want to. There are a lot of problems due to Ghostscript rendering directly to Pixmaps. Every image is rendered with its own Ghostscript process, but the parameter passing requires X properties as a global resource. This is done once per Ghostscript session and includes the display dimensions, so it can't really be extended to multiple image rendering without further Ghostscript API changes. The display code triggering the display is rather asynchronous: I've not been able figuring out how it is rooted in the bowels of the display engine. In practice, it worked more or less for a single image rendering per Emacs session. It doesn't scale at all. Serious work both in Ghostscript as well as in Emacs would be required to make this a smooth working feature, and I see no candidate for either. ------------------------------------------------ ^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#1524: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-02-04 16:16 ` Leo @ 2016-12-12 22:20 ` Glenn Morris 0 siblings, 0 replies; 14+ messages in thread From: Glenn Morris @ 2016-12-12 22:20 UTC (permalink / raw To: 1524-done Version: 26.1 In 3c65523 I obsoleted it (which breaks it, since obsolete files aren't scanned for autoloads. I've never seen it used.) I think ImageMagick images can do whatever this did, better. ^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#1524: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-10 13:22 ` Chong Yidong 2009-01-11 3:51 ` Leo @ 2009-01-11 3:51 ` Leo 1 sibling, 0 replies; 14+ messages in thread From: Leo @ 2009-01-11 3:51 UTC (permalink / raw To: Chong Yidong; +Cc: 1524, emacs-devel On 2009-01-10 13:22 +0000, Chong Yidong wrote: > Leo <sdl.web@gmail.com> writes: > >> I think it is safe to remove (info "(elisp)PostScript Images") and >> gs.el now that over a month has passed. > > It's used in image.c. We should probably try to fix it if it doesn't > work properly. I don't use it so I don't know whether it has bugs. I suspect it has. But I'm mostly concerned by the comment in the source which advise users not to use it. Best, Leo ^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#1524: 23.0.60; gs.el - This code is experimental. Don't use it. 2009-01-10 5:10 ` Leo 2009-01-10 13:22 ` Chong Yidong @ 2009-01-10 13:22 ` Chong Yidong 1 sibling, 0 replies; 14+ messages in thread From: Chong Yidong @ 2009-01-10 13:22 UTC (permalink / raw To: Leo; +Cc: 1524, emacs-devel Leo <sdl.web@gmail.com> writes: > I think it is safe to remove (info "(elisp)PostScript Images") and > gs.el now that over a month has passed. It's used in image.c. We should probably try to fix it if it doesn't work properly. ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2016-12-12 22:20 UTC | newest] Thread overview: 14+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2008-12-09 23:51 23.0.60; gs.el - This code is experimental. Don't use it Chong Yidong 2009-01-10 5:10 ` bug#1524: " Leo 2009-01-10 5:10 ` Leo 2009-01-10 13:22 ` Chong Yidong 2009-01-11 3:51 ` Leo 2009-01-11 14:57 ` bug#1524: " Stefan Monnier 2009-01-11 14:57 ` Stefan Monnier 2009-02-04 15:56 ` Leo 2009-02-04 15:56 ` bug#1524: " Leo 2009-02-04 16:16 ` Leo 2009-02-04 16:16 ` Leo 2016-12-12 22:20 ` bug#1524: " Glenn Morris 2009-01-11 3:51 ` Leo 2009-01-10 13:22 ` Chong Yidong
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.