On Thursday, May 17, 2012 7:57:08 AM UTC-5, Benjamin R. Haskell wrote: > > So, a script can know not to use that character. > > I'm not sure what you mean here. Why would a script care? If a user > opens a file in terminal Vim and it contains characters that can't be > displayed, the user can just quit and open it in another editor that can > display the characters (another terminal with a different font, or some > GUI program). The user can also, as you reported, edit the file anyway > (Vim won't corrupt the data -- it just won't be displayed properly). > > Otherwise, if it's not a file, why does Vim come into play? >
I can think of a few examples: 1. A plugin which displays markers in the sign column might want to use fancy Unicode arrow characters if supported, or a simpler "->" text if not. Eclim, for example, gives options allowing the user to specify the text to use for this reason, and defaults to using ASCII. http://eclim.org 2. A plugin which shows a call tree or something might want use fancy Unicode characters to draw lines between the tree items if supported, or simple ->, +, and | characters if not. http://www.vim.org/scripts/script.php?script_id=2368 is an example of this. 3. A plugin might just want fancy Unicode characters to show specific states, like an open or closed "fold", e.g. the Tagbar plugin. http://www.vim.org/scripts/script.php?script_id=3465 -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
