~kklimonda/ubuntu/lucid/rxvt-unicode/lp-514821

Committer: Bazaar Package Importer
Author(s): Decklin Foster
Date: 2006-09-01 14:44:58 UTC
mfrom: (1.1.8 upstream) (3.1.1 etch)
Revision ID: james.westby@ubuntu.com-20060901144458-98hrz8zg01w8a3vy

Tags: 7.9-2

http://bugs.debian.org/385481

* Edit the comments in the app-defaults file, and disable all settings by
  default. If font autoselection fails, I would prefer to open a new bug
  specifically for that. (Closes: #385481)
* Reorganize and edit README.Debian, pushing as much as possible into FAQ
  format (with resource setting issues first).

files added:
debian/patches/select-quoted.patch

src/perl/kuake

files removed:
debian/patches/faq-section.patch

debian/patches/grammar.patch

debian/patches/make-doc.patch

debian/patches/man-title.patch

src/rxvtlib.h

files modified:
Changes

MANIFEST

README.FAQ

README.configure

debian/README.Debian

debian/app-defaults

debian/changelog

debian/control

debian/patches/app-defaults.patch

debian/patches/generate-docs.patch

debian/patches/old-debian-nonsense.patch

debian/patches/series

debian/urxvtcd

doc/Makefile.in

doc/rxvt-unicode.spec

doc/rxvt.1.html

doc/rxvt.1.man.in

doc/rxvt.1.pod

doc/rxvt.1.txt

doc/rxvt.7.html

doc/rxvt.7.man.in

doc/rxvt.7.pod

doc/rxvt.7.txt

doc/rxvtc.1.html

doc/rxvtc.1.man.in

doc/rxvtc.1.pod

doc/rxvtc.1.txt

doc/rxvtd.1.html

doc/rxvtd.1.man.in

doc/rxvtd.1.txt

doc/rxvtperl.3.html

doc/rxvtperl.3.man.in

doc/rxvtperl.3.txt

src/Makefile.in

src/callback.h

src/command.C

src/fdpass.C

src/feature.h

src/hookinc.h

src/init.C

src/iom.h

src/main.C

src/perl/automove-background

src/perl/mark-urls

src/perl/searchable-scrollback

src/perl/selection

src/perl/selection-pastebin

src/perl/selection-popup

src/rxvt.h

src/rxvtfont.C

src/rxvtlib.h.in

src/rxvtperl.xs

src/rxvttoolkit.C

src/rxvttoolkit.h

src/rxvtutil.h

src/screen.C

src/urxvt.pm

src/version.h

Show diffs side-by-side

added added

removed removed

doc/rxvt.7.pod

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,

146

147

When you C<--enable-everything> (which I<is> unfair, as this involves xft

148

and full locale/XIM support which are quite bloaty inside libX11 and my

149

libc), the two diverge, but not unreasnobaly so.

149

libc), the two diverge, but not unreasonably so.

150

151

text data bss drs rss filename

152

163431 2152 24 20123 2060 rxvt --enable-everything

243

244

This requires XFT support, and the support of your X-server. If that

245

doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't

246

there yet, no matter what they claim. Rxvt-Unicode contains the neccessary

246

there yet, no matter what they claim. Rxvt-Unicode contains the necessary

247

bugfixes and workarounds for Xft and Xlib to make it work, but that

248

doesn't mean that your WM has the required kludges in place.

249

270

ask for the character bounding box, which unfortunately is wrong in these

271

cases).

272

273

It's not clear (to me at least), wether this is a bug in Xft, freetype,

273

It's not clear (to me at least), whether this is a bug in Xft, freetype,

274

or the respective font. If you encounter this problem you might try using

275

the C<-lsp> option to give the font more height. If that doesn't work, you

276

might be forced to use a different font.

304

Yes, using an escape sequence. Try something like this, which has the same

305

effect as using the C<-fn> switch, and takes effect immediately:

306

307

printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"

307

printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic"

308

309

This is useful if you e.g. work primarily with japanese (and prefer a

310

japanese font), but you have to switch to chinese temporarily, where

316

317

Many fonts have difficulties with italic characters and hinting. For

318

example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans

319

Mono> completely fails in it's italic face. A workaround might be to

319

Mono> completely fails in its italic face. A workaround might be to

320

enable freetype autohinting, i.e. like this:

321

322

URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true

332

=head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?

333

334

Rxvt-unicode will use whatever you specify as a font. If it needs to

335

fall back to it's default font search list it will prefer X11 core

335

fall back to its default font search list it will prefer X11 core

336

fonts, because they are small and fast, and then use Xft fonts. It has

337

antialiasing disabled for most of them, because the author thinks they

338

look best that way.

514

