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

Not working for me (windows 7, gvim 7.3) #17

Closed
erezsh opened this issue Feb 25, 2012 · 7 comments
Closed

Not working for me (windows 7, gvim 7.3) #17

erezsh opened this issue Feb 25, 2012 · 7 comments

Comments

@erezsh
Copy link

erezsh commented Feb 25, 2012

I use windows 7, gvim 7.3.46

After installing this plugin (using pathogen) I get a lot of error messages of them form:
Invalid argument: pyNiceOperator "" conceal cchar=ă■■

It goes on for about a dozen messages, after which vim is working, and some substitutions take place, for instance "sum" is replaced by "ā" or something of that nature, and "in" (for example) is not replaced at all.

@ehamberg
Copy link
Owner

I'm not very familiar with Vim on Windows, but could you try running the command :set enc? in Vim? That should hopefully say UTF-8 which is a Unicode encoding.

@erezsh
Copy link
Author

erezsh commented Feb 25, 2012

You're right, :set enc showed that I had latin-1 as the default encoding.
Adding either :set enc=utf-8 or :set enc=unicode before your script took care of the errors.
Unfortunately, the symbols still don't appear correctly, they all show up as small boxes instead.
This happens with every font I tried, including Inconsolata and Proggy.

@ehamberg
Copy link
Owner

That's strange. Are you using UTF-8 encoding in the actual source files you are writing? If you need to use latin-1 because you are working with old code together with others and the files need to stay as latin-1 (or other legacy encodings), perhaps setting the fileencoding option to be latin-1 and the encoding to be UTF-8?

The latter should only set the encoding used internally in Vim – when fileencoding is different a conversion is done on save, but since the non-latin-1 “conceal” symbols are never written to the file anyway, this should not be a problem, I think.

Of course, if you always work with UTF-8, this should never be a problem.

@erezsh
Copy link
Author

erezsh commented Mar 3, 2012

This happens with UTF-8 sources as well..

@mcelrath
Copy link

I had this problem too, on linux. It appears to be a conflict with the LatexSuite package for vim. (for me it was an old version in my ~/.vim directory dating from 2006) I removed this old version from .vim/ and set up the newer version following http://jishuzhai2164.wordpress.com/2012/03/23/vim-latex-suite-i/

Now the two are happy with each other, and I'm looking for Conceal plugins for latex syntax too!

@erezsh
Copy link
Author

erezsh commented Jan 23, 2013

I decided to give it another shot.
Apparently both Proggy and Inconsolata just don't show non-latin unicode correctly (at least on my system).
Now I'm using DejaVu and everything works just fine!

@erezsh erezsh closed this as completed Jan 23, 2013
@ehamberg
Copy link
Owner

erezsh: Cool. Glad to hear that you got it working! :)

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

No branches or pull requests

3 participants