… | |
… | |
48 | TODO: rclock iso mode? |
48 | TODO: rclock iso mode? |
49 | |
49 | |
50 | TODO: printf "\e[4:3m" - "undercurl" - should probbaly be interpreted as underline, rather than \e[43m |
50 | TODO: printf "\e[4:3m" - "undercurl" - should probbaly be interpreted as underline, rather than \e[43m |
51 | TODO: click through mode / https://shallowsky.com/blog/2017/Apr/06/ |
51 | TODO: click through mode / https://shallowsky.com/blog/2017/Apr/06/ |
52 | |
52 | |
53 | TODO: |
|
|
54 | 03:32:26 <BlueFish> Hi. I think I found a bug in special_encode in rxvtperl.xs |
|
|
55 | 03:33:37 <BlueFish> special_encode('لا') or any other string that contains 'لا' returns a disturbed string |
|
|
56 | 03:33:40 <schmorp> hi BlueFish |
|
|
57 | 03:34:10 <schmorp> whats a disturbed string? |
|
|
58 | 03:34:25 <BlueFish> for example سلام becomes ملام |
|
|
59 | 03:35:05 <BlueFish> see this issue: https://github.com/mkamensky/Text-Bidi/issues/10 I was trying to fix it |
|
|
60 | and after playing around for a while found out that special_encode is causing the problem |
|
|
61 | 03:35:36 <schmorp> does this happen when you compile without --enable-combining (or with --disable-combining)? |
|
|
62 | 03:37:40 <BlueFish> I don't know the one that I installed from my distro repository has this flag or not. Is |
|
|
63 | there anyway to check? |
|
|
64 | 03:38:49 <schmorp> rxvt --help will output a options: line at the top, whioch will list "combining" |
|
|
65 | 03:39:10 <schmorp> anyway, I don't think i will understand this at my current tiredness level, I'll have a |
|
|
66 | look when I have time |
|
|
67 | 03:39:26 <schmorp> are you usually around on this network, so I coulöd ask you in cas eI have questions? |
|
|
68 | 03:40:25 <BlueFish> yes combining is enabled. No I don't check IRC that much. You can reach me via email |
|
|
69 | 03:40:44 <schmorp> ok, thats fine |
|
|
70 | 03:40:40 <BlueFish> avestasabayemoghadam@gmail.com |
|
|
71 | |
|
|
72 | - implement a fix for CVE-2022-4170 (reported and analyzed by David Leadbeater). |
53 | - implement a fix for CVE-2022-4170 (reported and analyzed by David Leadbeater). |
73 | While present in version 9.30, it should not be exploitable. It is exploitable |
54 | While present in version 9.30, it should not be exploitable. It is exploitable |
74 | in versions 9.25 and 9.26, at least, and allows anybody controlling terminal |
55 | in versions 9.25 and 9.26, at least, and allows anybody controlling terminal |
75 | input to execute arbitrary code in the urxvt process. |
56 | input to execute arbitrary code in the urxvt process. |
76 | - the background extension no longer requires off focus fading support |
57 | - the background extension no longer requires off focus fading support |
… | |
… | |
85 | - fix regression that caused urxvt to no longer process OSC 705. |
66 | - fix regression that caused urxvt to no longer process OSC 705. |
86 | - restore CENTURY to be 1900 to "improve" year parsing in urclock (or at |
67 | - restore CENTURY to be 1900 to "improve" year parsing in urclock (or at |
87 | least go back to the old interpretation) (based on an analysis |
68 | least go back to the old interpretation) (based on an analysis |
88 | by Tommy Pettersson). |
69 | by Tommy Pettersson). |
89 | - exec_async (used e.g. by the matcher extension to spawn processes) now |
70 | - exec_async (used e.g. by the matcher extension to spawn processes) now |
90 | sets the URXVT_EXT_WINDOWID variable to the window id opf the terminal. |
71 | sets the URXVT_EXT_WINDOWID variable to the window id of the terminal. |
91 | - implement -fps option/refreshRate resource to change the default 60 Hz |
72 | - implement -fps option/refreshRate resource to change the default 60 Hz |
92 | maximum refresh limiter. I always wanted an fps option, but had to |
73 | maximum refresh limiter. I always wanted an fps option, but had to |
93 | wait for a user requesting it. |
74 | wait for a user requesting it. |
94 | |
75 | |
95 | 9.30 Sat 27 Nov 2021 21:07:09 CET |
76 | 9.30 Sat 27 Nov 2021 21:07:09 CET |