I'm trying to find a way to disable Sublime Text 3's minimap for a single syntax (Markdown) only and I'm not having much luck.
I've found a lot of references to adding "show_minimap": false, to your preferences both here and elsewhere but it doesn't seem to do anything regardless of whether I put it in Markdown.sublime-settings or Preferences.sublime-settings (I am restarting Sublime Text after changing the setting just to be safe).
The View/Hide Minimap menu item works globally but I can't set it for a specific syntax.
In most of the threads I've found I see some people saying that the setting doesn't work for them with other people saying it does but none of them seem to have an answer why and how you might fix it.
Has the syntax for that setting changed or has it simply been removed? I don't see it mentioned in the unofficial documentation.
If it does (still) exist is it something you can apply to a specific syntax or does it have to be a global setting?
Thanks!
I've tried both "hide_minimap": true and "show_minimap": false (alone and in combination) with ST2 2.0.2 and ST3 Build 3056 on XP, and nothing seems to work. I don't know the versions/platforms the answerers/commenters on your linked questions were using, but it seems that either the behavior was somehow removed recently, or it's platform-specific (maybe a little of both). I went back through the changelogs for ST2, ST3 Public Beta, and the ST3 dev builds and found a number of references to the minimap, but nothing to indicate that the functionality you're looking for had been removed intentionally.
We don't know if it makes a difference to the developer, but the community maintains an issue tracker on GitHub for things like this. Feel free to submit a new issue, with as much information as possible about what you've tried and the platform(s) and version(s) used, and we'll see where it goes.
If you're the plugin-writing type, there theoretically is a way around this, though. You could write an event listener that checks the scope of any newly-opened files, and if it matches text.html.markdown (or whichever type(s) of file for which you'd like to have the minimap hidden), it could execute the toggle_minimap command, which is what is fired when you select View -> Hide Minimap.
I'm working on that plugin, but it's not coming along very quickly. I'll report back if I can get it to work.
In OS X, Sublime text 3 try:
CMD+`
In Windows perhaps:
CTRL+`
Related
Notepad++ has a uniquely useful feature -- you can open a new tab and paste some text in and it will remember that text forever without saving it to any formal location. I have used it this way for a long time as I do a lot of experimental stuff when working with Hyperledger blockchain code and data.
I also like the style configurator, and particularly the solarized-light theme, which is easy on the eyes.
BUT ... when I create my unsaved tabs (new39, new40, etc...) they get an obnoxious background color that is unpleasant to look at and partially obscures text based on the lighter foreground font I am using. I've been searching for a solution off and on for days, and it is driving me nuts.
So does anyone know how to make it stop treating unsaved data so poorly? It is the one feature that makes me want to just use vscode for everything, despite its lack of the ability to act as a persistent cache for random unsaved data.
** EDIT (March 2019): The first comment on this question helped a bit IIRC but fresh installs seem to behave much better, which makes me think that I had managed over time to confuse the app. But in my opinion the choice now is to simply use VSCode, which has similar properties to NP++ but with a much richer and actively maintained plugin / extension system. So as much as I like NP++, it has aged itself out of my current tool set.
The color of your new window is dependant on the theme you have loaded. You can change these theme colors by going settings->style configurator. My best guess is that the specific attribute is going to be in the Global Styles dialog. It should be easy enough to cycle through those options until the color comes up.
Best of luck.
Ok ... my definitive solution since about mid-2018 is to switch to vscode. The reality a few years after my initial complaint:
vscode implements the feature I was using (persistent unsaved tabs) and runs on all OSs that matter
notepad++ eventually started working again when I reinstalled it, which tells me that its state is corruptible as I experienced
vscode has so many extensions and plugins that it is superior in pretty much every way to notepad++ (Note: my opinion and YMMV), although I do have fond memories of that app
I won't go back and I consider this issue closed.
On the version 8, during the installation process, there's options: check the "theme", you can check all themes. and thereafter, go to "prefereence", find the "Dark Mode", check "enable". That's it, all clear and beautiful.
Sublime Linter suddenly isn't displaying the nice ui highlighting it used to. It also isn't displaying lint messages in the bottom left of sublime. This may have happened after a recent windows update, but i wasn't paying close enough attention to be sure exactly when it occurred. I've followed the troubleshooting section on the documentation, and verified jshint is working in the command line. I've also switched to debug mode but I see no Linter errors in the console. I've also tried switching to manual lint mode, but the "Lint This View" option is grayed out. Not sure what to do at this point. Any suggestions?
You mention that you recently updated your copy of Windows, so it's possible that the Environment Variable for node(and other variables) have been removed or erased, I suggest you check that first.
I've recently upgraded from Xcode 4.3 to 4.4 and I'm about to bash my screen in with frustration.
The problem I'm having is with the code completion. As I type a variable or method name, the completion window pops up with the suggestions like it's supposed to. But if I attempt to use the cursor keys to scroll between the suggestions, the suggestions disappear and the cursor moves in the code, not between the suggestions. If I press enter to accept the default suggestion, it again dismisses the suggestions and inserts a return into the code taking the cursor to the next line.
This doesn't happen every time I attempt code completion, but it does occur more often than not. For a given name I'm trying to complete, it either works or it doesn't (e.g. if I press escape to get the suggestions back, it will disappear just as quickly as the first time it disappeared for that line/name I was trying to complete). When I get to the next line of code, it's a whole new bet whether it will work or not. It seems that the closer to the actual completion of the name I am, the more likely it is to actually work and accept the suggestion or move between the suggestions. Sometimes, if I act quickly enough, I can move the highlighted suggestion one or two lines before the suggestions disappear. I'm aware that if you don't select a suggestion quickly enough that it's supposed to eventually remove the suggestions (on the order of several seconds), but this behavior is not what I'm describing. I'd be VERY happy at this point if I had a single second to actually respond and select a suggestion from the pop-up.
So far I've tried a clean of the project, deleting all of the project's derived data, and restarting xcode. All of which don't seem to affect the behavior. Any ideas? I've searched stackoverflow and google and haven't found any other people reporting this problem ...
Thanks for any ideas,
Will
UPDATE:
After upgrading to the XCode 4.6 release version (and 4.5 somewhere in the middle there), this problem is still present ... and making edits in the left/main editor window is still a work-around.
I am seeing the same with Xcode 4.4.1. It seems to be related to where the completion window pops up. Debugger pane open or closed does not change anything here.
When in the Assistant Editor trying in the right pane the completion windows flickers. Same line of code in the left window works fine. Single editor works, too.
Try upgrading to Xcode 4.4.1. I used to have this problem, but I don't seem to have it after upgrading.
If this doesn't solve the problem, a crude workaround seems to be to put a lot of blank lines at the bottom of each file - the problem seems to occur from frequently when the file is scrolled all the way to the bottom.
There is a fix (at least Xcode 4.6.3): re-create the affected file by deleting it. Now create a new file and copy the content to it and drag it into the project - done. Fixes the issue here. It seems to be tied to certain files.
Sometimes, when I type something in Xcode, it changes the capitalization. For example, I type psSimpBox, and it changes to psSimpbox. That's OK since it's just a variable, but it is annoying. However, here's a real problem: When I type stringValue(), it changes to StringValue(). And, so I get a unrecognized selector error.
Also, Xcode has been recently doing a weird thing where my code starts appearing to run into itself. This is annoying, but has never actually broken things before. I don't think these two problems are related, but it seemed worth mentioning. Photo here.
Any ideas for how to fix this? The main problem is the capitalization, but the others would be nice to fix too...
Not sure if this is worth mentioning, but the app is mostly in ASObjC.
I would guess that you probably have another symbol in your code, e.g. a constant or a global variable, which is spelled psSimpbox, and Xcode's code completion is inserting this symbol after you've typed psSimp.
Regarding the symbol renaming, have you attempted to rebuild the code sense index? Click the project (blue icon) in your project list and press Cmd-I. Click the Rebuild CodeSense Index (or similarly-named) button.
I'm not sure what to tell you about the text running together. I've never seen that before, but I'd suggest selecting a different font (perhaps it's not the default font?) and checking your tab stop settings.
Xcode 3.2 has implemented cursor-level history for the "Go Forward", "Go Backward" commands. Previously these worked at the file level, so you could navigate back and forth through recent files you've been editing. Now they navigate at a more fine-grained level, through the places within files where you have been editing.
The downside to this is if you navigate backwards through the files and make a minor edit, all of your forward history is wiped out, whereas in the past it used to be easy to return to the file you were working on. It also means issuing a lot more commands if you just want to move through files, since you have to skip through all the edit points within each file.
I can't find anything in the release notes or documentation about this new behavior, so does anyone know if it's possible to get the old 'go back/forward by file' commands in 3.2? If not, does anyone have any tips on other ways of easily navigating recent files in Xcode?
Hold down the option key while you click the forward/backward arrows at the top of the code view, this will use the Xcode 3.0 behavior and go back a file at a time.
I had the same question as well and and Rob's answer on holding Option while clicking the forward/backward arrows works well.
I needed a keyboard shortcut though and I've found that Shift-Option-Cmd-left/right works.
From the comments on this blog entry:
Hold down the Option key to get the old file-based Go Forward/Go Back behavior. We rarely change established behavior like this when adding new options, but in this case, the majority of users considered file-level navigation Broken and location-based navigation Correct, based on their experience in browsers and other IDEs. We chose to give what more people considered the “obvious” behavior the pride of place on the keyboard shortcut, but the old way is still there.
-- Chris Espinosa
But like you guys have said, after every keyboard edit, the forward file history is lost. This is incredibly frustrating to me, as this is a feature I have heavily relied on for years, which is now broken. Is there still no fix?
There are Next File and Previous File commands, however their history is also wiped out after an edit. That seems like a bug to me.
This is plain stupid! What's the reason for suddenly change this ? Shift-Option-Cmd-left/right... great, more stupid shortcuts from Apple. I guess I soon have to use Shift-Option-Cmd-Left-Alt-Enter-N for something I use all the time. Can't they just implement a recent file list on ctrl-tab or something, like the Cmd-tab and the app switcher. Why would I want to grab for the mouse when I'm coding ? Still I have to use it lots in Xcode.
Sorry for my rant :)