… | |
… | |
54 | |
54 | |
55 | urxvt --background-expr 'scale keep { load "/path/to/mybg.png" }' |
55 | urxvt --background-expr 'scale keep { load "/path/to/mybg.png" }' |
56 | |
56 | |
57 | Or specified as a X resource: |
57 | Or specified as a X resource: |
58 | |
58 | |
59 | URxvt.background-expr: scale keep { load "/path/to/mybg.png" } |
59 | URxvt.background.expr: scale keep { load "/path/to/mybg.png" } |
60 | |
60 | |
61 | =head1 THEORY OF OPERATION |
61 | =head1 THEORY OF OPERATION |
62 | |
62 | |
63 | At startup, just before the window is mapped for the first time, the |
63 | At startup, just before the window is mapped for the first time, the |
64 | expression is evaluated and must yield an image. The image is then |
64 | expression is evaluated and must yield an image. The image is then |
… | |
… | |
132 | get a percentage): |
132 | get a percentage): |
133 | |
133 | |
134 | scale 2, load "$HOME/mypic.png" |
134 | scale 2, load "$HOME/mypic.png" |
135 | |
135 | |
136 | This enlarges the image by a factor of 2 (200%). As you can see, C<scale> |
136 | This enlarges the image by a factor of 2 (200%). As you can see, C<scale> |
137 | has now two arguments, the C<200> and the C<load> expression, while |
137 | has now two arguments, the C<2> and the C<load> expression, while |
138 | C<load> only has one argument. Arguments are separated from each other by |
138 | C<load> only has one argument. Arguments are separated from each other by |
139 | commas. |
139 | commas. |
140 | |
140 | |
141 | Scale also accepts two arguments, which are then separate factors for both |
141 | Scale also accepts two arguments, which are then separate factors for both |
142 | horizontal and vertical dimensions. For example, this halves the image |
142 | horizontal and vertical dimensions. For example, this halves the image |