Bug#692060: remove shell-command.el from emacs-goodies-el

2018-07-30 Thread Dima Kogan
Nicholas D Steeves writes: > On Mon, Jul 30, 2018 at 07:13:00PM +0800, David Bremner wrote: >> >> Dima Kogan writes: >> > >> > For MY use case I don't even need all that because I can simply replace >> > (shell-command-make-prompt-string " [%w]%$ " default-directory) >> > with >> > (format "

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-07-30 Thread Nicholas D Steeves
Hi, On Mon, Jul 30, 2018 at 07:13:00PM +0800, David Bremner wrote: > > Dima Kogan writes: > > > > For MY use case I don't even need all that because I can simply replace > > (shell-command-make-prompt-string " [%w]%$ " default-directory) > > with > > (format " [%s]$ " (directory-file-name (a

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-07-30 Thread David Bremner
Dima Kogan writes: > > I don't think anything here is worth maintaining. If this goes away, > should we think about how to not blow up peoples' existing usages? Perhaps a wiki page with config snippet suggestions? Or more documentation in emacs-goodies-el README.Debian d

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-07-29 Thread Dima Kogan
David Bremner writes: >> It looks like much of shell-command is already available in emacs >> itself, so if there're any pieces that should be preserved, where should >> they go? > > Into a separate package if they are substantial enough to warrant it. > If not, that's a bit trickier. If it's ju

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-07-16 Thread Nicholas D Steeves
Hi Dima, On Mon, Jul 16, 2018 at 01:27:51AM -0700, Dima Kogan wrote: > David Bremner writes: > > > Are you willing to maintain it upstream? Because the plan is that > > emacs-goodies-el is not going to be upstream for anything anymore. > > Hi. I just looked at it. If emacs-goodies-el isn't upst

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-07-16 Thread David Bremner
Dima Kogan writes: > David Bremner writes: > >> Are you willing to maintain it upstream? Because the plan is that >> emacs-goodies-el is not going to be upstream for anything anymore. > > Hi. I just looked at it. If emacs-goodies-el isn't upstream for > anything, then where are the upstream sour

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-07-16 Thread Dima Kogan
David Bremner writes: > Are you willing to maintain it upstream? Because the plan is that > emacs-goodies-el is not going to be upstream for anything anymore. Hi. I just looked at it. If emacs-goodies-el isn't upstream for anything, then where are the upstream sources coming from? Are there mult

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-06-26 Thread David Bremner
Dima Kogan writes: >>Are you willing to maintain it upstream? Because the plan is that >>emacs-goodies-el is not going to be upstream for anything anymore. > > Possibly. Let me look at it when I get back in a few weeks. Sounds good, it's waited all these years for attention, it can wait a few mo

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-06-26 Thread David Bremner
Dima Kogan writes: > On June 25, 2018 4:20:39 AM PDT, David Bremner wrote: >> >>control: retitle -1 "emacs-goodies-el: remove shell-command.el" >>control: severity -1 important >> >>It seems no-one cares for this library (no new version since >>2009?). Since it seems broken, it seems like a bad

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-06-25 Thread Dima Kogan
On June 25, 2018 4:20:39 AM PDT, David Bremner wrote: > >control: retitle -1 "emacs-goodies-el: remove shell-command.el" >control: severity -1 important > >It seems no-one cares for this library (no new version since >2009?). Since it seems broken, it seems like a bad idea to release it >in >buste

Bug#692060: remove shell-command.el from emacs-goodies-el

2018-06-25 Thread Nicholas D Steeves
On Mon, Jun 25, 2018 at 08:20:39AM -0300, David Bremner wrote: > > It seems no-one cares for this library (no new version since > 2009?). Since it seems broken, it seems like a bad idea to release it in > buster. > > If you know of a live upstream version of this, please let me know. Would the f