| 16 Oct 2022 |
 K900 | grahamc (he/him): can we get #kde:nixos.org or something? | 16:25:27 |
 @grahamc:nixos.org | #kde:nixos.org | 17:34:48 |
| @grahamc:nixos.org | all set K900 ! | 17:35:43 |
| 20 Oct 2022 |
|  daniel joined the room. | 06:26:26 |
|  Leon left the room. | 13:04:05 |
| 22 Oct 2022 |
|  markuskowa joined the room. | 10:26:37 |
 pie_ | Can we get a Nix HPC (channel? (cc markuskowa ) | 11:54:10 |
| 23 Oct 2022 |
|  @sofo:matrix.org joined the room. | 09:27:17 |
| 24 Oct 2022 |
|  @chris:mkaito.net left the room. | 07:59:04 |
|  FRidh joined the room. | 11:21:04 |
| FRidh | I suggest having a NixOS foundation channel where topics related to the foundation can be discussed. Maybe as a rule we should mention in the topic though that if a reply is sought from a board member, discourse should be used? | 11:22:15 |
| pie_ | In reply to @jcie74:matrix.org
Can we get a Nix HPC (channel? (cc markuskowa ) grahamc (he/him): didnt realize maybe I should highlight you, no worries if you just haven't had time. | 16:50:09 |
|  @bolnav:matrix.org joined the room. | 18:18:38 |
| @bolnav:matrix.org left the room. | 19:26:44 |
| 25 Oct 2022 |
| @sofo:matrix.org | Could we create a #neovim:nixos.org channel?
There seems to be reasonable demand for a NixOS spessific channel about the topic, similar to #emacs:nixos.org for emacs. Youtube has videos about the topic such as https://www.youtube.com/watch?v=rUvjkBuKua4 which already have over 10k views. There also exists a lot of external interest from places like r/neovim as well: https://www.reddit.com/r/neovim/comments/yagf37/which_plugin_manager_are_you_using/ There are also people in this matrix community as well who would be interested, one i know of directly is @shane:sveller.social
| 07:19:10 |
| @sofo:matrix.org | * Could we create a #neovim:nixos.org channel?
There seems to be reasonable demand for a Nix/NixOS specific channel about the topic, similar to #emacs:nixos.org for emacs. Youtube has videos about the topic such as https://www.youtube.com/watch?v=rUvjkBuKua4 which already have over 10 000 views. There also exists a lot of external interest from places like r/neovim as well: https://www.reddit.com/r/neovim/comments/yagf37/which_plugin_manager_are_you_using/ There are also people in this matrix community as well who would be interested, one i know of directly is @shane:sveller.social
| 07:19:51 |
 Sandro | Why not name it vim and include vim and neovim since there is quite some overlap?
| 16:06:08 |
 kevincox | Call it vi to ensure it isn't specific to vim either. | 16:07:21 |
| kevincox | ...although I'm sure someone is running some old original vi on nix. | 16:07:35 |
| @sofo:matrix.org | That is entirely possible, i chose against it for the suggestion as most individuals who customize their install now run Neovim over Vim. But it may also be called #vim:nixos.org to include both. | 16:08:14 |
| Sandro | In reply to @kevincox:matrix.org
Call it vi to ensure it isn't specific to vim either. jokes aside, vim and neovim are very close and you can with a few ifs re-use the config. vi is is no longer. | 16:08:59 |
| @sofo:matrix.org | In reply to @sandro:supersandro.de
jokes aside, vim and neovim are very close and you can with a few ifs re-use the config. vi is is no longer. This is if you use the older viml over the new standard of lua in neovim. Most neovim configs are not possible to backport without serious investment. But neovim can run all plugins and configurations from vim. | 16:09:56 |
| @sofo:matrix.org | In reply to @sandro:supersandro.de
jokes aside, vim and neovim are very close and you can with a few ifs re-use the config. vi is is no longer. * This is if you use the older viml (language) over the new standard of lua in neovim. Most neovim configs are not possible to backport without serious investment. But neovim can run all plugins and configurations from vim. | 16:10:37 |
| kevincox | That was kind of the point. Using the name of one of the alive projects vim or nvim suggests priority for one over the other. If we want both in a channel as would likely be useful it makes sense to pick a name that is clearly not specific about either one. Hence vi. | 16:11:36 |
| @sofo:matrix.org | I see vim and neovim going further and further apart as tooling becomes more split. Like LSP integration, diagnostic tooling, and UI APIs. | 16:11:44 |
| Sandro | In reply to @sofo:matrix.org
This is if you use the older viml (language) over the new standard of lua in neovim. Most neovim configs are not possible to backport without serious investment. But neovim can run all plugins and configurations from vim. I use both and only lua because some plugins need it. | 16:12:54 |
| @sofo:matrix.org | In reply to @kevincox:matrix.org
That was kind of the point. Using the name of one of the alive projects vim or nvim suggests priority for one over the other. If we want both in a channel as would likely be useful it makes sense to pick a name that is clearly not specific about either one. Hence vi. I could vouch for #vim, but #vi is a few decades too far out i think for people to realize its connection to neovim, which is what people are likely running today. Like calling Windows 10 of MSDOS-origin. | 16:13:43 |
| K900 | Just call it #v | 16:14:16 |
| @sofo:matrix.org | #ex and #ed are also great alternatives :P | 16:14:58 |
| @sofo:matrix.org | * #ex and #ed are also great alternatives if its history we are after :P | 16:19:25 |
