Just upgraded from Dreamweaver CS5.5 to Dreamweaver CS6, and this is a little thing, but its really starting to grate:
In CS5.5 whenever I opened apostrophes, it would auto-complete the closing apostrophe. Then whilst typing if I typed the closing apostrophe it would just skip past the auto-completed closing apostrophe.
eg: class="page"| <--being the cursor
In CS6 however, when I type to the closing apostrophe it adds another apostrophe without skipping past the auto-completed closing apostrophe.
eg: class="page"|" <-- the exact same sequence of keys typed as above, but results in this.
Is there any way to get CS6 mimicking the same behaviour as CS5.5?
Yeah this is possible, but I'm not using my windows machine right now (I'm in linux).
I'll go back home and follow up immediately, but to the best of my memory the options are in
Edit -> Preferences
After that I think it was in "Code Hints"
One of the options there has the solution to your problem.
Note on Dell/ASUS Machines
Dell and ASUS sometimes implement this 'feature' where if you press ", it gets autocompleted. This interferes with dreamweaver. Then the only solution is to simply turn off code hints.. sorry.. :(
Related
Since a few days (I don't know exactly when it started) the forward key in VS2019 is not working in the code editor. No matter how many times I press it, it doesn't do anything.
It also doesn't work in the seach box in the menu bar (labelled 'Search (Ctrl+Q)') nor in the search box which appears with Ctrl+F.
It does work in other places, like the solution explorer search box (Ctrl+;) and in the resource editor.
The forward slash is working in any other application that I tried (including Visual Studio Code and MS Excel). The question mark (Shift+/) is working everywhere, including in the code editor window. Even AltGr+/ is working (producing the Spanish upside down question mark).
I tried all other keys, including the AltGr combinations. They all work fine. Keyboard layout is US International.
The foward slash key doesn't work in the code editor when typing it on the laptop keyboard, and doesn't work when typing it on an external keyboard, or via an RDP session.
I am running Windows 10 Pro 64-bit, version 20H2, build 19042.685. System is up to date.
Visual Studio Professional 2019, 16.8.3, also up to date.
What is causing the forward slash key to fail?
How can I solve this problem?
(Too long for a comment.)
The OP indicated that the problem was resolved after resetting the keyboard shortcuts, which suggests that / was set as a keyboard shortcut either by accident or perhaps by an installed extension.
However, the question remains in such cases of how to identify what a particular keyboard shortcut is assigned to, in order to turn off just that one shortcut as opposed to resetting all.
Visual Studio does not appear to provide a place to see the list of all active keyboard shortcuts. An alternative is to go to Tools / Import and Export Settings / Export Selected / All Settings and save a .vssettings file with all the current settings. That is a plain text file with extended XML sections, and the keyboard shortcuts can be found under the following node (reformatted for readability):
<Category name="Environment_KeyBindings" ... >
<Version>16.0.0.0</Version>
<KeyboardShortcuts>
<DefaultShortcuts>
<Shortcut Command="View.ViewCode" Scope="Global">F7</Shortcut>
...
</DefaultShortcuts>
<UserShortcuts>
...
</UserShortcuts>
</KeyboardShortcuts>
</Category>
One of the <Shortcut> lines would have been listing / before the reset, and the Command attribute on that line indicated the assignment, so that it could be located and turned off individually in Tools / Options / Environment / Keyboard.
#dxiv Your comment made me check the shortcuts. Tedious job, scrolling through those hundreds of options). Nothing. Then I clicked the Reset button. That solved the problem.
In my case, the CodeRush extension was the guilty party. "Selection comment" gets set to use / upon installation. WTG DevExpress ......
https://docs.devexpress.com/CodeRushForRoslyn/120205/coding-assistance/selection-tools/comment-uncomment-selection
Update:
Also adding a screenshot of it in VS 2022 to help people find it:
Using LibreOffice Writer (version 6.0.7.3), I'm often searching for strings from within largish Writer document, and am using the ctrl+F search. While searching, I'm rather concentrated on looking at where the searched term is found from within the document text, and just press the arrow at the toolbar using mouse to get me to the next instance of the search string. I do this without actually looking at the toolbar.
When I've found the last search string from within the document, LibreOffice Writer only prints darker grey text "Reached end of document" on lighter grey background (sort of "grayed out" thing) on the toolbar. But -- me having eyes fixed on the document text and not looking at the toolbar -- I just keep on pressing the arrow button, and after second or third round get a sort of Déjà-vu feeling. Looking then at the toolbar, while not actually at the last specimen of the searched string within the document there seems to be no indication that I'm half way on my third helping...
What is the advantage of not actually allowing me (while using ctrl+F or ctrl+H at tools->options... or whatnot) to select that to me next should not go past the end of the document (by "next" momentarily becoming "first") without me being properly warned with a "yes-no-whatnot" dialog box that really would stop me from going past end, and be asked if I really want to go for a second helping?
Or have I really (again) missed something?
On my PC (Xbuntu 18.04.4 LTS , Xfce desktop environment 4.12, 32-bit) the same nastiness is found at all possible text editors:
Leafpad, version 0.8.18.1
Mousepad, version 0.4.0
Notepadqq, version v1.4.2
Gedit, version 3.28.1
Thunderbird, version 68.7.0
Firefox 75.0
LibreOffice Writer, Version: 6.0.7.3
The only one that seems to have it the way I wish is:
Notepad++, version 7.5.1 (under Wine), it has a checkbox: "wrap around"
Am I just having too narrow line of vision, or is this what everybody (except me) really only wants...
pekka
PS: I have asked the same question at https://ask.libreoffice.org/en/question/234758/ with no success...
Once again, AltSearch saves the day.
My preferred text editor also has an option: vim incremental search stop at end of file
I am using Sublime Text 3 and every time I press tab it will add an extra tab. My settings are to display tabs as an actual tab (not spaces) and is equivalent to 4 spaces. My issue causes a single tab to therefore create 2 tabs the length of 8 spaces.
For example, if I am trying to indent it will tab twice and I will have to delete one tab.
If I select a block of text it will indent it twice and result in the text being deleted and I have to undo it once to bring the text back.
Also, when using auto complete I normally hit tab to auto complete the first option. It will select the option and do a tab after it. I am not sure if this is an option or setting but its extremely annoying and I have not found a solution yet.
Sublime Text double tabs on tab key press
Sublime Text deletes/removes text on indentation / tab
Both problems are due to a popup (most often the SFTP free version popup for me) hiding in the background. If you make sure to close the popup windows every time they appear you will not get these issues. You could also pay for Sublime or the plugin to remove the popups.
In OSX you can't focus back on Sublime Text without clicking on the popup, so you will never have these problems.
I just had the same issue. I just restarted Sublime and it worked again, no need to reinstall or change any settings.
I just encountered this problem recently, and it appears to only happen on Windows. In my case, the pop-up "Hello! would you like to purchase sublime?" was open in the background, and that caused this issue for me. Once that pop-up is closed, everything works just fine.
Although the question is three months old at the time of writing, this might help people that are still looking for an answer. After having this issue for a while, it annoyed me so much that I traced back the issue.
The double tab issue only happened after a while, so I figured it was triggered by a certain key combination, being pressed wrongly. I've also noticed that the bug only occurred at Windows, not on Linux (Ubuntu).
After disabling all Sublime Text 3 plugins one by one, I've noticed that, for me, SFTP triggered the bug. This happened upon saving, SFTP started uploading, and displayed a evaluation notice. As I've purchased SFTP (and activated it), the double tab bug never occurred again. Even after enabling all other packages, the double tab never troubled again.
This is only one solution to the problem, your problem might originate from something else. Try to disable packages which might cause the problem and try to find the problem that way. It's a lot of work, but might get you the solution.
This solution worked for me on windows:
Just go to
View -> Layout -> Single
as stated in the questions title, we have an issue with VS2012. The problem is that sometimes suddenly some keyboard-input in VS isn't executed properly, if at all.
When the problem occurs, we are only able to type in characters and numbers, but neither are we able to delete them (backspace or DEL), nor to use the arrow key to jump up down a line or to the next/previous character. Overwriting a text which has been marked with the mouse is working.
I have found a very similar Question but the hints stated there doesn't work here. Those are:
Hitting Alt+Enter
Closing and Reopening Editor Windows
Closing the ToolboxWindow
Restarting VS
Pressing ScollLock
The Problem seems to be related to the Stylecop-AddIn. After uninstalling it, the issue doesn't come up anymore. Is there some known workaround? Thanks in advance!
Apparently StyleCop can be used with out Resharper, I didn't know. Very sorry. However, if you look at the documentation for StyleCop, if you right click on your project, click Source Analysis Settings, you will be presented with a dialog to turn on or off all of StyleCops rules.
Here is a link to the actual documentation which has images which helps describe it. StyleCop Settings
I did some find-and-replace actions in my C++ code with visual studio:
only single find-and-replace actions (did not use “replace all”)
only one file affected (did not change multiple files at the same time)
thus, a very simple case!
Then I wanted to undo these changes. So I pressed ctrl-Z one time. This had the desired effect. The latest change (which was still visible in the current screen) was undone.
But I also wanted to undo the remaining changes. These changes where currently not visible on the screen. So I expected the editor to scroll there when pressing ctrl-Z.
But unfortunately the editor did not scroll to the position of the undo when I pressed ctrl-z.
The undo worked, however. I checked by scrolling to the position manually.
Then I tried it with redo. Same result: Redo worked, but the editor did not scroll to the position of the redo.
Finally I tried if this also happens when I undo-redo other types of changes (not made by the “find and replace” functionality).
Result: Undo-Redo worked correctly and also scrolled correctly!
Thus: It seems only changes by the “find and replace” functionality are affected by this problem.
Did you also have this problem and found a solution?
Please help me!
Regards Gerhard
I am having the same thing happen in Visual Studio Ultimate 2012 (Version 11.0.60610.01 Update 3).
It might sound like it's not that important, but it is really hurting the usability of this otherwise great IDE!
PS I've been using VS since the 90s, I still haven't found anything better. I wish MS would put macros back into VS, even if it's VBA (or Python)