You could write, or hunt up, a "Character Map" like in start->programs->accessories->systemtools->. Mine has U-007C: Vertical Line. An x web browser on a wikipedia page for unicode would give you a bazillion glyphs. I get vi/vim has some octal/hex input feature somewhere. http://vim.wikia.com/wiki/Entering_special_characters
I am a big fan of the "set -o vi" mode of ksh/bash command line editing, not the bash thing so like DOS. In fact, I never leave $HOME except insice () so my commands when recalled all work. With X and command recall and vi command editing, you do not need the path shortening keystoke savings of cd. I usually make $HISTSIZE big, something like 32767 seems to all it can handle, move the $HISTORYFILE somewhere permanent, save it periodically in an archive, and write scripts to search it and display it so I can recall keystrokes for years. For long lines, you have to go exc-v-enter into vi every time, as they recall truncated, but they recall. Now, if you have or install vim, you export EDITOR=vim and poof! vi is not hard wired. I use vix, a script that, before running vi, echos out linefeeds to save the screen in the scrool buffer, and after running vi, returns 0 always, as when command line editing, return not zero from vi (any beep for trivial error) and the vi file is discarded.
Code:
$ cat mysrc/vix
#!/usr/bin/ksh
(
stty -a | sed '
s/^/ /
t a
:a
s/.* rows = \([1-9][0-9]*\).*/\1/
t
d
' | read zr
# echo $zr >&2
if [ "$zr" = "" ]
then
zr=25
fi
while [ "$zr" != -1 ]
do
zr=$(( $zr - 1 ))
echo >/dev/tty
done
vi "$@"
exit 0
)
I think the parens are for one aix or hpux system where the ksh, upon detecting the call of a ksh script, ran scripts in the login ksh, as if sourced. My environment kept getting trashed. My vix did not seem to work well on later x and vim, but it helps. I keep my xterms with huge scroll buffers running for weeks under vnc, where you can disconnect and reconnect to your remote per-host X desktops. Keystrokes are so valuable.
They really did not map 0174 onto the keyboard anywhere? How anti-ascii ! Rule Britannia!
Last edited by DGPickett; 02-28-2013 at 05:55 PM..
ok, I am having a seriouse problem!
I can not wite in my landguidge, I live in sweden but I seem to have an american keyboard layout so I cant write some letters and all the key commands are all messed up. Does anyone know where I can find a swedisch keyboard layout? (3 Replies)
Hi,
How do i go about changing the keyboard layout to the UK layout.
currently the @ symbol on the keyboard appears as a " sybol on the monitor.
Many Thanks in advance
Kam (1 Reply)
Hi
I have Fedora linux with XFCE desktop. I want to use Indic lanquage in that. I have installed unicode devnagri fonts. But I am not able to change my default keyboard layout. How can I change default keyboard layout in XFCE or through command line.
Thanks
NeeleshG (0 Replies)
After Solaris 10 installation I was unable to change keyboard using known commands
kbd -s and eeprom keyboard layoit.
Also modifinig /boot/solaris/bootenv.rc did not helped.
And is possible to replace Solaris keymap with ubuntu keymap because my keyboard
work perfectly under Ubuntu and... (7 Replies)
Hi to everyone
Once again I tried to modify my keyboard , because I am crazy keyborad can not be changed using
kbd-s
eeprom
also I tried to modify /boot/solaris/bootenv.rc
but I tried opensolaris and my keyboard works perfectly
So my question is
Can I transfer settings from... (14 Replies)
I would like to make a new keyboard layout that moves the modifier keys around. The problem is that this needs to be an xkb layout, because I still need to be able to switch to the Qwerty layout and the layout of my native language. Is there a way to write an xkb layout that works on the keycodes... (2 Replies)
Discussion started by: dotancohen
2 Replies
LEARN ABOUT DEBIAN
vim-registry
vim-registry(5) vim addons vim-registry(5)NAME
vim-registry - syntax for vim-addons registry files
SYNOPSIS
PACKAGE-NAME.yaml
DESCRIPTION
A registry file is a multi-document YAML file (i.e. it can be composed by several different YAML documents separated by "---" lines). Each
YAML document represents a registry entry, that is the information describing a single addon.
Ideally, the registry directory contains one file per package shipping addons; with a filename obeying to the convention PACKAGE-NAME.yaml.
Hence a single package can contribute to the registry with multiple entries described in a single YAML file.
For example, the "vim-scripts" package should ship a single /usr/share/vim/registry/vim-scripts.yaml file, containing one YAML document per
shipped addon. The first lines of such file can look like the following:
addon: alternate
description: "alternate pairing files (e.g. .c/.h) with short ex-commands"
basedir: /usr/share/vim-scripts/
disabledby: "let loaded_alternateFile = 1"
files:
- plugin/a.vim
- doc/alternate.txt
---
addon: whatdomain
description: "query the meaning of a Top Level Domain"
basedir: /usr/share/vim-scripts/
disabledby: "let loaded_whatdomain = 1"
files:
- plugin/whatdomain.vim
---
Each registry entry may contain the following fields, to be typeset according to the YAML specification:
addon (Required)
Name of the addon.
description (Required)
Human understandable textual description of the addon.
files (Required)
List of the files which compose the addon and are required to be present in a component of the Vim runtime path for the addon to be
enabled. Each file is specified relative to a component of the Vim runtime path.
basedir (Optional)
Directory where the files shipped by the addon (i.e., where the symlinks of the user/sysadm should point to) reside on the filesys-
tem. Default is /usr/share/vim/addons.
disabledby (Optional)
Vim script command that can be used (usually by adding it to ~/.vimrc) to prevent the addon from being used even when it is
installed. The intended usage of this field is to "blacklist" an undesired addon whose files are available, and hence automatically
loaded by Vim, in a component of the Vim runtime path.
AUTHOR
James Vega <jamessan@debian.org>
SEE ALSO vim-addons(1), YAML specification <http://www.yaml.org/>
COPYRIGHT
Copyright (C) 2010 James Vega
This program is free software, you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as pub-
lished by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
Debian Project January 2010 vim-registry(5)
02-28-2013
