| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This plugin overrides the standard `:bdelete` and `:bwipeout` commands
with capitalized versions with the following advantages:
+ Close and remove the buffer;
+ Show another file in that window;
+ Show an empty file if you've got no other files open;
+ Do not leave useless [no file] buffers if you decide to edit another file in that window;
+ Work even if a file's open in multiple windows;
+ Work okay with various buffer explorers and tabbars.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Vim will try to source a `.local.vim` file in the cwd. This is useful
when you want to have some project specific configuration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The wrapper function introduced allows for more focus on the spell
checking errors:
+ Errors are red and underlined;
+ Other possible syntactical mistakes are yellow and underlined;
+ any other text-related highlight group (`Normal` included) turns gray.
Note: this is done with a sequence of `highlight` commands that override
the current colorscheme. A simplier way would be to turn off syntax
detection overall (`set syntax=off`) and just change the `Normal`
highlight group. This can cause problems when one wants to limit syntax
checking to same part of the text (comments in a programming language),
since this is not possible with syntax disabled.
Bug: `spell` option is always activated per buffer, while `highlight`
commands are global. This can cause problems when one:
1) activates spell checking in one buffer
2) switches to another buffer
3) deactivates spell checking
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Now it is possible to launch the tor browser from anywhere in a shell.
It also enables remote controll by default, so that it is possible to
open new tabs from scripts/commandline/other programs.
`$TOR_BROWSER_DIR` is the env variable pointing to the directory in
which Tor Browser is installed.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The script (bound to `AltGr+Shift+t`) uses rofi to allow the user to:
1) open a new terminal window without Tmux running;
2) create a new temporary Tmux session;
3) Attach to an existing Tmux session.
The script needs to be invoked from a terminal, possibly using a command
like `xterm -e /path/to/rofi_tmux_sessions.sh`.
The binding `AltGr+t` will simply attach to the `HUB:main` session.
|
|
|
|
|
|
|
|
|
|
| |
The function `tmux-sessions` previously called `t` now takes a list of
sessions to start in the background. Controls are still performed to
ensure that the corresponding script for the session is trusted by the
user.
By default the command attaches to the last valid session provided. This
behaviour can be avoided with the flag `-d|--detach`.
|
| |
|
|
|
|
| |
Also removes URxvt daemon from the starting script.
|
| |
|
|
|
|
|
| |
This causes problems when the my definition of paragraph is not the same
of Vim's.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
After a chat on #vim we agreed that `if get(g:,'loaded_<plugin>',0)` is
the best way to test if a plugin is loaded. It also allows to manually
disable a plugin using `let g:loaded_<plugin> = 0` in vimrc.
Bear in mind that, despite the fact that initializing said variable is
the canonical way of starting a plugin, this is not forced. Plugin
authors might be unaware of this and don't provide such a variable.
|
|
|
|
| |
This needs the function `fugitive#head()` from TPope Fugitive plugin.
|
| |
|
|
|
|
|
| |
Basically activates mouse support and unbinds all unnecessary keys. Bear
in mind that this disables some XTerm mouse functionalities.
|
| |
|
|
|
|
|
|
| |
Statusline and status related features are hidden, and some highlight
groups are changed. Also integrates with Tmux Zoom feature, so that they
can be toggled together.
|
|
|
|
|
| |
This possibly avoids conflicts with autoload files declared inside
scripts.
|
| |
|
| |
|
| |
|
|
|
|
| |
Sets some options to be used with `gf` and the `include-search` feature.
|
|\ |
|
| | |
|
|/ |
|
|
|
|
|
| |
Keep TPope's Pathogen around and fall back to it in case the current Vim
version does not come with its own runtimepath manager.
|
| |
|
|
|
|
| |
Also search patterns are not included in the `viminfo` file anymore.
|
|
|
|
|
|
|
|
|
|
|
| |
A bash function `t()` has been added. This takes a session as an
argument (or tries its best to guess it) and start the corresponding
tmux script (if any exists).
If a session is already running, simply attach to it.
A digest protection system has been implemented to ask the user for
approval when running a script for the first time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It should work fine with or without TPope's `vim-obsession` plugin. The
advantage of the plugin is automatic session updates whenever the layout
changes.
Sessions are stored in $VIM_SESSIONS (set to
`~/.local/share/vim/sessions`) and are named after the name of the
current working directory (which is usually the project name).
A bash function `vims()` is also provided: if a session is currently
been tracked for the current directory, it is loaded, otherwise a new
one is created.
A statusline flag has been added to notify the user that a session is
currently been tracked. The flag changes if the session is tracked with
the `vim-obsession` plugin or simply with Vim `mksession`
functionalities.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Set some options regarding backup, swap, undo and viminfo files. Now Vim
tries its best to store this files out of the way, under a common
directory (namely `~/.local/share/vim`).
Restored the use of backups and undo files. `viminfo` variable
fine-tuned.
Also preventing the `root` user from using any of these functionalities
to avoid storing sensible information in these files.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This solves a problem that arises whenever you reload a colorscheme. In
fact most colorschemes clear all highlight groups before defining their
own (regardless of what they actually use). This inevitably overrides
any custom highlight made in the vim configuration file (if not sourced
again).
This adds all highlight group customisations to an autogroup hooked to
the `ColorScheme` event (to be executed after any `colorscheme` call).
Note that this group needs to be defined before the first `colorscheme`
call in the config file for the effects to be immediately visible.
|