Am Dienstag, 19. Januar 2021, 04:21:35 EET schrieb Walter Dnes:
> Maybe I should've kept quiet. The unicode fanbois probably saw this
> thread and decided to get heavy-handed. On my latest pretend update,
> I'm getting 8 (eight) rebuilds with "(unicode*)" being the reason.
That would've been
Maybe I should've kept quiet. The unicode fanbois probably saw this
thread and decided to get heavy-handed. On my latest pretend update,
I'm getting 8 (eight) rebuilds with "(unicode*)" being the reason.
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
Am Mittwoch, 30. Dezember 2020, 20:01:32 EET schrieb antlists:
> On 30/12/2020 17:30, Andreas K. Huettel wrote:
> > That's true, though registrars are filtering for it now. Also, I just
> > checked, e.g. firefox always builds with unicode support (it would have
> > trouble with a lot of websites
On 30/12/2020 17:30, Andreas K. Huettel wrote:
That's true, though registrars are filtering for it now. Also, I just checked,
e.g. firefox always builds with unicode support (it would have trouble with a
lot of websites otherwise).
(: ˙˙˙ǝpoɔᴉun sǝop oslɐ ʇuǝᴉlɔ lᴉɐɯ ɹnoʎ uǝɥʇ ¿sᴉɥʇ pɐǝɹ noʎ
On 30/12/2020 16:35, Andreas K. Huettel wrote:
I don't know if this has improved over the years, but my initial
experience with unicode was rather negative. The fact that text
files were twice as large wasn't a major problem in itself. The
real showstopper was that importing text files into
> On top of that Cyrillic letters like "m", "i", "c", and "o" are
> considered different from their English equivalants. Security experts
> showed proof-of-cocept attacks where clicking on "microsoft.com" can
> take you to a hostile domain (queue the jokes).
That's true, though registrars
> I don't know if this has improved over the years, but my initial
> experience with unicode was rather negative. The fact that text
> files were twice as large wasn't a major problem in itself. The
> real showstopper was that importing text files into spreadsheets
> and text-editors and word
On Tue, Dec 29, 2020 at 05:11:36PM +0200, Andreas K. Huettel wrote
> Hi Walter,
>
> > "-pch -roaming -sendmail -spell -tcpd -udev -udisks -unicode -upower
> > -xinerama"
>
> mostly out of curiosity, why do you want to disable unicode support
> here?
>
> This feels odd to me since utf8 has
Hi Walter,
> "-pch -roaming -sendmail -spell -tcpd -udev -udisks -unicode -upower
> -xinerama"
mostly out of curiosity, why do you want to disable unicode support here?
This feels odd to me since utf8 has effectively become the standard encoding
over the past years.
Cheers,
Andreas
--
On Mon, Dec 28, 2020 at 11:52:21PM +0100, tastytea wrote
>
> Bash depends on readline. If readline was built with USE="unicode" it
> depends on ncurses[unicode]. Try `chroot /mnt/gentoo /bin/busybox sh`.
> Busybox doesn't depend on readline so that should work. However,
> portage uses bash for
On 2020-12-28 16:36-0500 "Walter Dnes" wrote:
> The previous couple of attempts, the install on my XPS 8940 died on
> rebuilding ncurses when I copied over my full USE string from my
> current desktop and updated world. This time around, I did it in
> pieces. I added some variables, and
Walter Dnes wrote:
> The previous couple of attempts, the install on my XPS 8940 died on
> rebuilding ncurses when I copied over my full USE string from my current
> desktop and updated world. This time around, I did it in pieces. I
> added some variables, and emerged update,
On Mon, 28 Dec 2020 at 22:37, Walter Dnes wrote:
>On my other machines I tried...
>
> equery b libtinfow.so.6
I think you need to use full paths with equery b.
I combined it with whereis to confirm that /usr/lib/libtinfow.so.6
belongs to ncurses, so I guess what you need to figure out is why
13 matches
Mail list logo
