So my problem is that the error window in pgAdmin is small.
Although I managed to extended it I can't view everything written because the error page refers to the problem itself in the last line which I can't view.
I really don't know what to do. I've been trying to find a solution for hours.
Any answer would be much appreciated.
Edit: I actually solved it with File->RunTime->Zoom out(multiple times) so then the window could show everything because the letters were smaller. I wish I had seen this option earlier!
Related
I am having a hard time on VS code due to issues with the cursor. It keeps jumping around while I am typing and makes a mess of my codes. I have tried reloading the window and even restarting my system multiple times but its no help at all. I have also disabled my extensions to no avail.
Secondly, when I copy and paste my codes from one file to another, it all gets jumbled up and almost impossible to rectify as my cursor wont even let me type.
I would appreciate any help with this as I have struggled for months now with no success and this is my last resort. I look forward to your kind help. Thanks
Last Edit:
It appears I've had an F8 key being pressed non-stop, and it seems to be a shortcut for "Go to Next Error or Warning".
I've wrote a piece of code, it has an error which I'm aware of. Specifically, I'm trying to run a function which doesn't exist yet:
All good, I'm glad it is telling me there's a problem, but... I wish to keep writing stuff in the same file and I simply can't. Every so often the GUI keeps sending the caret (the place where my next piece of text will be written) to the beginning of the problematic piece of code. Simply speaking, I can't keep doing anything until I resolve the problem, since it forcefully intrudes my every action. Even more than that! When I go to a different file, with means of fixing the problem and adding the missing function, it once again interrupts me and forcefully takes me back to the problematic file to show me that there's a problem (??!?!?!). Closing it with "Esc" only closes it once, but it keeps on returning every several seconds.
I don't think it was like that just a week ago, and I didn't install any new plugin since then. I'm currently using the last version, 1.58.2.
How do I stop this work-flow-intruding behavior?
Edit:
I've kept on working for some time and it turns out the issue is much bigger than that. Whenever I type a name of some property, half way through some wild problem would jump and tell me "Cannot find name 'quar'. Did you mean 'quarter'?". The issue is basically the time delay of the problem checks, it's non-existent. It's also too intrusive, moving the caret and jumping between files to show me the existing problems. It's very recent, it didn't happen earlier this week. I've tried disabling different plugins I have and they're not the cause.
This is not exactly your issue, but could be related to what you are experiencing: https://github.com/microsoft/vscode/issues/68776
Try disabling the Outline Explorer and see what happens then.
Furthermore, see if disabling autosave improves anything.
"press the restart button to restart Visiual Studio Code and enable the setting."
Now Im going to preface this by saying that this is quite possibly the most annoying thing I have ever experienced in my years computing.
I'm new to VS Code and as such I am knee deep in my settings.json a lot of the time. Especially moreso when Ive just installed a new extension and it comes with loads of parameters, alnd all sorts of goodies - sort of like I did today when I got home from work.
I open settings.json. I add a comment line indicating a new section for my new extension's myriad of settings I half understand, and move any auto-generated config settings from the bottom to the freshly minted position. I start typing, the widget pops up letting me know about all 70+ settings I can fiddle with as much as I please.
I hit tab on the first entry, it goes down. Tab again, "true" goes down.
"A setting has changed that requires a restart to take effect"
OKAY no problem VS code. Quick restart, back to my config.
I start typing the extension again, I get 200ms in or however long it takes for that widgit to appear, and
"A setting has changed that requires a restart to take effect"
I watch the text in my editor contort as the settings are unloaded and reloaded and unloaded again.
I got the first 4 characters of the extension name typed out before this lovely notification reappears.
Now,
when this happens a few times its a little irritating.
BUT THIS IS CONSTANT .Every. Single. Line. I try to add. Each and every setting. Sometimes 2 or 3 times before I actually get the string down, never-mind its value.
I don't know what to do, I am legitimately going to rip my hair out. This is by far easily up there with one of the most frustrating things I have ever been forced to endure. It is relentless.
I dont know what else to do. Ive tried all I can think of.
I just want to learn and use my new extension.
Please for the love of anything help me.
Please.
First and foremost: I'm still an emacs noob, so please consider me misunderstanding things.
I'm currently experience weird rendering errors when using child frames in emacs. This problems is consistent over many packages. Whenever a package creates a child frame, it get's rendered poorly.
Example using company-box:
Another package I've the same experience with is lsp-ui or specifially lsp-ui-doc. For the sake of making sure no other package is causing this I'm using this minimal setup. The artifacts still remain:
To me it looks like that the size the child frame should have is the portion thats being displayed + the black artifact (or grey in the lsp-ui pictures. But somehow it only displays a portion of the content correctly and blanks out the rest. You can see that the actual content in the portion being displayed is cut off.
I have to note that this doesn't happen 100% of times. But about 80% I guess. Sometimes the frame is displayed correctly.
I have absolutely no idea what is causing this. One thing that might be of interest is my setup:
OS: Windows 10 (using WSL)
Emacs: 26.3 (running in Ubuntu 18.04 LTS)
X Server: VcXsrv 1.20.5.1 (But I've also tried Xming 6.9.0.31 - same result)
I've trouble finding any information about this online. There's at least one person having the same issue using company-box. He's also launching emacs using wsl and VcXsrv, which makes me think this may be related to WSL/VcXsrv.
I'd appreciate any help.
for anyone who is experiencing the same issues - I have found a solution.
The problem is VcXsrv/Xming. Details about this bug can be found here.
The solution is to switch to another Xserver. I'm currently trying MobaXTerm which doesn't have that problem. However there might be other, better alternatives.
However it's good to have found the culprit in this case for anyone who is facing the same issue.
There's a little column to the right of your code window which shows all of your code at a huge glance. It's kinda handy to click to jump to a certain portion if you have a large file....ultimately, especially when I have 2 windows side by side, it takes up a lot of useful space. Anyways I can remove this? (Having a hard time researching it because I don't even know what it's called)
Okay...I tried some different search terms and found this article.
https://stackoverflow.com/a/44774811/8887398
It's called "minimap".