I'm having an odd issue in sublime text 3. I have the indention guide lines turned on, but for some reason the guides are not showing for every indention level.
I have my indention level set to four spaces. I double checked the number of spaces for the tags (b/c sometimes if you're missing a space sublime doesn't recognize it as a proper indention) and the number of spaces is fine:
I've been reading through the docs and looking in the forums but I can't seem to find a solution for this problem.
Anyone have any ideas?
I had exactly de same thing and found that I didn't have the font I had configured in font_face (consolas, in my case) so I changed the font to one I actually had (inconsolata, in my case) and the indentation guides worked perfectly (opensuse 42.2).
Related
In the Pine editor, the cursor if offset to the right by some characters. In my case, it is 5 characters at the beginning so a line, and over 20 at the end of the line. It seems that the spacing the cursor thinks it needs for a character is about 10% more than the spacing it should be using. I have tried KDE, Xfce, metacity, etc., and disabled/enabled GTK stuff in Chrome, and various browsers, but all exactly the same.
I have seen several similar complaints regarding GTK/Linux web editors so it is necessarily a Pine editor issue, but I have no problem with every other web-based editor, which is why I am asking here , as it is only a problem for me with the Tradeview's Pine editor.
Are there any users here who have experienced this same issues, and if so, was there a solution? In my case, I am using Arch/Manjaro Linux.
Alternativley, is there a reccomended editor for Pine?
Thanks
I am editing files in VSCode (version 1.16.0) which were originally created in Emacs with indent-tabs-mode set to STANDARD. This was not set by me, but inherited, and, as far as I could tell, spaces were being inserted. Every indentation was 3 spaces, and the TAB key was used to achieve the indentation. That is what you saw in Emacs or if you more/cat the file from a command prompt. Like such:
data a;
set b;
x = 3;
run;
We have recently moved from a Solaris environment to Linux (Redhat 6) and, for a number of reasons, it behooves me to stop using Emacs in favor of VSCode. I have "editor.detectIndentation": false set in VSCode, with tabs inserting spaces, and the number of spaces set to 3.
When I open up these files in VSCode, however, the indentation looks off, like
data a;
set b;
x = 3;
run;
and, thus, I've begun a process where I am re-indenting everything, so they will look right in the VSCode world. The fact that this will create a bunch of whitespace-difference noise in version control is irrelevant in this particular case. Progress demands we move on and live with some short-term pain in that regard.
So, I delete all indentation and re-indent with the tab settings outlined above and all looks well in VSCode. Everything's lined up. I have 3 spaces per indent. Back to my first example above.
However, if I more/cat out the code now, it appears as if hard tabs have been used, so it looks awful (like my second example). And we do a lot of quick code inspection thru this means, so it's a highly undesirable effect. Why is this happening?
Everything I've seen online focuses on how VSCode handles soft/hard tabs, or problems with that functionality. Essentially, people are asking how to get the settings to what I've set above. I haven't seen anyone with my problem -- i.e. I believe I have the VSCode setting correct, it looks good and proper in VSCode, but looks like hard tabs were inserted instead of spaces when a simple more/cat is performed. (As a side note, if I open the files in Emacs after this, it also looks like hard tabs were used)
SublimeText is putting an ugly black color on all of my leading spaces and tabs. This started happening a few days ago. I don't think I changed anything.
Can someone help me to make my SublimeText look beautiful again?
The problem was the Highlight Whitespaces plugin. When I removed that, then the ugly black spaces went away. Strangely, I've had that plugin installed for months and it never caused a problem until now.
I have installed MacVim, and https://github.com/skwp/dotfiles (including all the dependencies such as zsh, etc). and I am having trouble getting auto complete to work.
When I'm typing
<tit a pink box shows up with <title>Index</title> and according to the https://github.com/skwp/dotfiles documentation pressing tab will make it autocomplete. Which sometimes works, sometimes it just adds two spaces, however that's not really my question.
When it does auto complete it turns it into
<<title>Index</title>> notice the two < and >
How can I fix this?
Wow… 79 plugins? Really?
At a low level, your problem is that you give someone else too much power over your configuration, your toolset and your workflow.
At a higher level, you are probably misusing your config's auto-completion feature. I think that you have a conflict between the neocomplcache, delimitmate and snipmate plugins: the 1st deals with auto-completion, the 2nd automatically closes pairs of characters (<>,"",()…) while the 3rd does "tab-expansion" on the tit keyword.
Basically, I believe that you are supposed to type tit<Tab> instead of <tit<Tab> to avoid triggering delimitmate.
I'm using gVim on Windows 7 and I recently added some fonts to C:\Windows\Fonts. In gVim, I can :set guifont=Font_Name some of them and it gets set as expected, but for several others I get E596 Invalid font(s): Font_Name.
Obviously the fonts which do not make the cut either have or lack some property which gVim requires of fonts it loads. Does anyone know what those are, and what, if anything, one might do to modify an existing font so that it meets those criteria?
In particular, the following fonts fail:
Cronos Display
Liberation Mono
Monospace
I will not be surprised to learn that these fonts are incomplete or missing something that Vim requires. I just have no idea what to check for.
Did you read :h guifont?
I've already made wild guesses in another very similar question but I couldn't find it ATM. In short, GVim on Windows is very picky about its fonts: it wants a monospaced font but something in the fonts you have tried is not to its liking.
In this case, "Cronos Display" is obviously not monospaced so there's no way it could work. I don't know about "Monospace" but I'm surprised "Liberation Mono" doesn't work.
You could open the fonts in a font editor to seee if they are really monospaced.
Here is a similar question I asked, weirdly enough, in the same week.
In my case it boiled down to 2 things that I was able to tweak using FontForge:
Having the right PANOSE tag (whatever that is) of "Monospaced" instead of "Even Width"
All the characters have to have the same width. I was able to fix this by doing the following:
Select all elements
Element -> Validation -> Find Problems
Select Random -> Bitmap/outline advance mismatch
Select BB -> Check Advance: 600
Select OK
In my case, it brought up one by one a list of all the elements that had 0 width and gave me the option to fix them to have 600 width.
Changing these seemed to work for me, but I may have committed some sort of fontrocity.