Anton Kochkov
Anton Kochkov
I started gathering the summary gist (like I did with true color one) and linked this issue in it https://gist.github.com/XVilka/a0e49e1c65370ba11c17
Please note, recently there was created a working group regarding BiDi support in a console: - https://terminal-wg.pages.freedesktop.org/bidi/ - https://gitlab.freedesktop.org/terminal-wg/bidi
Note, that with the release of [GNOME 3.34](https://www.gnome.org/news/2019/09/gnome-3-34-released/) the support of BiDi by @egmontkob is available in Gnome Terminal out of the box, which makes testing/implementing it in the other...
@imbillow could you please add also the mapping for PIC and https://github.com/rizinorg/rz-ghidra/issues/341?
@imbillow now that Rizin supports Xtensa, could you please address this one too?
It is already here: https://ci.appveyor.com/project/rizinorg/rizin/builds/50125190/job/6ewk3740kyarh9r1/artifacts Just choose: CI statuses for every commit, click AppVeyor one, then choose VS2022 job, then Artifacts tab.
@gogo2464 does it solve your problem?
Do you mean editing the sections of the executable? In general this is very complex process since it performs rebuilding the binary from scratch. In simple cases using something like...
@rodnymolina, I have a Dockerfile that somewhere inside calls `docker run ...`. Currently, sysbox is the default runtime on my server, so I don't need to supply any additional parameters....
@rodnymolina was my information sufficient on reproducing the issue?