Skip to content
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

Open
passstab opened this issue Jun 19, 2016 · 77 comments
Open

FreeBSD already comes with a program called vis #338

passstab opened this issue Jun 19, 2016 · 77 comments

Comments

@passstab
Copy link

passstab commented Jun 19, 2016

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

@ghost
Copy link

ghost commented Jun 28, 2016

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 visc, and the daemon visd?

@aeosynth
Copy link
Contributor

nodejs has a similar issue on debian/ubuntu; there is already a node program, so the js runtime is renamed to nodejs. most other distros leave the runtime as node.

@passstab
Copy link
Author

I don't think that is a good solution.

The other vis has quite a legacy, having first appeared in unix 8th edition.
Unlike the nodejs example which effects only debian and its downstream distributions, the other vis is now included in at least 5 separately maintained unix derivatives. In addition to the three I mentioned in my original comment, it is included in HP-UX and DragonflyBSD.

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.

@martanne
Copy link
Owner

I'm aware of the history leading to the original vis utility found on many Unix systems. And yes the name clash is unfortunate, at the time it was a deliberate decision. With hindsight it was probably a bad idea. I might indeed decide to rename the project at some point.

@czarkoff
Copy link

@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").

@martanne
Copy link
Owner

NetBSD/pkgsrc settled for vis-editor which seems preferable. I suggested the same thing for the homebrew package. In practical terms users properly use a shell alias anyway.

As for the more general problem of renaming the whole project, some naming suggestions which I remember from the last time this was discussed:

  • vs, might be too confusing with Visual Studio (Code)?
  • siv
  • mirj
  • ...

I haven't actually properly checked whether some of them are already in use etc. Suggestions welcome.

@ghost
Copy link

ghost commented Nov 28, 2016

Why not svi? It does not seems to be present in BSDs at least, and could mean Simple/Suckless VI[m] or Simple/Suckless Vi Improved (as in vi improved in a simple way).

@passstab
Copy link
Author

there is something else called vis-editor

@czarkoff
Copy link

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 svi or vie, so that vi part stands out.

@eworm-de
Copy link
Collaborator

Possibly a stupid idea, but... Let's discuss it. How about going with just v? In the end we are minimalistic. :D Would that clash anywhere?

@ghost
Copy link

ghost commented Nov 30, 2016

@eworm-de: I think no one ever dare name a text editor v, but many people may have a l as an alias for ls, and v for vi/vim.

On the other hand, this editor is not the default, so if the user installs it, he may want to use it.

@czarkoff: vie means "life" in french. And it is simple as in "VIsual Editor".

@czarkoff
Copy link

Yes, that was my reasoning behind this suggestion back in 2014..

@martanne martanne mentioned this issue Dec 14, 2016
@ghost ghost mentioned this issue Dec 17, 2016
@ghost
Copy link

ghost commented Jan 6, 2017

I also thought about triode, an anagram of editor, and the ancestor of the transistor. It is also very close to trimode (as the three modes of vi).

But it is too long to type: twice as much as vis!

@aeosynth
Copy link
Contributor

aeosynth commented Jan 17, 2017

savvy - sa(m) + vi(s). but this is also long.

edit - savi ?

@erf
Copy link
Contributor

erf commented Jan 17, 2017

Here are the permutations of vim and sam:

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

@shua
Copy link

shua commented Jan 22, 2017

is ve already taken? (visual editor)

or you can go the way of libzahl, and call it seh from german

@erf
Copy link
Contributor

erf commented Mar 17, 2017

@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.

@herrbischoff
Copy link

I like the idea of triode. It's a pleasant name which could also be shortened to tri.

@aeosynth
Copy link
Contributor

aeosynth commented Mar 22, 2017

the names sam and acme have no relation to ed or vi; this project doesn't have to pay homage either. call it me for 'modal editor'.

@luciusgone
Copy link

Seems stuck here. Shall I propose the name "fella" for this project is quite young compared to the other giant old mates.

@z3bra
Copy link

z3bra commented Jun 29, 2017

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 would suggest not going with a name that is longer than 4 char though. Long names calls for complex projects in my mind.

@ghost
Copy link

ghost commented Jun 30, 2017

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" ?

@ddkn
Copy link

ddkn commented Jul 3, 2017

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.

@lanodan
Copy link
Contributor

lanodan commented Jul 8, 2017

@josuah:

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:

  • Lojban makes it non-ambiguous in meaning & pronunciation
  • 1 letter longer than acme, 1 shorter than editor
  • It doesn’t clash and I don’t think it’s gonna clash with other software (checked: gentoo, debian, freebsd, openbsd, plan9front, wikipedia(fr,en,de,es))

@ghost
Copy link

ghost commented Jul 16, 2017

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:

name Linux (man7.org) Linux (die.net) NetBSD FreeBSD OpenBSD Plan 9
vis
vise
vs
siv
mirj
svi
vie
v
triode
savi
savvy
ve
seh
tri
me ~
fella
edit
edt
stika

To add more rows:

sed 's!.*!| `&` | [?](https://duckduckgo.com/lite/?q=site:man7.org/linux/+&) | [?](https://duckduckgo.com/lite/?q=site:linux.die.net/man+&) | [?](http://netbsd.gw.com/cgi-bin/man-cgi?&) | [?](http://man.freebsd.org/&) | [?](http://man.openbsd.org/&) | [?](https://duckduckgo.com/lite/?q=site:man.cat-v.org+&) |!'

@erf
Copy link
Contributor

erf commented Jul 16, 2017

Maybe add a poll at some time? Or a random chooser ;)

@lanodan
Copy link
Contributor

