New answers tagged gedit
You can insert a literal Tab character in gedit by using the GNOME Unicode input mode: Ctrl + Shift + U and then enter 9 followed by Enter. The horizontal tab character is Unicode code point U+0009. This will insert a tab regardless of your preferences to expand tabs or not.
You can create shortcuts to quickly change this setting: gsettings set org.gnome.gedit.preferences.editor insert-spaces false
Install a plugin for gedit Clone the repository git://git.gitano.org.uk/personal/liw/makefiletab3.git mkdir -p ~/src cd src git clone git://git.gitano.org.uk/personal/liw/makefiletab3.git Create the plugin folder for gedit mkdir -p ~/.local/share/gedit/plugins Create a symbolic link ln -s ~/src/makefiletab3 ~/.local/share/gedit/plugins/makefiletab3 ...
Might you have your Python virtual environment messing up the plugins as I had? I got plugins like codecomment working by hiding my PYTHONPATH and python virtual environment before launching Gedit. Since I still want to use my venv I have an executable script 'gedit' in my path with #!/bin/bash PYTHONPATH= ...
GEdit uses GtkSourceView for its syntax highlighting. Language File for IOS based devices. Language File for PIX/ASA based devices.
After some documentation search I was able find solution so I am gonna answer my question here. Open Gedit and go to "Tools" >> "Manage External Tools" and create new tool. Add following command just like below: echo -n $GEDIT_CURRENT_DOCUMENT_URI | xclip -sel clip;exit; Close it and then restart Gedit(just for confirmation). Open any document and then ...
The make command fails in my Ubuntu Vivid. I suspect that the libraries are too new for Gedit 3.16. Maybe you have luck with Trusty. Download the latest 3.6 version from here cd; wget http://ftp.gnome.org/pub/GNOME/sources/gedit/3.6/gedit-3.6.2.tar.xz Install the development libraries sudo apt-get build-dep gedit Extract the archive tar xf ...
If X10 files are not highlighted by default you can activate Snippets plugin. I assume you have set the .lang file under /usr/share/gtksourceview-3.0/language-specs. From plugin you can activate x10 highlightniing by shortcuts or snippet name followed by Tab key. I am not sure what Drop target option is for, nevertheless there is no way make it auto-detect ...
There is more than one possibility Change the language spec for CSS GTK3 sudo nano /usr/share/gtksourceview-3.0/language-specs/css.lang GTK2 sudo nano /usr/share/gtksourceview-2.0/language-specs/css.lang and replace the line <property name="globs">*.css;*.CSSL;</property> with <property ...
To edit configuration files, I would always use in your place a text-based editor: sudo nano /etc/default/grub
Script to copy the path of a file, opened in gedit With the gedit window in front, the small script below derives the path from the (gedit) window's name, and copies it to the clipboard. The script has two options: Only copy the path to the file's directory, running the script with the option -path or Copy the path including the file name, running the ...
Those are just backups of your original files that gedit creates before saving changes to your edited documents. How to prevent this ? In gedit preferences you need to disable Create a backup copy of file before saving, and if you want to automatic save your edits automatically set a timer with the option enable Autosave files every X minutes. That way ...
The problem is pretty simple, actually. You can get to know it by viewing the properties of that file. It's a backup file for the text, a.txt for example. the ~a.txt stores the last save (probably) of the file (a.txt). You can delete the backup file (~a.txt) if you want to. For some small files this is unnecessary.
Please remove #application/octet-stream=gedit.desktop; in your ./.local/share/applications/mimeapps.list. That's works for me.
What are you using to schedule? If it's cron-based, it likely doesn't have a DISPLAY variable set, so it doesn't know where to render the window. I'd recommend changing the command to include the DISPLAY, assuming it's the default :0: DISPLAY=:0 /usr/bin/gedit /path/to/file To debug cron issues, you can emulate a cron-like environment in a terminal: ...
Top 50 recent answers are included