| bio | website | l3.ms |
|---|---|---|
| location | Germany | |
| age | ||
| visits | member for | 2 years, 2 months |
| seen | Jan 29 at 1:12 | |
| stats | profile views | 2 |
Programming languages:
- C++/Qt
- PHP
To-Do list:
☑ Write a parser for a programming language of my choice
☐ Write a compiler for a programming language of my choice
☐ Write a linux kernel module
☐ Write an operating system
|
Jan 17 |
awarded | Popular Question |
|
Oct 29 |
awarded | Excavator |
|
Oct 29 |
awarded | Editor |
|
Oct 29 |
revised |
listing packages in Debian, a la `dpkg -l`, but including the package origin/source Nicer view of the output code (avoiding line breaks) |
|
Oct 29 |
suggested | suggested edit on listing packages in Debian, a la `dpkg -l`, but including the package origin/source |
|
Mar 20 |
comment |
Terminal charset / font To be more specific, I code in C++ and have access to termios and stuff... Maybe I can set the encoding of the underlying console manually? |
|
Mar 20 |
comment |
Terminal charset / font Yeah, I already feared that I dont get proper unicode support in the terminal... But thanks for the IBM code page link, I searched for this but didn't know what to search for. I think these characters are enough. I do not want to support only the linux terminal but I want to support it too. Can you tell me how I can use the IBM 437 chars using unicode? The unicode characters I mentioned don't get "converted" automatically. (They are properly displayed in a graphical console (I use gnome-terminal with unicode).) Is there any way of supporting both console types? |
|
Mar 20 |
awarded | Scholar |
|
Mar 20 |
accepted | Terminal charset / font |
|
Mar 19 |
awarded | Student |
|
Mar 19 |
asked | Terminal charset / font |