lanodan commented Nov 15, 2018

Should vis be renamed please also look for name clashes in Debian

Debian packages are indexed into repology.org, which I done checks against.

@msiism
Copy link
Contributor

msiism commented Dec 14, 2018

@josuah: Could you add vise to the poll as well?

@ghost
Copy link

ghost commented Dec 26, 2018

From all the proposed names, vie is the one I like the most.

@hholst80
Copy link

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 vis works just fine on my distro because there is no vis package nor vis binary and it installs as such. Go ahead and package it as visam why not there are infinite possibilities. Package maintainer makes the call and will maintain his choice for a long time and the founder of this project made his: vis.

@ghost
Copy link

ghost commented Apr 23, 2019

suggesting vise as it is named on OpenBSD - the obsession with 3 character names is absurd when it's as unhelpful as it so far has been

@Henry-Wilson
Copy link

@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 vise or visam or anything else, so be it. But if you all as project developers are satisfied with the name vis, so be that, too.

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.

@xxzozaxx
Copy link

xxzozaxx commented Dec 12, 2019

what about 9vi ?!

Plan 9 powered VI [Optional extra letters Editor, Sam]

@lanodan
Copy link
Contributor

lanodan commented Dec 13, 2019 via email

@filipencopav
Copy link

filipencopav commented Feb 25, 2020

@paride "svi" is even easier on dvorak

@noorwachid
Copy link

noorwachid commented Mar 8, 2020

I like 2 letters.

why not vs for vi + sam? no one uses it? vscode use code.
vn for vi plan 9.
and the most crazy i found no one uses. ai for sam vi.

@7v0lk0v
Copy link
Contributor

7v0lk0v commented Mar 8, 2020

I'm with @Henry-Wilson and @hholst80.

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.

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 ls and cd your editor of choice is probably the most invoked command, so typing even two chars is too much - I alias vis to just e (edit), just as ls is just l (a default alias on most systems) and cd is c.

@plasmoduck
Copy link

plasmoduck commented Nov 30, 2020

svi, keep it simple, stupid. Suckless/Simple VIm = svi

@ukn-ubi
Copy link

ukn-ubi commented Jan 11, 2021

I really like svi, especially since vis is a great compliment to a system running suckless software

@jzbor
Copy link

jzbor commented Jan 14, 2021

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'.

@rafaelveggi
Copy link

rafaelveggi commented Jan 19, 2021

"mestre", from "Combining modal editing with structural regular expressions"
But vis is a better name.

@plasmoduck
Copy link

Too long to type lol

@ddkn
Copy link

ddkn commented Jan 29, 2021

@3dc1d3: just add whatever shell alias you prefer

One annoyance is when you type man your_alias and it fails with "No manual entry for your_alias".

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:
On Mac: man vis-editor
On OpenBSD: man vise

Moving around systems makes it annoying, but that is my use case, which may be unique.

@mcepl
Copy link
Contributor

mcepl commented Mar 22, 2022

I propose "stika"[stika] which comes from lojban:

Also, štika is Esox (or pike) in Czech and Esox is too much underutilized name considering how beautiful fish it is. Not mentioning Rob Pike, of course.

However, I would vote for siv or svi myself.

@acidrums4 acidrums4 mentioned this issue May 1, 2022
@plasmoduck
Copy link

plasmoduck commented Oct 11, 2022 via email

@mcepl
Copy link
Contributor

mcepl commented Oct 11, 2022

svi, keep it simple, stupid. Suckless/Simple VIm = svi

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.

@rumaks-xyz
Copy link

I propose via.

  • If vis stands for vi + sam, then via could stand for vi + sam or vi + acme
  • Appears to not be taken by any other programs (please correct me if I'm wrong on this)
  • via sounds somewhat similar to Lua.
  • It only differs from vis and vim by one character and is equally easy to type.
  • Just like Vim, Vis is mostly based on vi, so it makes sense that the name would start with vi

@johngebbie
Copy link

You've probably been waiting for my suggestion:

vix - vi extended

@mcepl
Copy link
Contributor

mcepl commented Aug 4, 2023

I have no idea who has the authority to adjudicate on this one? @martanne ? @ninewise ? @rnpnr ? Could we get this to some conclusion, please?

@rnpnr
Copy link
Collaborator

rnpnr commented Aug 4, 2023

If your package repository doesn't have categories then I think
vis-editor or vise is fine with the first preferred. Same goes for
the binary.

What @martanne said 5 years ago is also true:

In practical terms users properly use a shell alias anyway.

If this has to be done I think the best suggestion I have seen is siv.
@mcepl is correct, this isn't simple/suckless vi; the s stands for
sam or 'Structural Regular Expressions'. The name should avoid that
misrepresentation.

In any case @martanne is the one who would have to do this since the
repo would need to be renamed not just the binary.

For the time being I am considering locking this conversation since we
don't really need anymore suggestions.

@mcepl
Copy link
Contributor

mcepl commented Aug 4, 2023

  • If vis stands for vi + sam, then via could stand for vi + sam or vi + acme

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.

@polluks2
Copy link

polluks2 commented Sep 4, 2023

macOS also comes with a program called vis:
"display non-printable characters in a visual format"

@VehementHam
Copy link

I like 2 letters.

why not vs for vi + sam? no one uses it? vscode use code. vn for vi plan 9. and the most crazy i found no one uses. ai for sam vi.

I aliased vis to vs

@mcepl
Copy link
Contributor

mcepl commented Jun 12, 2024

macOS also comes with a program called vis: "display non-printable characters in a visual format"

MacOS uses a lot of *BSD utils, so this is actually the same vis(1) with which this issue started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests