As you can see, while I type I get shown the signature of the function and the suggestion. But very often they cover each other.
Moreover, suggestion cover a lot of lines below the line I'm currently in, which could NOT be useful (e.g. I'd like to refer to them)
Is there a way to fix both issues? like pushing floating windows on the rightmost part of the currently window, where probably there are fewer lines of code ?
I think It could be really useful
it's not neovim version's problem.
Related
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".
Trying to make working version similar to revision. After I did Coppy current change from right to left I still see grayed line that according to my understanding shows difference. In reality these lines really became identical.
Why they are shown as different:
Wondering if there's hidden characters at play.
If you don't have an easy method at hand to view hidden characters, might be worth pumping each line into an ascii converter, there's one here:
Is there any way to mark Matlab code (in Matlab) via some kind of add-on? I'm looking for something similar to what Microsoft Word has with its "Review" mode where you can highlight a certain phrase/section and make a comment on the side. When I say "comment", I don't mean the regular code comments that you do with "%" in Matab.
I've googled for this, but I couldn't find anything. Anyone know if something like this exists that I may have missed? It would really help me when I'm reading someone else's code and I have to keep track of things / make comments for certain lines. Even if commenting isn't possible, it would be nice to be able to highlight certain lines via some kind of "highlighter" like the one in Word.
No. This isn't possible.
In fact, most editors and IDEs (if not ALL of them) that I know don't even support this feature as each IDE will have to be specific in the way this is implemented (à la Trojanian). The only thing that I can think of is if you print out the code in PDF, then use bubbles within the PDF viewer to tack on your comments.
However, if you want to highlight a specific line in your editor, you'll have to set this up in your settings. Go to preferences, then in the Editor / Debugger options, choose the Display option, then choose Highlight Current Line. Choose whichever colour you see fit. I'm running MATLAB R2013a on Mac OS, and this is the window I get:
You'll see the Highlight Current Line feature. Change that to whichever colour you want. I have it as gray because I do like having the current line highlighted.
Why doesn't Matlab put your variable's names on the top of it's suggestion like Eclipse. It's not smart to put everything in alphabetical order. Scrolling down to the function/variable you are looking for sometimes takes more time than typing it yourself. Besides it should also complete a function by writing the parenthesis and placing the courser in the middle of the parenthesis. Is there any way I can change the preferences to that it would act like Eclipse?
In short: No.
Matlab is not eclipse and it will never be. M-code is not Java code.
If you want to you can use eclipse to edit your m-files, however it will not behave as you describe in your question. This is because m-code is not as strict as for example Java, this is on one side the downside of Matlab as you describe above, however the positive side of this is that it offers flexibility during development.
Using a tab after typing some characters would narrow the possibilities for auto-fill, if you have selected this property in the Preferences-Keyboard window.
I have Eclipse 3.7.1 classic, with added Android plugin and HTML editor plugin.
If I have a long line of text in the HTML editor and scroll the horizontal scrollbar to where I want to be, when I place the cursor there and start to type, after a short pause it keeps resets the horizontal scrollbar to the far left. It doesn't do it all the time, but it is frequent enough to be annoying.
Why is Eclipse doing this, and how can I stop it?
Not really an answer but I have the same Problem since yesterday. I don't know the cause or any solution but ende up splitting all my lengthy strings using either "\" or "+". That "fixed" the problem and resulted and better readability of the code.
Good Day
Redfox
In my case this started happening after installing the Coffee Bytes Java Folding extension/plugin, and eventually it just annoyed me so much I turned it off...and the scroll jumping stopped.
It was a shame because I wanted folding of 'Regions' like in .Net and that extension gave me that ability. I've not looked for an alternative yet, but anyway I'm rambling - see if you have this extension enabled under Preferences > Java > Editor > Folding.
When this happens to me, the problem is that I'm not steady enough in my line selection. So I'll briefly be selecting two lines of input. And when the other line of input is shorter or even empty, it resets to the rightmost edge of that line (which if empty is the far left). Being very careful when moving horizontally can work but is difficult to maintain. Perhaps turning down the mouse sensitivity would help.
Searching for "eclipse line wrap" found that Alt Shift Y turns line wrap on and off. There also seems to be a button on the toolbar. See Does Eclipse have line-wrap for more details.
As others have noted, changing so that the lines aren't wider than the window also fixes this. But when you're in a situation where someone else sets the line length, toggling line wrap can be a quick and easy solution to this problem.
This of course assumes that you are having the same problem as me and not something caused by a plugin or other issue.