-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeBSD already comes with a program called vis #338
Comments
The project could keep the same name: Only the binary and the man page needs to change their name? Vis could get a server/client model in the future. The client could be |
nodejs has a similar issue on debian/ubuntu; there is already a |
I don't think that is a good solution. The other vis has quite a legacy, having first appeared in unix 8th edition. Leaving the naming to the different operating systems could mean more then a couple names, and it could be an annoyance for those who use more then one OS. I think keeping the name vis would unnecessarily cause a lot of confusion. |
I'm aware of the history leading to the original |
@martanne, I am making an OpenBSD port for vis, and I have to rename binary and manual page it to avoid name clash. Any suggestions regarding name? I came up with "vise" ("vis" + "e" for "editor"). |
NetBSD/pkgsrc settled for As for the more general problem of renaming the whole project, some naming suggestions which I remember from the last time this was discussed:
I haven't actually properly checked whether some of them are already in use etc. Suggestions welcome. |
Why not |
there is something else called vis-editor |
People won't necessarily use aliases unless they are forced to. Some may even switch between different vi-like editors depending on current task. So a simpler, shorter name would be a good thing. Also, if renaming is on cards, it should probably happen as soon as possible, so that the amount of downstream projects that have to deal with package name change is as small as possible. FWIW I'd rather go with |
Possibly a stupid idea, but... Let's discuss it. How about going with just |
@eworm-de: I think no one ever dare name a text editor On the other hand, this editor is not the default, so if the user installs it, he may want to use it. @czarkoff: |
Yes, that was my reasoning behind this suggestion back in 2014.. |
I also thought about But it is too long to type: twice as much as |
savvy - sa(m) + vi(s). but this is also long. edit - savi ? |
Here are the permutations of vim vis via vmi vms vma vsi vsm vsa vai vam vas iva ivm ivs ima imv ims isa isv ism ias iav iam mvs mva mvi mis mia miv msi msa msv mai mas mav svi svm sva siv sim sia smv smi sma sav sai sam avs avi avm ais aiv aim ams amv ami asm asv asi |
is or you can go the way of libzahl, and call it |
@shua a quick google search revealed this -> http://www.campbell-tx.net/campbellware/ve.php In general when considering a name, i think the key combination should be as easy as possible to type. |
I like the idea of |
the names |
Seems stuck here. Shall I propose the name "fella" for this project is quite young compared to the other giant old mates. |
It could be something as simple as "edit", so that typing "edit file" would make sense! I also like the name "vie". As I read it in french, it makes english sentences sound fun :) |
I like "edit" (contains ed(1) in it), but it is hard to search through search engines. Also, http://man.freebsd.org/edit points to ee(1). "edit" -> "edt" ? |
Reading through this list, I like the idea of siv, which is similar to a sieve /siv/. Defined as separating coarser from finer particles (code) -- seems to be what vis does as an editor. Short name, and still has sam, and vi in the name, as well as minimal and doesn't conflict. Compiling for FreeBSD was when I noticed this issue. |
I think removing few letters is not gonna help people that have issues reading/writing and/or issues remembering the name, also it makes it non-pronounceable or ambigous. I propose "stika"[stika] which comes from lojban:
|
There's a lot of names now ! :) They are all fine, but we cannot pick them all.b We could do the name change at version 1.0, with the announcement to the community (HN, lobste.rs, reddit...): "releasing **** 1.0". Does it clash on some OS, in chronological order of the proposition:
To add more rows:
|
Maybe add a poll at some time? Or a random chooser ;) |
Should |
Debian packages are indexed into repology.org, which I done checks against. |
@josuah: Could you add |
From all the proposed names, |
My two cents on this garbage fire. Global namespace is considered harmful. This project should not concern itself with the legacy interoperability of filenames on BSD. We can discuss what potential binary names could fit but it is the problem of the downstream packager to fix it how they seem fit. Meanwhile |
suggesting |
@hholst80 I agree. One software project is not responsible for avoiding all the names of other projects, obscure or not. The role of a project is simply to produce functional, clean software. The package management system for a given distro is responsible, as the whole point of package management is to satisfy dependencies and resolve conflicts. The project is afforded the right to brand itself how it sees fit. Now, if for the sake of that branding we might rather call this project I am certainly satisfied as a user. Perhaps other potential users would be influenced by a "better" name; I wouldn't know. I stumbled across this project in my search for a good editor, and the name struck me as (hopefully) reflective of simplicity in the project. |
what about 9vi ?! Plan 9 powered VI [Optional extra letters Editor, Sam] |
[2019-12-12 10:35:44-0800] Ahmed Khaled:
what about 9vi ?!
Plan *9* powered *VI* [Optional letters *E*ditor, *S*am]
Why not but the only Plan9 thing is sam.c and 9* is usually more for Plan9 (From User) Space.
|
@paride "svi" is even easier on dvorak |
I like 2 letters. why not |
I'm with @Henry-Wilson and @hholst80.
My thoughts exactly. For all the talk about what would be an easy/short name to type... just add whatever shell alias you prefer. After |
svi, keep it simple, stupid. Suckless/Simple VIm = svi |
I really like svi, especially since vis is a great compliment to a system running suckless software |
Here are my two cts: Have you considered 'vine'? It is easy to pronounce an just straight up mixture of 'vi' and 'nine'. There is a Japanese Linux distro with this name, but no binary as far as I have checked. Also 'nive' but it might sound a little violent... Other than that I really like the idea of 'vie'. |
"mestre", from "Combining modal editing with structural regular expressions" |
Too long to type lol |
One annoyance is when you type I run vis on Mac, Windows, OpenBSD, and rarely Linux. A consistent name would be nice across all OS's or distros, at this point I would just prefer consistency over anything else at the moment. Even though I am in favour of something short like vie (vi enhanced/extended) or svi (sam vi), which isn't much different from vis (vi sam). For example: Moving around systems makes it annoying, but that is my use case, which may be unique. |
sted - simple text editor
…On Tue, 22 Mar 2022, 7:41 pm Matěj Cepl, ***@***.***> wrote:
I propose "stika <http://jbovlaste.lojban.org/dict/stika>"[*stika*] which
comes from lojban:
Also, štika <https://cs.wikipedia.org/wiki/%C5%A0tika> is Esox
<https://en.wikipedia.org/wiki/Esox> (or pike) in Czech and Esox is too
much underutilized name considering how beautiful fish it is.
However, I would vote for siv or svi myself.
—
Reply to this email directly, view it on GitHub
<#338 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJJMIYHDQAGCZJHTCF66PYTVBGBVFANCNFSM4CHE7X4A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Except it is not: simple VI is not an editor with Lua plugins etc. If you need something truly suckless than I would go for nvi or something of that ilk. Exactly, not to confuse this with vi, I would suggest siv. |
I propose
|
You've probably been waiting for my suggestion: vix - vi extended |
If your package repository doesn't have categories then I think What @martanne said 5 years ago is also true:
If this has to be done I think the best suggestion I have seen is In any case @martanne is the one who would have to do this since the For the time being I am considering locking this conversation since we |
Except vis has almost nothing common with ACME, which is mostly GUI, shell-like or IDE-like environment, while vis is a very simple editor-only. |
macOS also comes with a program called vis: |
I aliased |
MacOS uses a lot of *BSD utils, so this is actually the same |
You might want to change the name of this project
https://www.freebsd.org/cgi/man.cgi?query=vis&sektion=1&apropos=0&manpath=freebsd
Edit: that software is also included in openbsd http://man.openbsd.org/vis.1 and netbsd http://netbsd.gw.com/cgi-bin/man-cgi?vis+1+NetBSD-6.0
The text was updated successfully, but these errors were encountered: