| eyalroz | There's this issue with lesspipe that's been bothering me | 09:52 |
|---|---|---|
| eyalroz | or rather, with its default choice of colors | 09:52 |
| eyalroz | For some reason, when highlighting source files (e.g. C/C++), it uses black, on a black terminal, for function names | 09:53 |
| eyalroz | So I was wondering - how do you change the color scheme there? | 09:57 |
| gnarface | eyalroz: this lesspipe? looks like it says it uses a perl script: https://www-zeuthen.desy.de/~friebel/unix/lesspipe.html | 10:35 |
| eyalroz | Well, to be more exact, lesspipe uses libsource-highlight | 10:35 |
| eyalroz | Which has a bunch of files in /usr/share/source-highlight | 10:35 |
| eyalroz | but I can't quite figure out where the color scheme is defined, nor whether it is adapted to the terminal's colors (or at least background) | 10:36 |
| eyalroz | gnarface: btw, am I the only one who has this issue with syntax highlighting in less on a black terminal, or have you / others also seen this? | 10:37 |
| eyalroz | anyway, here's an example: | 10:39 |
| eyalroz | https://imgur.com/a/VduG6fO | 10:39 |
| gnarface | eyalroz: all i can tell you for sure is that i don't have the same issue with emacs | 10:42 |
| gnarface | my guess is you're gonna have to read the script to figure it out | 10:42 |
| gnarface | mabye it actually parses ~/.Xresources or something useful like that | 10:43 |
| gnarface | but i've never heard of this and i don't really know | 10:43 |
| eyalroz | gnarface: I don't even have an ~/.Xresources | 11:00 |
| eyalroz | Maybe I'll file a bug report about the difficulty of playing with highlight colors | 11:00 |
| eyalroz | against libsource-highlight | 11:00 |
| xrogaan | simple inquiry, does everybody else here has the line "Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist" in their /var/log/kern.log? | 16:47 |
| * debdog hasn't | 16:50 | |
| debdog | though tomoyo-tools are not installed | 16:50 |
| xrogaan | err, are you on beowulf? | 16:51 |
| debdog | no, not on this PC | 16:52 |
| xrogaan | right, so, for people running beowulf then? :P | 16:52 |
| debdog | hehe | 16:52 |
| xrogaan | my /boot/config-* file has the line: | 16:55 |
| xrogaan | CONFIG_LSM="lockdown,yama,loadpin,safesetid,integrity,apparmor,selinux,smack,tomoyo" | 16:55 |
| xrogaan | I don't know why tomoyo is in there | 16:55 |
| xrogaan | is that the default config? | 17:01 |
| eyalroz | @gnarface: This _is_ a package issue. Or rather, an issue with the upstream library | 19:26 |
| eyalroz | The colors are defined in /usr/share/source-highlight/esc.style , which has the line: | 19:28 |
| eyalroz | function black b; | 19:28 |
| eyalroz | you see? Black on black. | 19:28 |
| eyalroz | I just checked the upstream repo again - it doesn't have that. Its functions are blue. | 19:28 |
| eyalroz | xrogaan: It's default on Devuan, it seems | 20:18 |
| eyalroz | xrogaan: Sorry, ignore my last message. | 20:18 |
| nemo | https://github.com/Xylemon/xlennart#about | 21:36 |
| gnarface | eyalroz: yuck, hardcoded. well i was afraid of that but i was trying not to be so negative. maybe what the world needs is a patch for it to parse ~/.Xresources | 23:07 |
| eyalroz | gnarface: You mean, for overwrites of the system-wide defaults? | 23:08 |
| gnarface | eyalroz: yes, that's how everything else that uses it works. i wouldn't suggest making the presence of a ~/.Xresources file mandatory. that is against it's own rules. | 23:09 |
| gnarface | there is a file somewhere with all the system-level defaults | 23:10 |
| eyalroz | but why that file? | 23:12 |
| eyalroz | I mean, the library has nothing to do with X | 23:12 |
| eyalroz | gnarface: I mean libsource-highlight | 23:13 |
| eyalroz | Anyway, even if there's a baked-in default - why would the Debian package maintainer bake in something different, and dangerous, like black function identifiers? | 23:14 |
| gnarface | eyalroz: probably he had terminals with blue backgrounds. some of the debian maintainers are short-sighted assholes. you can only do so much with volunteer labor. | 23:18 |
| gnarface | eyalroz: the reason i'd pick that one out specifically is just that lots of other terminals and x programs have used it. it's ancient and the standard, such as it is, isn't a target for corporate policy manipulation | 23:19 |
| gnarface | so it seemed like the closest thing to a starting point for something the work had already been done in | 23:20 |
| gnarface | i'd expect you wouldn't really have to parse the file yourself either. i assume there's some tools in there somewhere to automate or at least streamline tokenizing it | 23:20 |
| gnarface | i just haven't messed with ti | 23:20 |
| eyalroz | But actually, would even a per-used setting cut it? | 23:21 |
| eyalroz | I mean, maybe I use one terminal window with white background and another with black background etc. | 23:21 |
| gnarface | like a command-line option just for that one color field? sure that sounds easy too, just not a complete solution for every case. the only other idea along those lines that i have is the /usr/bin/dircolors thingy that is called from your ~/.bash_profile to set the default ansi colors | 23:21 |
| gnarface | (but since that is specifically intended for directory listings, i figured the Xresources thing would be more appropriate, but i could honestly be wrong about that) | 23:22 |
| eyalroz | Not just one color field, maybe even a map of all of them. Or at least something like dircolors. | 23:22 |
| gnarface | i guess the other thing i had in mind about ~/.Xresources is i figured you could find a lot of well-chosen default color palettes in the wild for it, and my unstated assumption is that this won't end with you just changing one color field. you're probably gonna eventually at least want to be able to change them all as a set. | 23:24 |
| eyalroz | Anyway, this all sounds like something to put on the plate of the libsource-highlighting author. But with the current state of affairs... | 23:25 |
| eyalroz | what should we do? | 23:25 |
| eyalroz | I mean, I suppose a bug report to the Debian package maintainer is in order, | 23:26 |
| eyalroz | but: 1. Should I do something else? 2. Do you (or you all) want to do something about this? | 23:27 |
| gnarface | eyalroz: well, at this point i have no vested interest in it other than the academic, and you've identified the field, so the fastest most efficient way for you to get back to work is to just change it to another hardcoded value | 23:32 |
| gnarface | and that's my professional advice for what to do | 23:33 |
| eyalroz | Oh, of course I've already done that on my system... | 23:33 |
| gnarface | my ethical advice suggests yes, you should file the bug report and try to as calmly state how stupid the defaults are and how much better the upstream ones are | 23:33 |
| eyalroz | I meant, to make sure Devuan is spared this shameful display... :-P | 23:33 |
| gnarface | hmmm | 23:33 |
| gnarface | to be clear | 23:33 |
| gnarface | i don't work here | 23:34 |
| gnarface | but... golinux may feel like weighing in on Devuanized color defaults | 23:34 |
| gnarface | (she's the designated colorizer) | 23:34 |
| eyalroz | Oh, I thought you had some official capacity, since you're so often on the channel and so responsive... | 23:34 |
| gnarface | no, i just don't have a life and i fear the outside world | 23:35 |
| eyalroz | I try split my non-life between multiple pursuits | 23:35 |
| gnarface | and also i remember what it was like to have the ladder pulled up in front of me by people who had already gotten there, so i like to try to be more supportive to others in the same position than others were to me | 23:36 |
| eyalroz | gnarface: That's very kind of you | 23:40 |
| eyalroz | or rather, I should say, very fair and reasonable of you; it's the opposite behavior that should be de-legitimized... | 23:41 |
| aitor | hi | 23:55 |
| fsmithred | hi aitor, why are you incognito? | 23:57 |
| fsmithred | Guest46359, ^^^ | 23:57 |
| Guest46359 | i'm trying to learn devuan from the very begining | 23:57 |
| Guest46359 | what about devuan jessie? | 23:57 |
| Guest46359 | :) | 23:57 |
| fsmithred | she's getting old | 23:57 |
| fsmithred | there might be instructions for upgrading jessie directly to beowulf | 23:58 |
| gnarface | Guest46359: you didn't really miss anything between jessie and ascii | 23:59 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!