XCV
Dev tools
command line utility
SHOW HN2015
How HN took it
2 positive, 5 neutral or asking, 0 mixed, 1 critical, out of 8 comments about the project. Thread score +0.10.
Design: 1 for, 1 againstIdea: 1 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful idea; the ability to list files being copied is good
From 2 comments
I wrote something similar sometime back: https://github.com/ashisha/x-cut-copy-paste But the ability to list the files being copied is brilliant indeed.
ashishb4u on HNApologies ahead of time for grammar and spelling, I am on a phone. This is a really cool idea, although you would you be willing to implement it using a file which would cache…
throwaway0x01 on HN
Maker already found it saved time
From 1 comment
I'm glad you like it, in its infancy it's already saved me a good bit of time! Your concerns make sense and I do want to eventually reconsider the paste processing; for now, for…
busterc on HN
Objections
Copy-based implementation loses move efficiency and SELinux labels
From 1 comment
Apologies ahead of time for grammar and spelling, I am on a phone. This is a really cool idea, although you would you be willing to implement it using a file which would cache…
throwaway0x01 on HN
Cut then forgetting to paste can lose content; accidental deletion risk
From 2 comments
The copy/cut/paste paradigm is ubiquitous, but I've always thought that a better model would be mark/duplicate/move. Where copy+paste is achievable by mark+duplicate and…
muxxa on HNSomething like this would be less likely to accidentally delete files (copy copy paste just purges the list, not the actual files):…
fyolnish on HN
Default recursive copy from home directory could be dangerous
From 1 comment
The requirement for adding -R might be useful. Consider the case of accidentally executing `xvc .` from within $HOME. Of course, cp/mv already provide plenty of ways to…
ilikepi on HN
Options should use dashes
From 1 comment
First thing I thought too: the options should have a dash. (yes cool project too)
nthcolumn on HN
Requests
Cache cut/copy operations in a file in HOME/.xcv instead of copying immediately
From 1 comment
Apologies ahead of time for grammar and spelling, I am on a phone. This is a really cool idea, although you would you be willing to implement it using a file which would cache…
throwaway0x01 on HN
Default recursive copy and simpler syntax
From 1 comment
Cool project! What about a syntax like: ``` Copy all files recursively: xcv . Cut all files recursively: xcv -x . List all files which will be pasted: xcv -l Paste all copied…
sillysaurus3 on HN
Mark/duplicate/move model instead of copy/cut
From 1 comment
The copy/cut/paste paradigm is ubiquitous, but I've always thought that a better model would be mark/duplicate/move. Where copy+paste is achievable by mark+duplicate and…
muxxa on HN
Questions
Does it use npm even though written in shell?
From 1 comment
It's interesting that this software is using NPM as package manager even if it's written in Shell itself.
daGrevis on HN
Is this related to xsel and the X clipboard?
From 1 comment
No one knows about xsel anymore?
kenshaw on HN
Alternatives named
Own earlier x-cut-copy-paste script
From 1 comment
I wrote something similar sometime back: https://github.com/ashisha/x-cut-copy-paste But the ability to list the files being copied is brilliant indeed.
ashishb4u on HN
Gist-based safer copy/move approach
From 1 comment
Something like this would be less likely to accidentally delete files (copy copy paste just purges the list, not the actual files):…
fyolnish on HN
xsel
From 1 comment
No one knows about xsel anymore?
kenshaw on HN