Copy as about vim-eunuch HOT 11 CLOSED

How about :Duplicate?

from vim-eunuch.

Native :saveas should do the feature.

from vim-eunuch.

Native :saveas should do the feature.

Not exactly. Comparing to other eunuch commands, :CopyAs would work like :Rename, i.e., relative to the current file's containing directory, and different from :Move, that's relative to the current working directory.

To illustrate it:

Imagine your working directory, as in :pwd, is /project, but you're editing /project/src/somefile.ext. Then you want to create a copy of this file and name it anotherfile.ext.

• With :saveas anotherfile.ext, the new file would be created at /project. To keep the copy in the same directory of the original file, you'd have to use :saveas %:p:h/anotherfile.ext.
• With the proposed CopyAs, typing :CopyAs anotherfile.ext would create the new anotherfile.ext at /project/src, alongside the original somefile.ext.

from vim-eunuch.

You're right @rawaludin, it's easy to use a native command in this case – actually, I'm already doing that. But the request matches the purpose of this plugin, that's to provide "Vim sugar for the UNIX shell commands".

So it seems to make sense having a command like the suggested :CopyAs (or :SaveAs). It is simply some sugar over the built-in :saveas and that's the thing of vim-eunuch.

from vim-eunuch.

from vim-eunuch.

I'm having trouble getting past the name. How do you get from ":saveas relative to the current file's directory" to :CopyAs?

from vim-eunuch.

I endorsed the feature request but, personally, I prefer :SaveAs.

from vim-eunuch.

That's less random, but still raises the same question.

Why provide :SaveAs and not also :Edit, Read, :Write, :WQ, :File, :VSplit, etc?

from vim-eunuch.

I was looking at the perspective that the suggested :CopyAs/:SaveAs would be a good companion to the already provided commands :Rename and :Move, and just that. But now I see that :Rename and :Move can't be achieved with a single native command, whereas :CopyAs/:SaveAs can.

So I understand your point of view, and now I see the implications this addition could trigger.

from vim-eunuch.

To sum up the arguments for providing :Rename as an alias :Move %:h/:

• It's an extremely common operation.
• It's a variation of something Eunuch has already taken responsibility for.
• There's a single, obvious, easily remembered name for it.

Compare to :SaveAs:

• It's common mainly as a poor man's template system. That is, it's useful in a pinch, but if you're doing it a million times a day, there's probably a better solution.
• It's a variation of a built-in.
• I can't think of a good name.

So yeah, it'd be a questionable addition with a good name. I don't think I'll be adding it with a bad name.

from vim-eunuch.

That's definitely a better name!

from vim-eunuch.