X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-Id: <1318598287.3598.140660985920089@webmail.messagingengine.com> From: "Ronald Fischer" To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" Subject: Mapping "underline" to "colour" - how is the colour determined? Date: Fri, 14 Oct 2011 15:18:07 +0200 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com When I (to give an example) execute a "man" command within a mintty window, and do the same within a "normal" Windows console window, I see that those words represented as underlined words in the mintty window, are represented by a different colour in the Windows console windows. I guess this different has nothing to do with the "man" command, but by the way the terminal definition says how render "emphasized" words. Since the Windows console (likely) can't underline, colouring is used. It's kind of a "terminal property". Do I understand this correctly? I would like to understand, where this mapping to a certain colour is done. Reason is that the colour used for my Windows console window, is a bit hard to read and I would like to change it. Any suggestions? Ronald -- Ronald Fischer + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Ronald Fischer + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple