… | |
… | |
150 | |
150 | |
151 | The mouse pointer background colour; resource B<pointerColor2>. |
151 | The mouse pointer background colour; resource B<pointerColor2>. |
152 | |
152 | |
153 | =item B<-bd> I<colour> |
153 | =item B<-bd> I<colour> |
154 | |
154 | |
155 | The colour of the border between the xterm scrollbar and the text; |
155 | The colour of the border around the text area and between the scrollbar and the text; |
156 | resource B<borderColor>. |
156 | resource B<borderColor>. |
157 | |
157 | |
158 | =item B<-fn> I<fontname> |
158 | =item B<-fn> I<fontlist> |
159 | |
159 | |
160 | Select the fonts to be used. This is a comma seperated list of font |
160 | Select the fonts to be used. This is a comma separated list of font names |
161 | names that are used in turn when trying to display Unicode characters. |
161 | that are used in turn when trying to display Unicode characters. The |
162 | The first font defines the cell size for characters; other fonts might |
162 | first font defines the cell size for characters; other fonts might be |
163 | be smaller, but not larger. A reasonable default font list is always |
163 | smaller, but not (in general) larger. A reasonable default font list is |
164 | appended to it. resource B<font>. |
164 | always appended to it. See resource B<font> for details. |
165 | |
165 | |
166 | See also the question "How does rxvt-unicode choose fonts?" in the FAQ |
166 | See also the question "How does rxvt-unicode choose fonts?" in the FAQ |
167 | section. |
167 | section. |
168 | |
168 | |
169 | =item B<-rb>|B<+rb> |
169 | =item B<-fb> I<fontlist> |
170 | |
170 | |
171 | Enable "real bold" support. When this option is on, bold text will be |
171 | Compile font-styles: The bold font list to use when bold characters are to |
172 | displayed using the first available bold font in the font list. Bold |
172 | be printed. See resource B<boldFont> for details. |
173 | fonts should thus be specified in the font list after their |
173 | |
174 | corresponding regular fonts. If no bold font can be found, a regular |
174 | =item B<-fi> I<fontlist> |
175 | font will be used. resource B<realBold>. |
175 | |
|
|
176 | Compile font-styles: The italic font list to use when bold characters are to |
|
|
177 | be printed. See resource B<italicFont> for details. |
|
|
178 | |
|
|
179 | =item B<-fbi> I<fontlist> |
|
|
180 | |
|
|
181 | Compile font-styles: The bold italic font list to use when bold characters are to |
|
|
182 | be printed. See resource B<boldItalicFont> for details. |
176 | |
183 | |
177 | =item B<-name> I<name> |
184 | =item B<-name> I<name> |
178 | |
185 | |
179 | Specify the application name under which resources are to be obtained, |
186 | Specify the application name under which resources are to be obtained, |
180 | rather than the default executable file name. Name should not contain |
187 | rather than the default executable file name. Name should not contain |
… | |
… | |
389 | high-intensity (bold = bright foreground, blink = bright background) |
396 | high-intensity (bold = bright foreground, blink = bright background) |
390 | colours. The canonical names are as follows: 0=black, 1=red, 2=green, |
397 | colours. The canonical names are as follows: 0=black, 1=red, 2=green, |
391 | 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour |
398 | 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour |
392 | names used are listed in the B<COLORS AND GRAPHICS> section. |
399 | names used are listed in the B<COLORS AND GRAPHICS> section. |
393 | |
400 | |
|
|
401 | Colours higher than 15 cannot be set using resources (yet), but can be |
|
|
402 | changed using an escape command (see @@RXVT_NAME@@(7)). |
|
|
403 | |
|
|
404 | Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with |
|
|
405 | 88 colour support). Colours 80-87 are evenly spaces grey steps. |
|
|
406 | |
394 | =item B<colorBD:> I<colour> |
407 | =item B<colorBD:> I<colour> |
395 | |
408 | |
|
|
409 | =item B<colorIT:> I<colour> |
|
|
410 | |
396 | Use the specified colour to display bold characters when the foreground |
411 | Use the specified colour to display bold or italic characters when the |
397 | colour is the default. This option will be ignored if B<realBold> is |
412 | foreground colour is the default. If font styles are not available |
398 | enabled. |
413 | (Compile styles) and this option is unset, reverse video is used instead. |
399 | |
414 | |
400 | =item B<colorUL:> I<colour> |
415 | =item B<colorUL:> I<colour> |
401 | |
416 | |
402 | Use the specified colour to display underlined characters when the |
417 | Use the specified colour to display underlined characters when the |
403 | foreground colour is the default. |
418 | foreground colour is the default. |
… | |
… | |
459 | |
474 | |
460 | =item B<troughColor:> I<colour> |
475 | =item B<troughColor:> I<colour> |
461 | |
476 | |
462 | Use the specified colour for the scrollbar's trough area [default |
477 | Use the specified colour for the scrollbar's trough area [default |
463 | #969696]. Only relevant for normal (non XTerm/NeXT) scrollbar. |
478 | #969696]. Only relevant for normal (non XTerm/NeXT) scrollbar. |
|
|
479 | |
|
|
480 | =item B<borderColor:> I<colour> |
|
|
481 | |
|
|
482 | The colour of the border around the text area and between the scrollbar |
|
|
483 | and the text. |
464 | |
484 | |
465 | =item B<backgroundPixmap:> I<file[;geom]> |
485 | =item B<backgroundPixmap:> I<file[;geom]> |
466 | |
486 | |
467 | Use the specified XPM file (note the `.xpm' extension is optional) for |
487 | Use the specified XPM file (note the `.xpm' extension is optional) for |
468 | the background and also optionally specify its scaling with a geometry |
488 | the background and also optionally specify its scaling with a geometry |
… | |
… | |
484 | |
504 | |
485 | Specify the colon-delimited search path for finding files (XPM and |
505 | Specify the colon-delimited search path for finding files (XPM and |
486 | menus), in addition to the paths specified by the B<RXVTPATH> and |
506 | menus), in addition to the paths specified by the B<RXVTPATH> and |
487 | B<PATH> environment variables. |
507 | B<PATH> environment variables. |
488 | |
508 | |
489 | =item B<font:> I<fontname> |
509 | =item B<font:> I<fontlist> |
490 | |
510 | |
491 | Select the fonts to be used. This is a comma seperated list of font |
511 | Select the fonts to be used. This is a comma separated list of font |
492 | names that are used in turn when trying to display Unicode characters. |
512 | names that are used in turn when trying to display Unicode characters. |
493 | The first font defines the cell size for characters; other fonts might |
513 | The first font defines the cell size for characters; other fonts might |
494 | be smaller, but not larger. A reasonable default font list is always |
514 | be smaller, but not larger. A reasonable default font list is always |
495 | appended to it. option B<-fn>. |
515 | appended to it. option B<-fn>. |
496 | |
516 | |
497 | =item B<realBold:> I<boolean> |
517 | Each font can either be a standard X11 core font (XLFD) name, with |
|
|
518 | optional prefix C<x:> or a Xft font (Compile xft), prefixed with C<xft:>. |
498 | |
519 | |
499 | B<True>: Enable "real bold" support. When this option is on, bold text |
520 | In addition, each font can be prefixed with additional hints and |
500 | will be displayed using the first available bold font in the font list. |
521 | specifications enclosed in square brackets (C<[]>). The only available |
501 | Bold fonts should thus be specified in the font list after their |
522 | hint currently is C<codeset=codeset-name>, and this is only used for Xft |
502 | corresponding regular fonts. If no bold font can be found, a regular |
523 | fonts. |
503 | font will be used. option B<-rb>. B<False>: Display bold text in a |
524 | |
504 | regular font, using the color specified with B<colorBD>; option B<+rb>. |
525 | For example, this font resource |
|
|
526 | |
|
|
527 | URxvt*font: 9x15bold,\ |
|
|
528 | -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ |
|
|
529 | -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ |
|
|
530 | [codeset=JISX0208]xft:Kochi Gothic:antialias=false, \ |
|
|
531 | xft:Code2000:antialias=false |
|
|
532 | |
|
|
533 | specifies five fonts to be used. The first one is C<9x15bold> (actually |
|
|
534 | the iso8859-1 version of the second font), which is the base font (because |
|
|
535 | it is named first) and thus defines the character cell grid to be 9 pixels |
|
|
536 | wide and 15 pixels high. |
|
|
537 | |
|
|
538 | the second font is just used to add additional unicode characters not in |
|
|
539 | the base font, likewise the third, which is unfortunately non-bold, but |
|
|
540 | the bold version of the font does contain less characters, so this is a |
|
|
541 | useful supplement. |
|
|
542 | |
|
|
543 | The third font is an Xft font with aliasing turned off, and the characters |
|
|
544 | are limited to the B<JIS 0208> codeset (i.e. japanese kanji). The font |
|
|
545 | contains other characters, but we are not interested in them. |
|
|
546 | |
|
|
547 | The last font is a useful catch-all font that supplies most of the |
|
|
548 | remaining unicode characters. |
|
|
549 | |
|
|
550 | =item B<boldFont:> I<fontlist> |
|
|
551 | |
|
|
552 | =item B<italicFont:> I<fontlist> |
|
|
553 | |
|
|
554 | =item B<boldItalicFont:> I<fontlist> |
|
|
555 | |
|
|
556 | The font list to use for displaying B<bold>, I<italic> or B<< I<bold |
|
|
557 | italic> >> characters, respectively. |
|
|
558 | |
|
|
559 | If specified and non-empty, then the syntax is the same as for the |
|
|
560 | B<font>-resource, and the given font list will be used as is, which makes |
|
|
561 | it possible to substitute completely different font styles for bold and |
|
|
562 | italic. |
|
|
563 | |
|
|
564 | If unset (the default), a suitable font list will be synthesized by |
|
|
565 | "morphing" the normal text font list into the desired shape. If that is |
|
|
566 | not possible, replacement fonts of the desired shape will be tried. |
|
|
567 | |
|
|
568 | If set, but empty, then this specific style is disabled and the normal |
|
|
569 | text font will being used for the given style. |
505 | |
570 | |
506 | =item B<selectstyle:> I<mode> |
571 | =item B<selectstyle:> I<mode> |
507 | |
572 | |
508 | Set mouse selection style to B<old> which is 2.20, B<oldword> which is |
573 | Set mouse selection style to B<old> which is 2.20, B<oldword> which is |
509 | xterm style with 2.20 old word selection, or anything else which gives |
574 | xterm style with 2.20 old word selection, or anything else which gives |
… | |
… | |
689 | The locale to use for opening the IM. You can use an LC_CTYPE of e.g. |
754 | The locale to use for opening the IM. You can use an LC_CTYPE of e.g. |
690 | de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input |
755 | de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input |
691 | extension to be able to input japanese characters while staying in |
756 | extension to be able to input japanese characters while staying in |
692 | another locale. option B<-imlocale>. |
757 | another locale. option B<-imlocale>. |
693 | |
758 | |
694 | =item B<insecure> |
759 | =item B<insecure:> I<boolean> |
695 | |
760 | |
696 | Enables "insecure" mode. Rxvt-unicode offers some escape sequences that |
761 | Enables "insecure" mode. Rxvt-unicode offers some escape sequences that |
697 | echo arbitrary strings like the icon name or the locale. This could be |
762 | echo arbitrary strings like the icon name or the locale. This could be |
698 | abused if somebody gets 8-bit-clean access to your display, wether |
763 | abused if somebody gets 8-bit-clean access to your display, wether |
699 | throuh a mail client displaying mail bodies unfiltered or though |
764 | throuh a mail client displaying mail bodies unfiltered or though |
… | |
… | |
851 | |
916 | |
852 | You enter this mode by holding down C<Control> and C<Shift> together, then |
917 | You enter this mode by holding down C<Control> and C<Shift> together, then |
853 | pressing and holding the left mouse button and moving around. The unicode |
918 | pressing and holding the left mouse button and moving around. The unicode |
854 | hex code(s) (it might be a combining character) of the character under the |
919 | hex code(s) (it might be a combining character) of the character under the |
855 | pointer is displayed until you release C<Control> and C<Shift>. |
920 | pointer is displayed until you release C<Control> and C<Shift>. |
|
|
921 | |
|
|
922 | In addition to the hex codes it will display the font used to draw this |
|
|
923 | character - due to implementation reasons, characters combined with |
|
|
924 | combining characters, line drawing characters and unknown characters will |
|
|
925 | always be drawn using the built-in support font. |
856 | |
926 | |
857 | =back |
927 | =back |
858 | |
928 | |
859 | With respect to conformance, rxvt-unicode is supposed to be compliant to |
929 | With respect to conformance, rxvt-unicode is supposed to be compliant to |
860 | both scenario A and B of ISO 14755, including part 5.2. |
930 | both scenario A and B of ISO 14755, including part 5.2. |
… | |
… | |
919 | |
989 | |
920 | =over 4 |
990 | =over 4 |
921 | |
991 | |
922 | =item How do I know which rxvt-unicode version I'm using? |
992 | =item How do I know which rxvt-unicode version I'm using? |
923 | |
993 | |
924 | The version number is displayed with the usage (-h). For rxvt-unicode |
994 | The version number is displayed with the usage (-h). Also the escape |
925 | version 2.14 and later, the escape sequence C<ESC[8n> sets the window |
995 | sequence C<ESC[8n> sets the window title to the version number. |
926 | title to the version number. |
996 | |
|
|
997 | =item When I log-in to another system it tells me about missing terminfo data? |
|
|
998 | |
|
|
999 | The terminal description used by rxvt-unicode is not as widely available |
|
|
1000 | as that for xterm, or even rxvt (for which the same problem often arises). |
|
|
1001 | |
|
|
1002 | The correct solution for this problem is to install the terminfo, this can be done |
|
|
1003 | like this: |
|
|
1004 | |
|
|
1005 | infocmp rxvt-unicode >rxvt.unicode.tic |
|
|
1006 | scp rxvt-unicode.tic remotesystem: |
|
|
1007 | ssh remotesystem tic rxvt-unicode.tic |
|
|
1008 | |
|
|
1009 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
1010 | |
|
|
1011 | If you cannot or do not want to do this, then you can simply set |
|
|
1012 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
|
|
1013 | problems arising, which includes wrong keymapping, less and different |
|
|
1014 | colours and some refresh errors in fullscreen applications. It's a nice |
|
|
1015 | quick-and-dirty workaround for rare cases, though. |
|
|
1016 | |
|
|
1017 | If you always want to do this you can either recompile rxvt-unicode with |
|
|
1018 | the desired TERM value or use a resource to set it: |
|
|
1019 | |
|
|
1020 | URxvt.termName: rxvt |
|
|
1021 | |
|
|
1022 | =item How can I configure rxvt-unicode so that it looks similar to the original rxvt? |
|
|
1023 | |
|
|
1024 | Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode |
|
|
1025 | behave similar to the original rxvt: |
|
|
1026 | |
|
|
1027 | URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
|
|
1028 | URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
927 | |
1029 | |
928 | =item Rxvt-unicode does not seem to understand the selected encoding? |
1030 | =item Rxvt-unicode does not seem to understand the selected encoding? |
929 | |
1031 | |
930 | =item Unicode does not seem to work? |
1032 | =item Unicode does not seem to work? |
931 | |
1033 | |
… | |
… | |
964 | your system/os) have specified does not cover all the characters you want |
1066 | your system/os) have specified does not cover all the characters you want |
965 | to display. |
1067 | to display. |
966 | |
1068 | |
967 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
1069 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
968 | font. Often the result is fine, but sometimes the chosen font looks |
1070 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
1071 | bad. Many fonts have totally strange characters that don't resemble the |
|
|
1072 | correct glyph at all, and rxvt-unicode lacks the artificial intelligence |
|
|
1073 | to detetc that a specific glyph is wrong: it has to believe the font that |
|
|
1074 | the characters it contains indeed look correct. |
|
|
1075 | |
969 | bad. In that case, select a font of your taste and add it to the font |
1076 | In that case, select a font of your taste and add it to the font list, |
970 | list, e.g.: |
1077 | e.g.: |
971 | |
1078 | |
972 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
1079 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
973 | |
1080 | |
974 | When rxvt-unicode sees a character, it will first look at the base |
1081 | When rxvt-unicode sees a character, it will first look at the base |
975 | font. If the base font does not contain the character, it will go to the |
1082 | font. If the base font does not contain the character, it will go to the |
976 | next font, and so on. |
1083 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
1084 | search and use less resources within rxvt-unicode and the X-server. |
977 | |
1085 | |
978 | The only limitation is that all the fonts must not be larger than the base |
1086 | The only limitation is that all the fonts must not be larger than the base |
979 | font, as the base font defines the principial cell size, which must be the |
1087 | font, as the base font defines the principial cell size, which must be the |
980 | same due to the way terminals work. |
1088 | same due to the way terminals work. |
981 | |
1089 | |
… | |
… | |
999 | In the future it might be possible to switch preferences at runtime (the |
1107 | In the future it might be possible to switch preferences at runtime (the |
1000 | internal data structure has no problem with using different fonts for |
1108 | internal data structure has no problem with using different fonts for |
1001 | the same character at the same time, but no interface for this has been |
1109 | the same character at the same time, but no interface for this has been |
1002 | designed yet). |
1110 | designed yet). |
1003 | |
1111 | |
|
|
1112 | =item How can I keep rxvt-unicode from using reverse video so much? |
|
|
1113 | |
|
|
1114 | First of all, make sure you are running with the right terminfo |
|
|
1115 | (C<urxvt>), which will get rid of most of these effects. Then make sure |
|
|
1116 | you have specified colours for italic and bold, as otherwise rxvt-unicode |
|
|
1117 | might use reverse video to simulate the effect: |
|
|
1118 | |
|
|
1119 | URxvt*colorBD: white |
|
|
1120 | URxvt*colorIT: green |
|
|
1121 | |
|
|
1122 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
|
|
1123 | |
|
|
1124 | For some unexplainable reason, some programs (i.e. irssi) assume a very |
|
|
1125 | weird colour palette when confronted with a terminal with more than the |
|
|
1126 | standard 8 colours (rxvt-unicode supports 88). The right fix is, of |
|
|
1127 | course, to fix these programs not to assume non-ISO colours without very |
|
|
1128 | good reasons. |
|
|
1129 | |
|
|
1130 | In the meantime, you can either edit your C<urxvt> terminfo definition to |
|
|
1131 | only claim 8 colour support or use C<TERM=rxvt>, which will fix colours |
|
|
1132 | but keep you from using other rxvt-unicode features. |
|
|
1133 | |
1004 | =item How does rxvt-unicode determine the encoding to use? |
1134 | =item How does rxvt-unicode determine the encoding to use? |
1005 | |
1135 | |
1006 | =item Is there an option to switch encodings? |
1136 | =item Is there an option to switch encodings? |
1007 | |
1137 | |
1008 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
1138 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
… | |
… | |
1062 | This is useful if you e.g. work primarily with japanese (and prefer a |
1192 | This is useful if you e.g. work primarily with japanese (and prefer a |
1063 | japanese font), but you have to switch to chinese temporarily, where |
1193 | japanese font), but you have to switch to chinese temporarily, where |
1064 | japanese fonts would only be in your way. |
1194 | japanese fonts would only be in your way. |
1065 | |
1195 | |
1066 | You can think of this as a kind of manual ISO-2022 switching. |
1196 | You can think of this as a kind of manual ISO-2022 switching. |
|
|
1197 | |
|
|
1198 | =item Why do italic characters look as if clipped? |
|
|
1199 | |
|
|
1200 | Many fonts have difficulties with italic characters and hinting. For |
|
|
1201 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
|
|
1202 | Mono> completely fails in it's italic face. A workaround is to enable |
|
|
1203 | freetype autohinting, i.e. like this: |
|
|
1204 | |
|
|
1205 | URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
1206 | URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
1207 | |
|
|
1208 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
|
|
1209 | |
|
|
1210 | You cna specify separate locales for the input method and the rest of the |
|
|
1211 | terminal, using the resource C<imlocale>: |
|
|
1212 | |
|
|
1213 | URxvt*imlocale: ja_JP.EUC-JP |
|
|
1214 | |
|
|
1215 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
|
|
1216 | use your input method. Please note, however, that you will not be able to |
|
|
1217 | input characters outside C<EUC-JP> in a normal way then, as your input |
|
|
1218 | method limits you. |
|
|
1219 | |
|
|
1220 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
|
|
1221 | |
|
|
1222 | Rxvt-unicode tries to obey the rule of not charging you for sth. you |
|
|
1223 | don't use. One thing you should try is to configure out all settings that |
|
|
1224 | you don't need, for example, Xft support is a resource hog by design, |
|
|
1225 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
1226 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
1227 | |
|
|
1228 | Also, many people (me included) like large windows and even larger |
|
|
1229 | scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use |
|
|
1230 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
1231 | kilobyte per line. A scorllback buffer of 10000 lines will then (if full) |
|
|
1232 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
|
|
1233 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
1234 | |
|
|
1235 | =item Can I speed up Xft rendering somehow? |
|
|
1236 | |
|
|
1237 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
1238 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
1239 | antialiasing (by appending C<:antialiasing=false>), which saves lots of |
|
|
1240 | memory and also speeds up rendering considerably. |
|
|
1241 | |
|
|
1242 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
|
|
1243 | |
|
|
1244 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
1245 | fall back to it's default font search list it will prefer X11 core |
|
|
1246 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
1247 | antialiaisng disabled for most of them, because the author thinks they |
|
|
1248 | look best that way. |
|
|
1249 | |
|
|
1250 | If you want antialiasing, you have to specify the fonts manually. |
1067 | |
1251 | |
1068 | =item Mouse cut/paste suddenly no longer works. |
1252 | =item Mouse cut/paste suddenly no longer works. |
1069 | |
1253 | |
1070 | Make sure that mouse reporting is actually turned off since killing |
1254 | Make sure that mouse reporting is actually turned off since killing |
1071 | some editors prematurely may leave the mouse in mouse report mode. I've |
1255 | some editors prematurely may leave the mouse in mouse report mode. I've |