Talk:Vim

From ArchWiki
Jump to: navigation, search

256 Colorschemes

There should be a comment somewhere in the vimrc example pointing out that 256 colors load properlly if the colorscheme sentence on the vimrc is at the bottom of the file

set mouse=a and root terminals

vimrc_example.vim enables mouse support (enter visual mode on selection) via set mouse=a. If you installed gvim, then this also copies text to PRIMARY, as any other selection in Xorg.

This only works if the DISPLAY variable is available, which it usually isn't with sudo. e.g. try with:

unset DISPLAY
vim

I believe the article should point this out: while obvious in hindsight, at first it looks like clipboard support is haphazardly failing. It may be out of scope for Vim#Installation, but we could create a Troubleshooting section. -- Alad (talk) 14:28, 15 January 2016 (UTC)

On my system DISPLAY is propagated into sudo's session. It is not specified in the sudoers file and man sudoers says "The DISPLAY, PATH and TERM variables remain unchanged;" so I believe this is the default behaviour... -- Lahwaacz (talk) 15:47, 15 January 2016 (UTC)
You're right, I was using su - and confused things. Well, I assume most users go with sudo and don't face the issue - maybe just link to [1] ? -- Alad (talk) 18:05, 15 January 2016 (UTC)
Somehow I'm losing the connection between :h mouse and :h clipboard...? Anyway, if you find it appropriate to describe the X11 features more thoroughly, just start a new section. Lahwaacz (talk) 21:06, 15 January 2016 (UTC)

Configuration

Some of the links to example configurations are dead and I have replaced them with links to archive.org. Would these be better replaced by other well documented examples? -- ToxygeneB (talk) 18:25, 29 May 2016 (UTC)

Nice you looked them up for a start. Generally you are right, particularly since it is likely that vim configuration changes, so the files outdate for sure which can lead to avoidable troubleshooting. If you think from your experience, that it is likely they outdated already, better remove them or replace them. Up to you to decide, if someone disagrees they will likely be re-added with an edit comment on why they are still useful.
In general I think it would be nicer, if the links in the Vim#Configuration_2 had a little comment next to them about special points they might cover. I'm not expert enough to add such though.
--Indigo (talk) 13:11, 30 May 2016 (UTC)

Should there be this much tutorial content?

The usage section is very large, and not very useful, in my opinion. If users are looking for learning resources, vimtutor would do a much better job. I think usage should be a short overview of things that focuses on more abstract things, such as how modal editing works. Conley (talk) 15:06, 23 September 2012 (UTC)

My reply would be a simple +1 (also because of Help:Style#Hypertext metaphor), but the same observation can be done for Emacs, so we can either remove the usage sections from both articles or none.
I don't think it's the ArchWiki's duty to teach how to use Vim or Emacs, there are innumerable guides, tutorials, cheat sheets... out there for both applications, not counting their official documentation. I don't think either that people really come to the ArchWiki to learn how to use those programs.
On the other hand, I recognise that a lot of effort has been put to write those sections, and just chucking them out like that would make me a little sorry ^^
More opinions?
-- Kynikos (talk) 12:35, 24 September 2012 (UTC)
The Emacs page was re-written and structured to be consistent with the Vim page; any structure change should be reflected in both pages. I don't want to speculate why people do and don't come to the ArchWiki. The standard of documentation on these pages is quite good and I wouldn't like to see them removed just for the sake of it. However, if other pages can be found which provide an equivalent (or better) resource, then I'm all for it.
--Chpln (talk) 09:23, 25 September 2012 (UTC)
This documentation is hard for me to read; my eyes just skim right past it. I think it may be the typography that's causing issues, but at any rate, I feel that there are many better resources. There's the wonderful vimtutor and the help documents both built into vim. Also, here are a few sites I found from a quick search:
http://vim.wikia.com/wiki/Vim_Tips_Wiki
http://www.openvim.com/
http://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressively/
http://www.knowvim.com/
http://yanpritzker.com/2011/12/16/learn-to-speak-vim-verbs-nouns-and-modifiers/
http://vim-adventures.com/ (You have to pay if you want the entire game)
Conley (talk)
Vim hs a very good document base. Arch wiki should link to these pages instead duplicate information here. Upstream first is what Arch always does. -- Fengchao (talk) 02:26, 26 September 2012 (UTC)
I'm beginning to work on deleting all the extraneous content. Once all the other sections are up to par, as well as the basics section, I'll take them out. -- Conley (talk) 22:23, 6 October 2012 (UTC)
More than three years later, we can assume this issue is solved. Closing. -- Alad (talk) 14:31, 15 January 2016 (UTC)
Restoring because referenced from Talk:Emacs#Should there be this much tutorial content?. — Kynikos (talk) 10:57, 10 June 2016 (UTC)