I use Manjaro/Gnome and had Super+F to start the file manager (Files). I decided to give it a try to VSCodium and now the shortcut starts VSCodium, not Files.
I searched in Gnome Settings>Keyboard and the shortcut assigned to Files is still Super+F, but it is not working, all I get is to start VSCodium.
Any ideas on how to fix it?
Thanks
After some research, I found that VSCodium or VS Code installation sets themselves as the default application to deal with directories.
To go back to default/personal shortcuts you must edit mimeinfo.cache found in the /usr/share/applications directory.
Look for the line
inode/directory=codium.desktop;org.gnome.Nautilus.desktop;ranger.desktop;
and delete codium,desktop;... Logout and login again.
That will fix it.
Related
I have cygwin installed on my new Windows-10 PC and I have a file "foo.bash" on my desktop that I need to be able to double-click on and have c:\cygwin64\bin\bash.exec open it (foo.bash is a shell script being interpreted by bash.exe). On my previous PCs I simply double-clicked the program, browsed til I found/selected bash.exe, clicked the "always use this app" button and from then on double-clicking on foo.bash would always open it using bash.exe.
On my new Windows 10 laptop I initially had the same experience but then after a couple of days I created a file named "bar.bash" and was surprised to get prompted for what type of app to open it with. bash.exe was listed so I selected that, clicked the "always open with" again and that was fine but then when I had to open it again later I found that the "always open with" hadn't stuck. So I repeated and could not get Windows to remember to open that ".bash" extension file bar.bash with "bash.exe"
So I went back and double clicked on the original "foo.bash" and it opened with bash.exe. I tried changing it's "open with" to Notepad to see if that would stick and it didn't AND then I found I could no longer get bash.exe to stick either.
So now every time I double-click on a file with a ".bash" extension I have to click on bash.exe to open it. I have tried associating the extension with the app from the file properties, from the Settings menu, and everywhere else that any web page I can find tells me will work and none of them work - I 100% CANNOT get Windows 10 to remember to open ".bash" files with "bash.exe".
I also followed the steps at https://www.winhelponline.com/blog/remove-file-association-windows/ to delete the references to a ".bash" extension from the registry and that changed the popup prompt for which app to open the file with but after once again selecting bash.exe and "always open with", I was back once again to having to repeat the process every time I open the file.
Does anyone have any real ideas on how to do this? I assume it'll involve some arcane procedure to edit registry entries or something else that I REALLY don't want to be messing with but I've exhausted all of the "normal" ways that this should work from a user perspective.
Eureka! In a flash of inspiration I restarted Windows in Safe Mode (a chore in itself these days - see https://www.digitalcitizen.life/4-ways-boot-safe-mode-windows-10) and then right-clicked on foo.bash, searched for bash.exe again, selected it and now after rebooting back out of safe mode the association with "bash.exe" is still in place for all my ".bash" files.
So the trick is - go into safe mode to permanently associate the file suffix with the app.
I didnt change any file paths and everything was working fine. I made one quick change saved it ok, did another change and I went to save it and got the following error. How can I solve this. It will save other files ok
Unable to save
D:\xampp\htdocs\websites\dev.liverpool\style\main.scss
Error:
MoveFileEx(D:\xampp\htdocs\websites\dev.liverpool\style\.sublae1.tmp, D:\xampp\htdocs\websites\dev.liverpoolzstylezmain.scss) failed,
Access is denied.
seems it's because Windows or another program is blocking the file. Sublime text uses a temporal file instead of editing the file directly, and when you save the file uses a API command to move this edited file to the original, so this command has restrictions when one file is locked and Sublime shows this alert.
Maybe this setting {"atomic_save": false} will work for you.
Go to the path where you installed sublime text 2 and...
Right click on the sublime_text 2.exe file.
Go to its properties.
Go to compatibility section under this.
Set its privilege level to "Run this program as an administrator".
Now change settings for all users and there also check the field "Run this program as an administrator".
Apply the changes.
I just solved the same issue on Sublime Text 3 beta, Stable Channel Build 3065 by doing the following under Windows 7:
Navigate to the Sublime Text 3 executable file, wherever you have it installed.
Right-click it and select properties.
Click on the tab marked "Security"
About half way down the tab, on the right hand side, under the list of group and user names is this little button:
Click it.
If your machine is setup the way I suspect it is (otherwise you probably would not be having this issue), you should be prompted for your administrator account credentials. Enter them.
Now, select the Users group in the list, then take a look in the box at the bottom labeled 'Permissions for Users'. Put a check mark in the 'Allow' column for the 'Write' item.
Click 'Apply'
Click 'OK'
You should be set. What this does is it essentially gives Sublime the ability to write files while running with regular user privileges, no administrator level access required. Upon taking a better look at your error, what is happening is Sublime Text is creating a temp file for editing, rather than editing to file itself, then attempting to overwrite the original file with the temp on save. The problem is that the program is not being run by a user with sufficient privileges to perform the overwrite, hence the failure with an 'Access denied' message.
A simple and effective solution: Right-click on the file you want to save, in my case it is index.html, go to the properties and uncheck read-only.
The Sublime text will start working fine.
I have come across this error quite many times and by un-checking read-only file attribute of index.html, I am able to get rid of it
I found out more ways to fix this:
Close and reopen the Sublime Text windows or
Open the file with Np++, add a space, save, quit, then you're prompted by ST to reload the file, click yes, and it works again... or
Open the FTP console to see if there's a transaction in progress - then cancel it
In my case the SFTP plugin seems to be causing this problem, as when the FTP connection is timed out, the file which is waiting to be uploaded is being used, and you try to overwrite it.
This happens because you're using ScoutApp or Compass, they block your SCSS files because they are checking for changes as you specified for a directory for those files.
I suggest you reading this:
http://aspirecode.com/how-to-add-sass-support-in-sublime-text/
Good luck!
On mac using a remote volume sometimes I experience this. The solution is to remove the temp file then save again and all fixed.
IE: if you are working on test.html then the temp file would be ._test.html
Remove ._test.html then save again.
For Mac-
Try changing the destination from 'Macintosh HD' to 'Documents' or any other folder.
Worked for me.
The plugin of Superlime solved this problem. It tries to save the file as root in SublimeText.
Reference Link: https://github.com/azubr/Superlime
Try switching your SublimeText process priority to higher level in process manager (it has to have higher priority than your scss compiling app, if you're using one).
It seems to have worked for me.
if it's not working after doing all suggestions, reinstall the program
On Mac I saved the file in Home directory and it gave me this alert, later when I re saved the file again this time in Document directory the file is working now. Using SublimeText 3.
I found this occurred when the folders are read-only. Right-click on the folders where your site is contained and see if read-only is selected in the properties.
Just open it as an administrator.
Because I want to edit anything and write as admin all the time, I set this program to always open as an administrator using "Configure Applications to Always Run as an Administrator".
Just got your file folder properties which you want to save and deselect to read only attribute.
This is probably bordering off-topic-ness here, but not a lot of people on SuperUser use GVim, as opposed to here, so I'm leaving it here.
The problem is simple - I'm using GVim 7.3. from vim.org, downloaded it in the form of archived binaries (the two archive files) like always and replaced the older version. However, I can't get Windows to recognize it and to associate a file extension to it.
From windows explorer go to, let's say, .py file, Open with ... / Browse / gvim.exe in its directory and ... nothing. Like it never happened.
Does anyone have any idea what could be causing this behaviour? It's mighty annoying to have to open every file from within Vim manually.
I think the default installer ("self-installing executable") from vim.org lets you register shell associations; this means you get an entry "open with vim" in every context menu from the explorer. Did you not use this file?
I'm looking at this page and I'm thinking about this download.
This doesn't answer your question, but it's a different way to edit with gvim from the context menu.
Create a .reg file with the contents below (adjusting your path to gvim.exe) and execute it. Then whenever you right-click on a file in explorer you will have an "Open with GVIM" option.
REGEDIT4
[HKEY_CLASSES_ROOT\Unknown\shell]
#="Open with GVIM"
[HKEY_CURRENT_USER\SOFTWARE\Classes\*\shell]
[HKEY_CURRENT_USER\SOFTWARE\Classes\*\shell\Open with &GVim]
#="Open with GVIM"
[HKEY_CURRENT_USER\SOFTWARE\Classes\*\shell\Open with &GVim\command]
#="C:\\Vim\\gvim.exe \"%1\""
I gave up trying all kinds of tricks through the registry, but this solution works for me just fine. I might add, I'm having the same issue on Windows 7. Since Windows seems to be able to do the association with vim.exe just fine, and this is apparently tied to the file name, I moved vim.exe off as say vim.ex$ and made a copy of gvim.exe to vim.exe. Cheap and easy way around this goofy problem, and I can't say I ever use vim.exe on purpose.
What shortcuts do you use for file navigation in Gedit? Does anyone use the file browser?
I thought that these shortcuts would exist, but I can't find anything about them:
switch focus to/from the file browser.
disclose folder contents. (Most applications use up/down arrows for moving up and down, and the right/left arrows to open/disclose the folders.)
Do these exist?
Thanks,
Loren
I'm going to assume at this point that no one knows of these. (The only semi-useful shortcut I have found is F9, which simply shows/hides the file browser.)
Even the official shortcut list doesn't show anything regarding these two features:
http://live.gnome.org/Gedit/KeyboardShortcuts
For now, I'll submit this as a bug. Please let me know if this changes, so I can inform the dev team.
Loren
The shortcuts for the embedded file browser are pretty much the same as the file manager ones:
Enter - open directory
Backspace - go back
Alt+Up - go up one level
Up and Down arrows - navigate directory contents
As to how to switch focus to/from the file browser, I have added an answer here.
I have PHP for FastCGI installed on Windows 7 through the Web Platform Installer. I need to edit php.ini to enable logging, but I'm not able to overwrite the existing file, apparently because something has it open and/or locked.
Stopping the server in IIS Manager doesn't help; stopping the Windows Process Activation Service and the World Wide Web Publishing Service doesn't help. phpinfo() confirms that I'm working with the correct file (C:\Program Files (x86)\PHP\php.ini). It's not marked as read only and I do have permissions for it. I'm out of ideas.
I had this problem and managed to work around it. You need to be running the editor (notepad or whatever) as an admin.
In Window Vista / Window 7, right click and choose "Run as Administrator".
Then open php.ini and edit it...
Another option is to copy the text of the file into a new file in a different location, make your changes, save the file as 'php.ini'. Then copy the new file across overwriting the old one. Explorer may handle the permissions differently.
I've had a similar problem, and I was working in windows 10 which doesn't use "run as administrator"
So this is what I did:
right click the problem file and go to properties
go to tab security
click edit, which should have a shield
select in names of groups: Users(computer specifics\Users)
in the square under it you can allow editing of the file
This causes it to allow you to edit the file for users and not run into the problem anymore. This also removes the problem in the future for this file so you can always edit it again by just opening the file in text editor.
Please note I am Dutch and that certain names are translated incorrectly.
You could use the Find Handle feature of Process Explorer (direct EXE download link), from Sysinternals (a part of Microsoft now), to find out what exactly is locking the file.
I'm sorry I can't help with your exact question, but hope that helps!
In Windows 7, right click Notepad and choose "Run as Administrator". Make sure you do not use Notepad++ as your editor. It accesses this file and therefore tells you there's is an error.
The default notepad will work fine with these instructions.
Depending on what are you trying to write to the file, you can write to an '.htaccess' file on the root of the site instead. I can provide a more specific example if you would like.
You can also use Unlocker to figure this out. A pain, but the utility is really handy anyway so it won't hurt to have it around.
1) Open CMD with administrator mostly like this.
2) Then go to "C:\Program Files\php-8.1.7" like this.
3) then paste "cd C:\Program Files\php-8.1.7" and press Enter and type
php.ini like this.
4) It will automatically open the file in a text editor or suggest to
open any editor like notepad , notepad++,vs code etc.
5) edit as you wish and save it like (ctrl + s) .Here I adding MongoDB
extension like this .And that's it.
By the way the question was asked 12 years ago but we still facing the problem
Try this:
Stop the webserver
Change the file
Start the webserver
If that doesn't work, then you are probably changing the wrong file. It's possible that the original file is elsewhere and when the server starts it copies it to C:\Program Files (x86)\PHP\php.ini. phpinfo() might be pointing to the file that is overwritten every time...