Sponsored Content
Full Discussion: Xterm with Pine
Top Forums UNIX for Dummies Questions & Answers Xterm with Pine Post 5069 by radimus on Tuesday 7th of August 2001 11:56:24 AM
Old 08-07-2001
Question Xterm with Pine

Hello,

Does anyone know why I'm not able to get colors in Pine when using Xterm, but I can get them using Dtterm?

Any answers to this would be much appreciated.

Radimus.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Pine

Hi :- I am trying to make a script to send mail using pine. But it takes me to the Pine Menu Console and I have to send it manually. Note that I am attaching a file with it. Any quick response will be highly appreciated. (4 Replies)
Discussion started by: s_aamir
4 Replies

2. UNIX for Dummies Questions & Answers

Avoid spam in pine?

Hi there, for email we are using "pine" on SSH. is there any way to block junk mail on pine? i've been lookin for sumthin that allows me to block senders but all my efforts in vain. can sum1 help me on that? Thanks (1 Reply)
Discussion started by: a25khan
1 Replies

3. UNIX for Dummies Questions & Answers

Pine inbox

i have shell account at grex.org but i cannot get mauil with pine because the inbox cannot be found? any suggestion? (7 Replies)
Discussion started by: cogeek
7 Replies

4. UNIX for Dummies Questions & Answers

Trouble configuring Pine

I am having trouble confiuring pine. I have downloaded it on 2 computers 1 with freebsd and the other fedora and I am getting the same result in both. Both say "folder does not exist","no folder to open". I went into set up and configured personal name,user-domain,smtp-server,inbox-path. I know I... (1 Reply)
Discussion started by: m8trix
1 Replies

5. UNIX for Dummies Questions & Answers

pine

how to configure pine in my linux os (1 Reply)
Discussion started by: rajan_ka1
1 Replies

6. Solaris

problem installing pine

when i try to build pine unix tells me it can't find make # ./build xxx make args are CC=cc soc Including LDAP functionality ln: cannot create c-client: File exists ln: cannot create mtest: File exists ln: cannot create mailutil: File exists ln: cannot create imapd: File exists ln:... (0 Replies)
Discussion started by: vutty81
0 Replies

7. Shell Programming and Scripting

how to find pine messages

still touching on the basics here: first of all where are my received messages stored in pine? /var/spool/mymail is not it. i guess i cant start my script without knowing this. because i need to move those files into a seperate folder and so on and so forth. I can prolly do a... (0 Replies)
Discussion started by: oxoxo
0 Replies

8. Shell Programming and Scripting

Moving msgs in pine

hey im writing a script like this: #!/bin/bash #Name: moveMail #Purpose: To move some files in the pine inbox to a folder on the desktop #Step one: Find all messages with that have the subject "Hello" in them. #---------------------------------------------------------------------... (1 Reply)
Discussion started by: oxoxo
1 Replies

9. UNIX for Dummies Questions & Answers

Problem with Pine

I'm learning a little about pine after downloading it. I can't seem to get it to work, though. It can't open the inbox -- it sits there (as the little slash mark rotates) but after a while it stops and can't make the connection, with a message saying that "connection to gmail.pop....(something)... (0 Replies)
Discussion started by: Straitsfan
0 Replies

10. UNIX for Dummies Questions & Answers

Forwarding mail via Pine

I am asking about my work account, running Linux on a system server. On pine, I set up a forward to another email account. I also keep a copy in the original account. The forward has been running fine for some time. I believe the system sends the mail first to the forwarded account and then puts... (0 Replies)
Discussion started by: BLabel
0 Replies
TERMINAL_COLORS.D(5)						 terminal-colors.d					      TERMINAL_COLORS.D(5)

NAME
terminal-colors.d - Configure output colorization for various utilities SYNOPSIS
/etc/terminal-colors.d/[[name][@term].][type] DESCRIPTION
Files in this directory determine the default behavior for utilities when coloring output. The name is a utility name. The name is optional and when none is specified then the file is used for all unspecified utilities. The term is a terminal identifier (the TERM environment variable). The terminal identifier is optional and when none is specified then the file is used for all unspecified terminals. The type is a file type. Supported file types are: disable Turns off output colorization for all compatible utilities. enable Turns on output colorization; any matching disable files are ignored. scheme Specifies colors used for output. The file format may be specific to the utility, the default format is described below. If there are more files that match for a utility, then the file with the more specific filename wins. For example, the filename "@xterm.scheme" has less priority than "dmesg@xterm.scheme". The lowest priority are those files without a utility name and terminal iden- tifier (e.g. "disable"). The user-specific $XDG_CONFIG_HOME/terminal-colors.d or $HOME/.config/terminal-colors.d overrides the global setting. EXAMPLES
Disable colors for all compatible utilities: touch /etc/terminal-colors.d/disable Disable colors for all compatible utils on a vt100 terminal: touch /etc/terminal-colors.d/@vt100.disable Disable colors for all compatible utils except dmesg(1): touch /etc/terminal-colors.d/disable touch /etc/terminal-colors.d/dmesg.enable DEFAULT SCHEME FILES FORMAT
The following statement is recognized: name color-sequence The name is a logical name of color sequence (for example "error"). The names are specific to the utilities. For more details always see the COLORS section in the man page for the utility. The color-sequence is a color name, ASCII color sequences or escape sequences. Color names black, blink, blue, bold, brown, cyan, darkgray, gray, green, halfbright, lightblue, lightcyan, lightgray, lightgreen, lightmagenta, lightred, magenta, red, reset, reverse, and yellow. ANSI color sequences The color sequences are composed of sequences of numbers separated by semicolons. The most common codes are: 0 to restore default color 1 for brighter colors 4 for underlined text 5 for flashing text 30 for black foreground 31 for red foreground 32 for green foreground 33 for yellow (or brown) foreground 34 for blue foreground 35 for purple foreground 36 for cyan foreground 37 for white (or gray) foreground 40 for black background 41 for red background 42 for green background 43 for yellow (or brown) background 44 for blue background 45 for purple background 46 for cyan background 47 for white (or gray) background Escape sequences To specify control or blank characters in the color sequences, C-style -escaped notation can be used: a Bell (ASCII 7)  Backspace (ASCII 8) e Escape (ASCII 27) f Form feed (ASCII 12) Newline (ASCII 10) Carriage Return (ASCII 13) Tab (ASCII 9) v Vertical Tab (ASCII 11) ? Delete (ASCII 127) \_ Space \ Backslash () ^ Caret (^) # Hash mark (#) Please note that escapes are necessary to enter a space, backslash, caret, or any control character anywhere in the string, as well as a hash mark as the first character. For example, to use a red background for alert messages in the output of dmesg(1), use: echo 'alert 37;41' >> /etc/terminal-colors.d/dmesg.scheme Comments Lines where the first non-blank character is a # (hash) are ignored. Any other use of the hash character is not interpreted as introducing a comment. FILES
$XDG_CONFIG_HOME/terminal-colors.d $HOME/.config/terminal-colors.d /etc/terminal-colors.d ENVIRONMENT
TERMINAL_COLORS_DEBUG=all enables debug output. COMPATIBILITY
The terminal-colors.d functionality is currently supported by all util-linux utilities which provides colorized output. For more details always see the COLORS section in the man page for the utility. AVAILABILITY
terminal-colors.d is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils /util-linux/>. util-linux January 2014 TERMINAL_COLORS.D(5)
All times are GMT -4. The time now is 08:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy