This should be a Bug, because I can reproduce it with my friends.
I just set allowsNonContiguous Layout of NSTextView. layoutManager to true, and that's the problem.
In the editor, I first enter N blank lines, that is, press N times to return. Then go back to the second line of our input, and press any key at the moment insertion Point disappears, which will make my insertion Point incorrect.
Here is my demo:
https://github.com/iiiDD/TextViewDemo
I had the same problem. I’ve detailed how I’ve fixed this bug here : NSTextView cursor doesn't appear when typing text on macOS 10.14
Related
When I select a block of code in VS Code I get the following:
png
At the end of each line, and at the beginning of the selection, the editor selects an extra space (that isn't actually there). How can I stop it from doing this? I want the selection to be exactly the text that I select and nothing else.
The question is, how do I move the selected block of code by one or several tabs, but not to the right (which is done by selecting a code and pressing Tab key), but to the left? Without selection each line one by one and deleting whitespace?
Moving parts of code from one place to another with differences in indent levels is a bit hard without knowing the shortcut.
What I mean (Imgur)
Thanks!
For what you want,
Shift+Tab
should do the trick. However, I would like to recommend this extension which I find easier to use when formatting blocks of text: Indent One space
Note however this extension only indents selections by exactly one space, forward or backwards.
I edited a document from a client with some highlights then later decided to remove the highlights for comments instead.
For whatever reason, the document highlighted a number of bullet point and numbered list sections which I could not revert when I attempted to select the entire document and change the highlighting to 'No Fill'.
The highlighted bullet point/number lists did not allow me to select them to revert.
Searches on Google seemed to result in a ton of convoluted "[Solved]" responses on their forum which didn't fix the issue for me (or resulted in a TLDR response from my brain...):
Google Search: open office remove highlight bullet lists
[Solved] Yellow highlighting won't go away
[Solved] Bullet highlighting will not go away.
[Solved] Surprise Yellow Highlighting on Bullets & Numbers
Permanently highlighted bullets.
[Solved] Oddities Involving Bullets/Outlines & Font Styles
[Solved] Bullet color
Seriously... what the heck!? How can this be so hard? So I decided this issue needed some serious StackOverflow help...
Version info:
Apache OpenOffice-4.1.4
AOO414m5(Build:9788) - Rev. 1811857
2017-10-11 20:12
So after all that...
I figured it out. But its still crazy how it's not answered very clearly in the resources above... I hope this helps someone not spend as much time on this in the future.
If you double-click the first bullet/number of the list... it appears to select the first word of the first item of the list, BUT you'll see that it also selects the list bullets/numbers with a dark gray highlight.
Now selected, you can remove the highlight from the list.
Selecting all of the document doesn't select the numbered/bulleted lists.
Well, most of this solutions didnt helped me.
But I found a simple way to fix it:
Select Highlight option.
Position to the left of the bullet until the cursor converts to a white arrow.
One click to highlight entire text line. One click again to un-highlight the entire text line (including the bullet).
Select the highlighted area, rather "highlight" the highlighted area and press CTRL+Q, it is a paragraph formatting issue and this should remove all formatting from the selected area.
The answers above didn't work. Try this (mouse-select means left-click and drag the selection of words, aka highlighting but wanted to avoid confusion):
Turn on paragraph marks ¶ in Word
Add a clean paragraph before the highlighted-bullet sentence. (Clean means it's unbulleted, without colour highlight, unformatted)
Mouse-select the entire bulleted sentence containing the highlighted bullet. Make sure the selection also goes left before the highlighted bullet to include the clean paragraph above it i.e. your selection should include the ''¶'' mark of the clean paragraph you created in 2.
Apply white/clear/no-colour highlighting.
It's actually pretty simple though I was having trouble with it myself. Just select all the items of that particular bulleted/numbered list and highlight them. Then select the items again and remove the highlight. Doing that removed the highlights from the bullets too for me.
Super frustrating but here's the fix that's always worked for me (even with .doc or .docx file):
Double click the bulleted/numbered list item so they all highlight
Ctrl + Spacebar (resets character formatting)
Apply any needed formatting (font type, bold, etc.)
This will keep the formatting on the paragraph (indents, header type, etc.) but will just allow you to change the format of the actual text that is highlighted - which is likely all you want.
Hope that works for you!
The highlighted text in the paragraph that you have highlighted past the period id causing this issue. If you want to keep the last sentence highlighted but remove the highlight bullet just remove highlight on the period at the end of the paragraph and the highlighted bullet goes away :)
(If you can) Start from above, add in a new clean bullet point, copy/paste the desired text from the problematic highlighted bullet point, then delete the problematic highlighted bullet point altogether.
So I am having a problem. This is what I can create on one of my laptop:
On another, when I created something that has {TC} in it, the whole field code disappeared.
For the example above, if on the other computer, both are running Office 2010,
I can input the code to create the table of content from:
{TOC \f \h \z \f 1\t "Heading 1,1,Heading 2,2,Heading 3,3,Title,1}
to
{TC}
The moment I type in TC, the whole {} disappears.
Other field codes work just fine, except for {TC}. So my question is how do I get {TC} to show on my other laptop?
Thank you for your time.
Apparently, I found my answer.
When I searched google for my answer, most sites give this as a solution:
For Word 2010, go to File->Options->Advanced
Under Show document contents: Select "Show field code instead of their values"
This is the equivalent of pressing Alt+F9, which DID NOT solve my problem.
Apparently, the solution to get {TC} to show in your document is in:
go to File->Options->Display
and check to always show HIDDEN TEXT.
I hope this helps someone in the future.
Yeah, the disappearing TC code is annoying at first -- seems like it's broken. Other codes work, but why does that disappear, even if entering manually? Word instantly sets TC code to Hidden, even the field code itself.
To temporarily toggle this visible without permanently changing your display to show Hidden Text, you can use the normal Ctrl-Shift-8, which toggles display of spaces, paragraph marks, tabs, and Hidden Text, on and off. This is a good keyboard shortcut to have in your standard back of tricks anyway. It is frequent in Word that you need to toggle paragraph marks on and off, because paragraph formatting is attached to the Paragraph mark, and when they're hidden, it can be tricky to fix various formatting issues.
The original post was a few years ago, but I fear things have gotten worse since then, not better. I am using Word 365 v2201, which should be up to date. The other day, I wasted hours on trying to resolve this issue with TC field codes.
First I tried entering them using Insert > Quick Parts > Field. Word creates what looks like a field code, but it behaves as normal text. Messing around with the various controls to toggle field display and hidden text etc etc, has absolutely no effect. It is basically a faux field. And of course, it is completely ignored when compiling the TOC.
Next, I tried entering it manually, by using Ctrl + F9 to either create a blank field or convert some existing text into a field. Same result as above.
As with the original post, this seems to afflict only the TC field code. Other codes work fine, including TOC. And if I create a TOC field, then edit the code to TC, it immediately loses its properties as a field. If I then put the O back in, it immediately behaves as a field once again. Unlike in the original post, adjusting the settings for field display and/or hidden text, have no impact.
In the end, the only solution was to create the field using Alt + Shift + o to open the Mark Table of Contents Entry dialog box. And finally, this works!
I'm trying to use the multi cursor functionality of vscode on a large(ish) file.
the file is too large to select every line individually with ctrl-alt-up or down. In sublime-text I would select everything and push ctrl-shift-l. Is there a similar thing in vscode. I've tried using a regex search for ^, but that gives me an error stating "Expression matches everything".
The command Selection / Add Cursors to Line Ends altshifti will put a cursor on every line in the current selection. (For mac use optshifti)
Tip: You can pull up the keyboard shortcut reference sheet with ctrlk,ctrls (as in, those two keyboard combos in sequence).
(For mac use cmdk,cmds)
Hold Alt+Shift and select the block. Then press End or Right button.
You get selected individual lines.
I use version VSCode 1.5.3 in Windows.
Hold Alt+Shift+i
Hold Home (fn+-> Mac) for right-most or End for left most(fn+<- Mac)
This feature is actually called split selection into lines in many editors.
Sublime Text uses the default keybinding, CTRLSHIFT L
VSCode uses ALTSHIFTI
For Atom you actually need to edit your keymap to something like this
'.platform-win32 .editor, .platform-linux .editor':
'ctrl-shift-L': 'editor:split-selections-into-lines'
Real Lines vs Display Lines
First we have to understand the difference between Real Lines and Display Lines to completely understand the answer of the question.
When Word Wrap is enabled, each line of text that exceeds the width of the window will display as wrapped. As a result, a single line in the file may be represented by multiple lines on the display.
The easiest way to tell the difference between Real Lines and Display Lines is by looking at the line number in the left margin of the text editor. Lines that begin with a number correspond to the real lines, which may span one or more display lines. Each time a line is wrapped to fit inside the window, it begins without a line number.
Cursor At the Beginning of each Display Lines:
Cursor At the Beginning of each Real Lines:
Answer to the Question
Now that we know the difference between Display Lines and Real Lines, we can now properly answer the actual question.
Hold AltShift and select the text block.
Press Home to put cursor on the beginning of every Display Line.
Press End to put cursor on the end of every Display Line.
Press HomeHome (Home twice) to put cursor on the beginning of every Real Line.
Press EndEnd (End twice) to put cursor on the end of every Real Line.
Please understand that AltShiftI put cursor on the end of every Real Line.
Install the extension Sublime Commands.
[Sublime Commands] Adds commands from Sublime Text to VS Code: Transpose, Expand Selection to Line, Split into Lines, Join Lines.
(Don't forget to add the keybinding(s) from the extensions details page to your keybindings.json)
Doesn't VS Code already have a "split into lines" command?
Yes, yes it does. However it differs from the one in Sublime.
In VS Code, when you split into lines your selection gets deselected and a cursor appears at the end of each line that was selected (except for the last line where the cursor appears at the end of the selection).
In Sublime, when you split into lines a cursor appears at the end of each line (with the same exception as in VS Code) and the selection is divided on each line and "given" to the same line.
I have the same problem, i'm used to Alt + drag to do 'box selections' in visual studio but it does'n work in code.
It seems to be impossible for now to do it differently than by selecting every single line.
However plugins should be supported soon so we will likely see a plugin for this if not implemented directly by microsoft.
From visual studio uservoice forums:
We plan to offer plugin support for Visual Studio Code. Thank you for your interests and look for more details in our blog in the coming weeks. http://blogs.msdn.com/b/vscode.
For the preview we are looking for exactly this type of feedback. Keep it coming.
Sean McBreen – VS Code Team Member