Strange characters at beginning of line in VSCode - visual-studio-code

I'm trying to learn Spring Boot and I'm using VSCode. I've written some code and changed a file and suddenly these "s: s:" appear at the beginning of some lines. They are not in the file, my code works as expected but I can't remove them in VSCode.
Where are these characters coming from and what do they mean?
I don't even have an idea how to call them and thus I wasn't able to google about them, so I add a screenshot here.
Can anyone tell me something about these "hints" (?)? What do they mean? Can I disable them? Or shouldn't I disable them since they want to tell me something?
Thanks!
Wolfgang

Related

Phantom line display in Visual Studio Code IDE

In VS Code I have a tab with a plain text file I use for scratch while working during the day. I place all kinds code, questions, TODO lists, etc in this file and will reference it from time to time. It's helpful for history purposes.
At any rate, this file has ballooned up to well over 46,000 lines over the years and I'm now seeing this odd phantom line being injected at my cursor. I am unable to select it or remove it. I thought it was being displayed as VS Codes way of letting me know that a software update was available but when checking that was not the case. This is what it phantom line looks like, it seems to contain a history of CSS classes used over the years which is odd.
If I restart VS Code it goes away for a little while but then reappears. I have a feeling it might be because of the number of lines or perhaps memory but can't say for certain.
Has anyone else seen this behavior? I've probably enabled some setting by mistake and have no idea how to disable it.
Any suggestions would be greatly appreciated. Thank you!
Turns out it was the HTML End Tag Labels plugin that was trying to auto complete some HTML that was somewhere within the 46k lines.
I would have thought by identifying the file as type Plain Text, the plug-in would ignore trying to close HTML tags (since its not an HTML file) but alas that's not the case.
Thank you Mark Ahrens for the tip!

Indentation for files that don't have a registered formatter

It seems that I am getting this problem since version 1.18, honestly I don't remember.
With VSCodeVim installed I used to press the = key to get my code (Elixir, embedded elixir, ...) indented properly.
Am I missing something, like a configuration, that would allow me to re-indent my files without having a nagging "Formatter for file x not installed".
This is honestly the only things that nags me with VSCode so far, love the speed, the capabilities and the UI...
Just posting my comment as an answer
Try using the reindent lines command. This command should work for many languages even if you don't have a formatting extension for that language installed
Select the contents of file.Bottom right corner shows spaces/tabs: 2/4. You can click on that and indent the whole file.

Unable to use Heroku from the commandline

Currently I'm making a Facebook app with Heroku, I did as the instruction says, but then I get stuck after installing heroku-toolbelt. I opened cmd.exe, typed something like 'heroku', but it results in an error as follows
C:/Program Files/Heroku/bin/heroku:15:in []': code converter not found (UTF-16LE to Windows-1258) (Encoding::ConverterNotFoundError)
from C:/Program Files/Heroku/bin/heroku:15:in'
I don't know what is the problem, searching around but there's no luck at all.
Does anyone have an idea of what I am doing wrong?
Just typing heroku in the command line won't do anything. First go to the directory where you have set up a folder to put all the files of your app from command line using DOS commands. Then type heroku login. It'll prompt you for user credentials for your heroku account. Enter those correctly and you're good to go from there.
I encountered the same error as you did. Windows-1258 is text code for Vietnamese language. I figured something like to stop converting text code automatically to Windows- 1258.
So here is how it works for me. Hope it works for you too. Simply go to Control Panel --> Change keyboards or other input method --> Administrative tab --> Change System Locale (from Vietnamese to English (United States) for example). Restart and work like a charm!
I need to dig around some more and find a way to build in this kind of functionality, but as a work around, if you open a new command prompt and type "chcp 1252" prior to running any commands it will switch command.exe to a compatible code page. That should prevent encoding errors of this type. Sorry for the inconvenience, but it should at least function as a stop gap and I'll work to integrate a fix into the tool itself. Thanks!

Macro not working as expected in Notepad++

I just installed notepad++ and i am having some problems with macros in it.
i have a simple text file below:
hi
i am here
this is the third line
i kept the cursor at the first line before "hi".Now i selected start recording macro in the menu.i typed 'hi' before 'hi'(the actual word in the line) like below and pressed [Home] key in the keyboard and then pressed down arrow.Now i selected stop recording macro from the menu
hihi
i am here
this is the third line
but when i run the macro i am getting the following output
hihi
hˆi«i am here
hˆi«this is the third line
Could anybody please tell me where is the problem?
Upgrade to, at least, version 5.8.2 where that problem was fixed. I was experiencing the same problem, upgraded to version 5.8.5 and the problem is gone.
http://notepad-plus-plus.org/release/5.8.2
Fix macro recording bug for the non-ASCII characters.
same here as for Matt. For language, I was in normal text.
As mentioned in my comment at top, I have also been experiencing this same issue. Strange characters inserted when playing back a macro. This worked OK with previous versions, but appears to have been a bug introduced with version 5.7
It does appear to be an encoding issue. I have been able to workaround this issue by switching to UTF-8 encoding whilst recording the macro - as mentioned in the comment of this bug report.
This has been reported as a bug several times recently. Many are still open, however, one is reported as fixed. And is reported as fixed in the current release (5.8.2) - which also introduces several new features as regards macros. However, nothing later than v5.7 is yet available from the auto-updater within Notepad++ itself. However, you can manually download the latest installer from SourceForge.net.
I turned off the auto complete feature and this fixed the issue for me.
How do I stop Notepad++ from showing autocomplete for all words in the file
I had a problem, I typed in some code and it came out wrong in macro.
Then I neglected the advice to type the code and not paste it, and so I copy/pasted the code I needed and it worked fine.
So my advice: write it somewhere else and copy/paste when you start macro.

Using css_color plugin for vim causes omni completion not to work

I am using the css_color.vim script with gvim 7.2 on vista. Because of this script I am not able to use omni-completion for css that came with the gvim I installed, which works perfectly fine if I rename the css.vim file to css.vim.bak or something.
I usually open omni-completion drop down using <C-x><C-o>, but with the css.vim, when I hit <C-x>, vim seems to go in a "temporary" normal mode, I dont really know what it is doing, but it is definetely not giving me the omni-completion drop down.
I tried search for <C-x> in the css.vim file but nothing. I dont have much experience with vim scripting, so any help appreciated.
I think I found the answer... Commenting the 3 lines at the bottom of the script seems to fix this. I can now use omni-completion in css files along with this plugin.
For anyone that comes along looking for this later on, these are the lines I commented...
autocmd CursorHold * silent call s:PreviewCSSColorInLine('.')
autocmd CursorHoldI * silent call s:PreviewCSSColorInLine('.')
set ut=100
Couple of ideas.
for your first issue
run
:scriptnames
wtih the script on an off and look for differences. It's possible you've placed the script in the wrong directory or its overriding a system wide file.
Secondly for your , issue. run
:verbose map ,
to find where the , map has been defined. Looking at the css script it's possible these are separate issues