but when running a program that doesn't parse cursor movements or in some

515

cases during rlogin sessions, it fails to detect this properly.

516

517

You can permamently switch this feature off by disabling the C<readline>

517

You can permanently switch this feature off by disabling the C<readline>

518

extension:

519

520

URxvt.perl-ext-common: default,-readline

523

524

Some Debian GNUL/Linux users seem to have this problem, although no

525

specific details were reported so far. It is possible that this is caused

526

by the wrong C<TERM> setting, although the details of wether and how

526

by the wrong C<TERM> setting, although the details of whether and how

527

this can happen are unknown, as C<TERM=rxvt> should offer a compatible

528

keymap. See the answer to the previous question, and please report if that

529

helped.

559

=head3 What's with the strange Backspace/Delete key behaviour?

560

561

Assuming that the physical Backspace key corresponds to the

562

BackSpace keysym (not likely for Linux ... see the following

562

Backspace keysym (not likely for Linux ... see the following

563

question) there are two standard values that can be used for

564

Backspace: C<^H> and C<^?>.

565

696

write.

697

698

The selection stuff mainly makes the selection perl-error-message aware

699

and tells it to convert pelr error mssages into vi-commands to load the

699

and tells it to convert perl error messages into vi-commands to load the

700

relevant file and go tot he error line number.

701

702

URxvt.scrollstyle: plain

703

URxvt.secondaryScroll: true

704

705

As the documentation says: plain is the preferred scrollbar for the

706

author. The C<secondaryScroll> confgiures urxvt to scroll in full-screen

707

apps, like screen, so lines scorlled out of screen end up in urxvt's

706

author. The C<secondaryScroll> configures urxvt to scroll in full-screen

707

apps, like screen, so lines scrolled out of screen end up in urxvt's

708

scrollback buffer.

709

710

URxvt.background: #000000

765

urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true

766

767

I wrote rxvt-unicode to be able to specify fonts exactly. So don't be

768

overwhelmed. A special note: the C<9x15bold> mentioend above is actually

768

overwhelmed. A special note: the C<9x15bold> mentioned above is actually

769

the version from XFree-3.3, as XFree-4 replaced it by a totally different

770

font (different glyphs for C<;> and many other harmless characters),

771

while the second font is actually the C<9x15bold> from XFree4/XOrg. The

772

bold version has less chars than the medium version, so I use it for rare

773

characters, too. Whene ditign sources with vim, I use italic for comments

773

characters, too. When editing sources with vim, I use italic for comments

774

and other stuff, which looks quite good with Bitstream Vera anti-aliased.

775

776

Terminus is a quite bad font (many very wrong glyphs), but for most of my

831

URxvt.resource: value

832

833

If you want to use another form (there are lots of different ways of

834

specifying resources), make sure you understand wether and why it

834

specifying resources), make sure you understand whether and why it

835

works. If unsure, use the form above.

836

837

=head3 When I log-in to another system it tells me about missing terminfo data?

878

library (Fedora Core's bash is one example) and rely on a termcap entry

879

for C<rxvt-unicode>.

880

881

You could use rxvt's termcap entry with resonable results in many cases.

881

You could use rxvt's termcap entry with reasonable results in many cases.

882

You can also create a termcap entry by using terminfo's infocmp program

883

like this:

884

910

=head3 Why does C<ls> no longer have coloured output?

911

912

The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to

913

decide wether a terminal has colour, but uses it's own configuration

914

file. Needless to say, C<rxvt-unicode> is not in it's default file (among

913

decide whether a terminal has colour, but uses its own configuration

914

file. Needless to say, C<rxvt-unicode> is not in its default file (among

915

with most other terminals supporting colour). Either add:

916

917

TERM rxvt-unicode

962

The best thing is to fix your startup environment, as you will likely run

963

into other problems. If nothing works you can try this in your .profile.

964

965

printf '\e]701;%s\007' "$LC_CTYPE"

965

printf '\33]701;%s\007' "$LC_CTYPE"

966

967

If this doesn't work, then maybe you use a C<LC_CTYPE> specification not

968

supported on your systems. Some systems have a C<locale> command which

993

applications so everybody agrees on character properties such as width

994

and code number. This mechanism is the I<locale>. Applications not using

995

that info will have problems (for example, C<xterm> gets the width of

996

characters wrong as it uses it's own, locale-independent table under all

996

characters wrong as it uses its own, locale-independent table under all

997

locales).

998

999

Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All

1022

Yes, using an escape sequence. Try something like this, which sets

1023

rxvt-unicode's idea of C<LC_CTYPE>.

1024

1025

printf '\e]701;%s\007' ja_JP.SJIS

1025

printf '\33]701;%s\007' ja_JP.SJIS

1026

1027