Where did you get that strange idea Linux 3D performance is terrible? I won't deny that OpenSource drivers can be less efficient that close source driver especially on devices that are not properly documented and must be reversed engineered. However, if you only consider the drivers provided by the vendors, the performances are usually similar to the Windows driver.
Of course, Windows is usually a higher priority for the vendors so there is often a small delay before a good driver becomes available on Linux for new hardware.
You missed the point. I assume that by "profile" you mean the termcap or terminfo entries. They are not there to "map the keyboard onto the imaginary terminal". Their purpose is to tell to the applications how to talk to the terminal. When an shell application such as emacs or vim needs to perform an action such as moving the cursor or changing the color of the text, it needs to know which sequence of special characters must be sent to the terminal. This information is provided by the local copy of the termcap entry. The terminal that will interpret those characters may be located several thousands kilometres away.
This is especially useful for systems that can be accessed remotely. The terminal emulator you use to get a local shell on your machine is only a special case. Each of those 2615 entries is a driver for a terminal or a terminal emulator that could potentially be used to connect to the machine.
Consider for instance the putty entry. Putty is a windows terminal emulator so you could think that it is useless on a Linux system but removing it would make it more difficult to access your Linux machine from Window.
For instance, I see that there is a hp9845 in my database so if tomorrow I find a old HP9845 (http://www.hp9845.net/) in a junk shop, I could potentially connect it to my linux box via a serial line. From there I could log via SSH into my account on the Titan supercomputer at Oak Ridge National Lab. Emacs and other tty application should work fine assuming that the hp9845 termcap is also installed on Titan.
Of course, the sysadmin on Titan never imagined or cared that I could access the machine from an old hp9845. Most entries in the termcap data may seem useless but they are a bit like with multimedia codecs; it is better to have as many as possible even if you do not plan to ever use them.
Also, even if we ignore old hardware and emulators for old systems, we should not underestimate the number of entries that are potentially relevant for a significant amount of users: konsole (KDE), eterm (term in emacs), putty (Windows), vte (gnome), linux (the linux console), bsdos-*, xrvt, screen, tmux,...
There are also plenty of variants for different numbers of colors (e.g. xterm vs xterm-256color) or multiplexers (screen.gnome, screen.linux, screen.xterm,...).
You are wondering which entry to choose. Actually, you should not have to make a choice unless you are using a real terminal connected via a serial line. Any terminal emulator should already select the right termcap entry for you. What you may want to do is specialize the provided choice to get more feature. For instance change TERM=xterm into TERM=xterm-256color so that your applications know that they can use 256 colors instead of the default 32.
I agree. I am a big terminal user and after trying a few, I am back to XTerm.
A few years ago, XTerm was limited to bitmap fonts which was quickly becoming a problem at high resolution. This is not the case anymore.
For me, the killing feature is the ability to change the default background color using an escape sequence. I have a few shell aliases (.red,.blue,...) to change the color theme. Somehow, this simple feature is not supported by most other terminal emulators.
Also, XTerm uses the X11 resource mechanism. That is a bit obsolete according to modern standards but that makes it highly configurable for specific needs.
To be honest, this is something I would also do on slightly more complex sequence of if-then-else-if that are supposed to try all possibilities. Similarly, I always try to enforce the 'default:' on switch statement even if I know that all possible values are tested.
That may be unnecessary at the time I write the code but that can save my ass if someone decides to make a small 'harmless' change in a few months or years.
The funny thing is that in C++, it is actually possible to reach the final 'else' assuming that 'p' is not a pointer but of a type that overloads 'operator bool' and 'operator !'.
However, the ttf version has a problem in Emacs: There is a lot of horizontal space between the characters. About 1/2 the character width. I do not see this problem in xterm or other applications. Also the font looks fine in the emacs font selector dialog (that's the GTK2 dialog).
You wll never be happy because laptops will never be as powerful as desktops. Simply speaking, if you manage to create a laptop as powerful as a desktop then you can also create a more powerful desktop. That is not a matter of computing power but of temperature. Desktop are by definition bigger than laptops so they can dissipate more heat.
Slashdot Mirror
Where did you get that strange idea Linux 3D performance is terrible? I won't deny that OpenSource drivers can be less efficient that close source driver especially on devices that are not properly documented and must be reversed engineered. However, if you only consider the drivers provided by the vendors, the performances are usually similar to the Windows driver.
Of course, Windows is usually a higher priority for the vendors so there is often a small delay before a good driver becomes available on Linux for new hardware.
So webcam support is broken in 4.4-rc1. Is that on the Pi or on x86?
You missed the point. I assume that by "profile" you mean the termcap or terminfo entries. They are not there to "map the keyboard onto the imaginary terminal". Their purpose is to tell to the applications how to talk to the terminal. When an shell application such as emacs or vim needs to perform an action such as moving the cursor or changing the color of the text, it needs to know which sequence of special characters must be sent to the terminal. This information is provided by the local copy of the termcap entry. The terminal that will interpret those characters may be located several thousands kilometres away.
This is especially useful for systems that can be accessed remotely. The terminal emulator you use to get a local shell on your machine is only a special case. Each of those 2615 entries is a driver for a terminal or a terminal emulator that could potentially be used to connect to the machine.
Consider for instance the putty entry. Putty is a windows terminal emulator so you could think that it is useless on a Linux system but removing it would make it more difficult to access your Linux machine from Window.
For instance, I see that there is a hp9845 in my database so if tomorrow I find a old HP9845 (http://www.hp9845.net/) in a junk shop, I could potentially connect it to my linux box via a serial line. From there I could log via SSH into my account on the Titan supercomputer at Oak Ridge National Lab. Emacs and other tty application should work fine assuming that the hp9845 termcap is also installed on Titan.
Of course, the sysadmin on Titan never imagined or cared that I could access the machine from an old hp9845. Most entries in the termcap data may seem useless but they are a bit like with multimedia codecs; it is better to have as many as possible even if you do not plan to ever use them.
Also, even if we ignore old hardware and emulators for old systems, we should not underestimate the number of entries that are potentially relevant for a significant amount of users: konsole (KDE), eterm (term in emacs), putty (Windows), vte (gnome), linux (the linux console), bsdos-*, xrvt, screen, tmux, ...
There are also plenty of variants for different numbers of colors (e.g. xterm vs xterm-256color) or multiplexers (screen.gnome, screen.linux, screen.xterm, ...).
You are wondering which entry to choose. Actually, you should not have to make a choice unless you are using a real terminal connected via a serial line. Any terminal emulator should already select the right termcap entry for you. What you may want to do is specialize the provided choice to get more feature. For instance change TERM=xterm into TERM=xterm-256color so that your applications know that they can use 256 colors instead of the default 32.
I agree. I am a big terminal user and after trying a few, I am back to XTerm.
A few years ago, XTerm was limited to bitmap fonts which was quickly becoming a problem at high resolution. This is not the case anymore.
For me, the killing feature is the ability to change the default background color using an escape sequence. I have a few shell aliases (.red, .blue, ...) to change the color theme. Somehow, this simple feature is not supported by most other terminal emulators.
Also, XTerm uses the X11 resource mechanism. That is a bit obsolete according to modern standards but that makes it highly configurable for specific needs.
Give us a break ... I mean ... line breaks!
To be honest, this is something I would also do on slightly more complex sequence of if-then-else-if that are supposed to try all possibilities. Similarly, I always try to enforce the 'default:' on switch statement even if I know that all possible values are tested.
That may be unnecessary at the time I write the code but that can save my ass if someone decides to make a small 'harmless' change in a few months or years.
The funny thing is that in C++, it is actually possible to reach the final 'else' assuming that 'p' is not a pointer but of a type that overloads 'operator bool' and 'operator !'.
Obviously, learning formal logic did not help improve your writing skills.
Please! Mark parent as Funny
Please! Do no obscure the debate with facts!
Hummm... I am pretty sure that any quantum physicist would disagree with you.
Phrenology! Is that similar to Dickology but only applied to human heads?
> What about a constant that describes the relationship of the volume of a sphere to its radius/diameter?
Uhhhh.... Pi? or if you prefer 4/3*Pi
Anyways, I do not believe that Pi, 2 Pi or 4/3 Pi are fundamentally different.
Let's assume that today we receive a message from outer space and with the number 1.01015254455 .
How much time will it take to figure out how it was obtained?
Like this one: http://apod.nasa.gov/apod/ap14...
ASL is the ACPI human language.
Or if you are not root, drop it into ~/.fonts/
Also I noticed that in 11pt the 'u' is taller than other characters in emacs and in some gtk2 apps but not in xterm !!!!
Looks good. I'll give it a try.
However, the ttf version has a problem in Emacs: There is a lot of horizontal space between the characters. About 1/2 the character width.
I do not see this problem in xterm or other applications. Also the font looks fine in the emacs font selector dialog (that's the GTK2 dialog).
The otf version looks fine in Emacs
Being even more pedant I will point out that the improvement is a lore more. What is important here is the error rate.
Simply speaking, they went from 4.82 to 4.58 so the improvement is (4.82-4.58)/4.82 = 0.0497 ~= 5%
Another way to see that is that Google made 48200 errors on the full set of 1 Million images while Baidus made only 45800 errors.
You wll never be happy because laptops will never be as powerful as desktops. Simply speaking, if you manage to create a laptop as powerful as a desktop then you can also create a more powerful desktop. That is not a matter of computing power but of temperature. Desktop are by definition bigger than laptops so they can dissipate more heat.
Think of the children!
Don't worry. I don't know you but I also feel that I hate you.
You are a genius
I always wondered how hard it would be for an ISP to hide a microphone in all their ADSL/Cable Box.
No. It is called D&D but some say it is only a placebo.
You missed the reference. I give you a hint. It starts with Monty and ends with a snake.