This help page is a how-to guide. It details processes or procedures of some aspect(s) of Wikipedia's norms and practices. It is not one of Wikipedia's policies or guidelines, as it has not been thoroughly vetted by the community. |
Parts of this help page (those related to section) need to be updated. In particular: several of these add-ons are incompatible with recent (post-Quantum) versions of Firefox. Please update this help page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. (February 2019) |
This help page needs to be updated. Please update this help page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. |
vim
command within that X terminal, or generally your preferred editor. Assume that the filename of this script is wiki.edit.vim
, and that you put the script in the directory /home_dir/bin/
so that the path of the script would be/home_dir/bin/wiki.edit.vim
Put the above path in the Preferences box (instead of /usr/bin/gvim
) of It's All Text. It should work. Note that /home_dir/
is the complete path to your home directory from the root (/
) directory; don't use ~/
(tilde) instead of /home_dir/
; it won't work.The listing of the script wiki.edit.vim
is given below:$chmod +x wiki.edit.vim
LYGlobalDefs.h
:<BR>
tags): Advanced text editors, like vi or VIM, do typically show cursor position within a line in their status areas, and thus allow to gauge line length when the cursor is at the end of a line.date=26 February 2011
can be replaced with date=2011-02-26
— Users with their own date preferences should then see dates in their favoured format when logged in;&#xXX;
format, which in that form are sent to text editors and then back.ö
), and these add to the 1023-character line limit.OpenSSL
.utf-8
, as this is also the default charset used by Wikipedia. The display character set can be different, such as cp850
, but editable text will always be in utf-8
.lynx.cfg
is the config file for Lynx; the global config file in Windows is always located in the same folder as the Lynx executable, wherever it has been installed to. A typical location is C:Program FilesLynx
. If Lynx is installed in that folder, then Windows Vista and newer usually require administrator access to edit the file (via User Account Control).lynx.rc
is a per-user Lynx User Defaults File saved from the Options page. Settings in it take priority over the global config file. In Windows Vista, the per-user User Defaults file can be in C:UsersUsernameAppDataLocaltemplynx.rc
. If the file is in the temp
directory, care is advised when using automated cleanup tools, such as Disk Cleanup.lynx.cfg
is extensive; very often, almost all options are placed into it, along with explanatory comments for each option. If it's not so, there's an official online version at lynx.isc.org/lynx2.8.7/lynx2-8-7/lynx.cfg — Keep in mind that if your Lynx version is different, change the numbers in the URL accordingly, as some options may be version-specific.#
and its default setting is on; To use an option, delete the hash character before it. It may occasionally happen that the config file does not contain a specific option, but it can be added by the user.lynx.cfg
and are usually not specified in the Options page. Before making changes, make a backup copy of the file, renaming it to lynx.cfg.old
, for example.COLLAPSE_BR_TAGS:
option should be set to FALSE
, as in the example below:<BR>
tag, especially in locations where conventional paragraph breaks are not allowed.dwb:keys
page under the open_editor
option, and the editor is defined on the dwb:settings
page.editor
and open_editor
Lua modules. User configuration is done by editing a userconf.lua
file and key bindings are changed with the add_binds
and remove_binds
functions.:open-editor
command. Settings can be changed using the :set
command, with the editor defined in the editor.command
section. The key-binding can be changed by using config.bind()
in config.py
or with the :bind
command.;e
or by pressing Ctrl+t on a form field while in Input Mode. The editor is defined by changing the :set editor-command
setting and changing the key mapping is done by using :map
to change mappings. Note that there are various key mapping modes for mapping commands.vimprobablerc
file. To change the key binding, use the map
command on the openeditor
function. To define a different editor, use the handler
command to change the vimprobableedit
URI schema.o
to open the Options screen and change the Editor field. If the Editor field is left blank, w3m will use the $EDITOR
environment variable.__init__.py
found in the ~/.webmacs/init
directory and changing the external-editor-command
variable. The define_key()
and undefine_key()
functions define and undefine a command to a keymap respectively.longlines.el
is now part of the default GNU Emacs distribution. The following information is retained for reference.longlines.el
is now part of GNU Emacs). Installation instructions for longlines.el
.Tools → Highlighting → Markup → Mediawiki
.It recognizes everything in default markup:<nowiki>...</nowiki>
sectionsSettings → Configure Kate → Fonts & Colors → Highlighting Text Styles
and select 'Markup/MediaWiki' in the drop-down menu.Settings → Configure Kate → Fonts & Colors → Highlighting Text Styles → Highlight: → Import button
./Library/Application Support/SubEthaEdit/Modes/
(system-wide) or ~/Library/Application Support/SubEthaEdit/Modes/
(user-specific). You may need to create the final two directories by hand. The mode will be automatically selected for files with a .wiki or .Wikipedia extension.vimrc
):input
and select
elements, ↵ Enter saves the text. For textarea
elements such as for editing a page, Ctrl+↵ Enter will save the text. In all cases, :w
will also save the written text and Esc or :q
will leave the editor without saving changes.open -a TextEdit file.txt
open -e file.txt
open -t file.txt
open file.txt
. You can use the 'file' command to reveal what the operating system thinks the file type is: file file.txt
. So, for example, if you renamed 'file.txt' to just 'textfile' then open textfile
would still open it in the default text-file editing application, as long as file textfile
still thought that 'textfile' was actually a text file.open
can be found by running~/.profile
:Command Line Utilities
, allowed you to do:open -t README.txt
, but maybe I'm just suffering from inertia.edit
is a binary executable file (from the TextWrangler kit), not just an alias or symlink.