re-run the command. Subsequent invocations of the script will re-use the
existing daemon.
-=head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
+=head3 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
The original rxvt and rxvt-unicode always export the variable "COLORTERM",
so you can check and see if that is set. Note that several programs, JED,
When you C<--enable-everything> (which I<is> unfair, as this involves xft
and full locale/XIM support which are quite bloaty inside libX11 and my
-libc), the two diverge, but not unreasnobaly so.
+libc), the two diverge, but not unreasonably so.
text data bss drs rss filename
163431 2152 24 20123 2060 rxvt --enable-everything
This requires XFT support, and the support of your X-server. If that
doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
-there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
+there yet, no matter what they claim. Rxvt-Unicode contains the necessary
bugfixes and workarounds for Xft and Xlib to make it work, but that
doesn't mean that your WM has the required kludges in place.
ask for the character bounding box, which unfortunately is wrong in these
cases).
-It's not clear (to me at least), wether this is a bug in Xft, freetype,
+It's not clear (to me at least), whether this is a bug in Xft, freetype,
or the respective font. If you encounter this problem you might try using
the C<-lsp> option to give the font more height. If that doesn't work, you
might be forced to use a different font.
but when running a program that doesn't parse cursor movements or in some
cases during rlogin sessions, it fails to detect this properly.
-You can permamently switch this feature off by disabling the C<readline>
+You can permanently switch this feature off by disabling the C<readline>
extension:
URxvt.perl-ext-common: default,-readline
Some Debian GNUL/Linux users seem to have this problem, although no
specific details were reported so far. It is possible that this is caused
-by the wrong C<TERM> setting, although the details of wether and how
+by the wrong C<TERM> setting, although the details of whether and how
this can happen are unknown, as C<TERM=rxvt> should offer a compatible
keymap. See the answer to the previous question, and please report if that
helped.
=head3 What's with the strange Backspace/Delete key behaviour?
Assuming that the physical Backspace key corresponds to the
-BackSpace keysym (not likely for Linux ... see the following
+Backspace keysym (not likely for Linux ... see the following
question) there are two standard values that can be used for
Backspace: C<^H> and C<^?>.
write.
The selection stuff mainly makes the selection perl-error-message aware
-and tells it to convert pelr error mssages into vi-commands to load the
+and tells it to convert perl error messages into vi-commands to load the
relevant file and go tot he error line number.
URxvt.scrollstyle: plain
URxvt.secondaryScroll: true
As the documentation says: plain is the preferred scrollbar for the
-author. The C<secondaryScroll> confgiures urxvt to scroll in full-screen
-apps, like screen, so lines scorlled out of screen end up in urxvt's
+author. The C<secondaryScroll> configures urxvt to scroll in full-screen
+apps, like screen, so lines scrolled out of screen end up in urxvt's
scrollback buffer.
URxvt.background: #000000
urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
-overwhelmed. A special note: the C<9x15bold> mentioend above is actually
+overwhelmed. A special note: the C<9x15bold> mentioned above is actually
the version from XFree-3.3, as XFree-4 replaced it by a totally different
font (different glyphs for C<;> and many other harmless characters),
while the second font is actually the C<9x15bold> from XFree4/XOrg. The
bold version has less chars than the medium version, so I use it for rare
-characters, too. Whene ditign sources with vim, I use italic for comments
+characters, too. When editing sources with vim, I use italic for comments
and other stuff, which looks quite good with Bitstream Vera anti-aliased.
Terminus is a quite bad font (many very wrong glyphs), but for most of my
URxvt.resource: value
If you want to use another form (there are lots of different ways of
-specifying resources), make sure you understand wether and why it
+specifying resources), make sure you understand whether and why it
works. If unsure, use the form above.
=head3 When I log-in to another system it tells me about missing terminfo data?
library (Fedora Core's bash is one example) and rely on a termcap entry
for C<rxvt-unicode>.
-You could use rxvt's termcap entry with resonable results in many cases.
+You could use rxvt's termcap entry with reasonable results in many cases.
You can also create a termcap entry by using terminfo's infocmp program
like this:
=head3 Why does C<ls> no longer have coloured output?
The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to
-decide wether a terminal has colour, but uses its own configuration
+decide whether a terminal has colour, but uses its own configuration
file. Needless to say, C<rxvt-unicode> is not in its default file (among
with most other terminals supporting colour). Either add:
=item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode.
When you want to use e.g. B<kinput2>, it must be set to
-C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input
+C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input
method servers are running with this command:
xprop -root XIM_SERVERS
You should build one binary with the default options. F<configure>
now enables most useful options, and the trend goes to making them
-runtime-switchable, too, so there is usually no drawback to enbaling them,
+runtime-switchable, too, so there is usually no drawback to enabling them,
except higher disk and possibly memory usage. The perl interpreter should
be enabled, as important functionality (menus, selection, likely more in
the future) depends on it.
Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined
in your compile environment, or an implementation that implements it,
-wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
+whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that
B<wchar_t> is represented as unicode.
-As you might have guessed, FreeBSD does neither define this symobl nor
+As you might have guessed, FreeBSD does neither define this symbol nor
does it support it. Instead, it uses its own internal representation of
B<wchar_t>. This is, of course, completely fine with respect to standards.
=head1 DESCRIPTION
-Everytime a terminal object gets created, extension scripts specified via
+Every time a terminal object gets created, extension scripts specified via
the C<perl> resource are loaded and associated with it.
Scripts are compiled in a 'use strict' and 'use utf8' environment, and
The index number (0, 1...) must not have any holes, and each regex must
contain at least one pair of capturing parentheses, which will be used for
-the match. For example, the followign adds a regex that matches everything
+the match. For example, the following adds a regex that matches everything
between two vertical bars:
URxvt.selection.pattern-0: \\|([^|]+)\\|
popup is being displayed.
It's sole argument is the popup menu, which can be modified. The selection
-is in C<$_>, which can be used to decide wether to add something or not.
+is in C<$_>, which can be used to decide whether to add something or not.
It should either return nothing or a string and a code reference. The
string will be used as button text and the code reference will be called
when the button gets activated and should transform C<$_>.
=item tabbed
This transforms the terminal into a tabbar with additional terminals, that
-is, it implements what is commonly refered to as "tabbed terminal". The topmost line
+is, it implements what is commonly referred to as "tabbed terminal". The topmost line
displays a "[NEW]" button, which, when clicked, will add a new tab, followed by one
button per tab.
This is useful if you need a single terminal thats not using any desktop
space most of the time but is quickly available at the press of a key.
-The accelerator key is grabbed regardless of any modifers, so this
+The accelerator key is grabbed regardless of any modifiers, so this
extension will actually grab a physical key just for this function.
If you want a quake-like animation, tell your window manager to do so
This is basically a very small extension that dynamically changes the
background pixmap offset to the window position, in effect creating the
same effect as pseudo transparency with a custom pixmap. No scaling is
-supported in this mode. Exmaple:
+supported in this mode. Example:
@@RXVT_NAME@@ -pixmap background.xpm -pe automove-background
The following subroutines can be declared in extension files, and will be
called whenever the relevant event happens.
-The first argument passed to them is an extension oject as described in
+The first argument passed to them is an extension object as described in
the in the C<Extension Objects> section.
B<All> of these hooks must return a boolean value. If any of the called
=item on_start $term
Called at the very end of initialisation of a new terminal, just before
-trying to map (display) the toplevel and returning to the mainloop.
+trying to map (display) the toplevel and returning to the main loop.
=item on_destroy $term
requested from the server. The selection text can be queried and changed
by calling C<< $term->selection >>.
-Returning a true value aborts selection grabbing. It will still be hilighted.
+Returning a true value aborts selection grabbing. It will still be highlighted.
=item on_sel_extend $term
Called whenever the user tries to extend the selection (e.g. with a double
click) and is either supposed to return false (normal operation), or
-should extend the selection itelf and return true to suppress the built-in
+should extend the selection itself and return true to suppress the built-in
processing. This can happen multiple times, as long as the callback
returns true, it will be called on every further click by the user and is
supposed to enlarge the selection more and more, if possible.
=item on_view_change $term, $offset
-Called whenever the view offset changes, i..e the user or program
+Called whenever the view offset changes, i.e. the user or program
scrolls. Offset C<0> means display the normal terminal, positive values
show this many lines of scrollback.
future.
Be careful not ever to trust (in a security sense) the data you receive,
-as its source can not easily be controleld (e-mail content, messages from
+as its source can not easily be controlled (e-mail content, messages from
other users on the same system etc.).
=item on_add_lines $term, $string
=item on_user_command $term, $string
-Called whenever the a user-configured event is being activated (e.g. via
+Called whenever a user-configured event is being activated (e.g. via
a C<perl:string> action bound to a key, see description of the B<keysym>
resource in the @@RXVT_NAME@@(1) manpage).
=item on_resize_all_windows $tern, $new_width, $new_height
-Called just after the new window size has been calculcated, but before
+Called just after the new window size has been calculated, but before
windows are actually being resized or hints are being set. If this hook
returns TRUE, setting of the window hints is being skipped.
=item on_focus_out $term
-Called wheneever the window loses keyboard focus, before rxvt-unicode does
+Called whenever the window loses keyboard focus, before rxvt-unicode does
focus out processing.
=item on_configure_notify $term, $event
=item @urxvt::TERM_INIT
-All coderefs in this array will be called as methods of the next newly
+All code references in this array will be called as methods of the next newly
created C<urxvt::term> object (during the C<on_init> phase). The array
-gets cleared before the codereferences that were in it are being executed,
-so coderefs can push themselves onto it again if they so desire.
+gets cleared before the code references that were in it are being executed,
+so references can push themselves onto it again if they so desire.
-This complements to the perl-eval commandline option, but gets executed
+This complements to the perl-eval command line option, but gets executed
first.
=item @urxvt::TERM_EXT
=item @terms = urxvt::termlist
Returns all urxvt::term objects that exist in this process, regardless of
-wether they are started, being destroyed etc., so be careful. Only term
+whether they are started, being destroyed etc., so be careful. Only term
objects that have perl extensions attached will be returned (because there
is no urxvt::term objet associated with others).
optionally change it. All option values are stored by name in the hash
C<%urxvt::OPTION>. Options not enabled in this binary are not in the hash.
-Here is a a likely non-exhaustive list of option names, please see the
+Here is a likely non-exhaustive list of option names, please see the
source file F</src/optinc.h> to see the actual list:
borderLess console cursorBlink cursorUnderline hold iconic insecure
Please note that resource strings will currently only be freed when the
terminal is destroyed, so changing options frequently will eat memory.
-Here is a a likely non-exhaustive list of resource names, not all of which
+Here is a likely non-exhaustive list of resource names, not all of which
are supported in every build, please see the source file F</src/rsinc.h>
to see the actual list:
=item $cursor_is_hidden = $term->hidden_cursor
-Returns wether the cursor is currently hidden or not.
+Returns whether the cursor is currently hidden or not.
=item $view_start = $term->view_start ([$newvalue])
=item $string = $term->special_decode $text
-Converts rxvt-unicodes text reprsentation into a perl string. See
+Converts rxvt-unicodes text representation into a perl string. See
C<< $term->ROW_t >> for details.
=item $success = $term->grab_button ($button, $modifiermask[, $window = $term->vt])
=item $success = $term->grab ($eventtime[, $sync])
Calls XGrabPointer and XGrabKeyboard in asynchronous (default) or
-synchronous (C<$sync> is true). Also remembers the grab timestampe.
+synchronous (C<$sync> is true). Also remembers the grab timestamp.
=item $term->allow_events_async
=item $iow = $iow->fd ($fd)
-Set the filedescriptor (not handle) to watch.
+Set the file descriptor (not handle) to watch.
=item $iow = $iow->events ($eventmask)
=item $iow = $iow->stop
-Stop watching for events on the given filehandle.
+Stop watching for events on the given file handle.
=back
=item $pw = $timer->start ($pid)
-Tells the wqtcher to start watching for process C<$pid>.
+Tells the watcher to start watching for process C<$pid>.
=item $pw = $pw->stop
=item >=10 - all called hooks
-=item >=11 - hook reutrn values
+=item >=11 - hook return values
=back
projects / dana / urxvt.git / commitdiff