Re: Bug#801837: ITP: yank -- interactively select and yank terminal output to stdout or xsel
On Oct/15, Jakub Wilk wrote: > Please talk to upstream (or maybe to both upstreams) before renaming > anything. > [...] > Eeek... https://lists.debian.org/20070428095345.ga9...@kunpuu.plessy.org The package is already in NEW, and contains /usr/bin/yank-cli. I'll add a note to README.Debian about that renaming, and also a recommendation to alias it to something short : users of this package will be command-line afficionados, and as such should probably not be handicapped by this. Cheers, --Seb
Re: Bug#801837: ITP: yank -- interactively select and yank terminal output to stdout or xsel
On Oct/15, Jakub Wilk wrote: > Sounds very cool, but apt-file tells me this name is already taken: > > emboss: /usr/bin/yank I think I'll keep the package name, but I'll install the binary itself under some other name, maybe something like /usr/bin/yank-cli ? Cheers, --Seb
Re: Bug#801837: ITP: yank -- interactively select and yank terminal output to stdout or xsel
* Sebastien Delafond, 2015-10-15, 08:04: * Package name: yank Version : 0.4.0 Upstream Author : Anton Lindqvist * URL : https://github.com/mptre/yank * License : MIT Programming Lang: C Description : interactively select and yank terminal output to stdout or xsel Sounds very cool, but apt-file tells me this name is already taken: emboss: /usr/bin/yank -- Jakub Wilk
Re: Bug#801837: ITP: yank -- interactively select and yank terminal output to stdout or xsel
Le jeudi 15 octobre 2015, 11:29:00 Sébastien Delafond a écrit : > On Oct/15, Jakub Wilk wrote: > > Sounds very cool, but apt-file tells me this name is already taken: > > > > emboss: /usr/bin/yank > > I think I'll keep the package name, but I'll install the binary itself > under some other name, maybe something like /usr/bin/yank-cli ? > > Cheers, > > --Seb > Hi, from [1], I see that emboss ships 261 programs in /usr/bin/ including cool names like "banana", "chaos", "needle", "water", "wobble" ... so this means all these names can't be re-used forerver :-( Current /usr/bin/yank [2] is 10 lines of code, the new tool seems more usefull for more users; and from the animated .gif on the project page, it's supposed to be something short that's called frequently, so the contrived name with the hypen will make it hard to use... Maybe this can be also be solved by documenting how to set a bash alias, or a symlink in /usr/local/bin . [1] https://packages.debian.org/sid/amd64/emboss/filelist [2] https://sources.debian.net/src/emboss/6.6.0%2Bdfsg-1/emboss/yank.c/ [3] https://github.com/mptre/yank Greets, Alexandre Detiste signature.asc Description: This is a digitally signed message part.
Re: Bug#801837: ITP: yank -- interactively select and yank terminal output to stdout or xsel
> Well, that `emboss` tool clearly appears to be lame in its approach: > it should provide a single CLI tool called `emboss` which would have > those "yank" et al as its subcommands so that anyone could do something > like `emboss yank ...` etc. > > I'd say this should be reported as a bug upstream. > > The original names could be provided as a compat package shipping a > bunch of shell one-liner scripts. ...or rather symlinks, and/or place them in its own directory, like other tools with many subcommands (openssl, busybox) do. I think this is common enough to warrant codification by policy. Olaf
Re: Bug#801837: ITP: yank -- interactively select and yank terminal output to stdout or xsel
Le jeudi 15 octobre 2015, 11:29:00 Sébastien Delafond a écrit : Sounds very cool, but apt-file tells me this name is already taken: emboss: /usr/bin/yank I think I'll keep the package name, but I'll install the binary itself under some other name, maybe something like /usr/bin/yank-cli ? Please talk to upstream (or maybe to both upstreams) before renaming anything. * Alexandre Detiste, 2015-10-15, 18:14: from [1], I see that emboss ships 261 programs in /usr/bin/ including cool names like "banana", "chaos", "needle", "water", "wobble" ... so this means all these names can't be re-used forerver :-( Eeek... https://lists.debian.org/20070428095345.ga9...@kunpuu.plessy.org Current /usr/bin/yank [2] is 10 lines of code, Um, length of the source file that contains main() is a very poor measure of program's complexity or usefulness. -- Jakub Wilk
Re: Bug#801837: ITP: yank -- interactively select and yank terminal output to stdout or xsel
On Thu, 15 Oct 2015 18:14:17 +0200 Alexandre Detistewrote: > > > Sounds very cool, but apt-file tells me this name is already > > > taken: > > > > > > emboss: /usr/bin/yank > > > > I think I'll keep the package name, but I'll install the binary > > itself under some other name, maybe something > > like /usr/bin/yank-cli ? [...] > Hi, from [1], I see that emboss ships 261 programs in > /usr/bin/ including cool names like "banana", "chaos", "needle", > "water", "wobble" ... so this means all these names > can't be re-used forerver :-( > > Current /usr/bin/yank [2] is 10 lines of code, the new tool > seems more usefull for more users; [...] > [2] > https://sources.debian.net/src/emboss/6.6.0%2Bdfsg-1/emboss/yank.c/ Well, that `emboss` tool clearly appears to be lame in its approach: it should provide a single CLI tool called `emboss` which would have those "yank" et al as its subcommands so that anyone could do something like `emboss yank ...` etc. I'd say this should be reported as a bug upstream. The original names could be provided as a compat package shipping a bunch of shell one-liner scripts.
Bug#801837: ITP: yank -- interactively select and yank terminal output to stdout or xsel
Package: wnpp Severity: wishlist Owner: Sebastien Delafond* Package name: yank Version : 0.4.0 Upstream Author : Anton Lindqvist * URL : https://github.com/mptre/yank * License : MIT Programming Lang: C Description : interactively select and yank terminal output to stdout or xsel Read input from stdin and draw a selection interface where all fields in the given input are recognized by using a default or user-supplied set of delimiters. . Using ctrl-n and ctrl-p will move the field selection forward and backward, pressing the return key will invoke the yank command and write the selected field to its stdin. The yank command defaults to xsel, but could be anything that accepts input on stdin.