Sponsored Content
Full Discussion: Tilde commands not working
Operating Systems Solaris Tilde commands not working Post 302994164 by drysdalk on Monday 20th of March 2017 04:49:27 AM
Old 03-20-2017
Hi,

Assuming that flag is supported in your implementation of mailx, I'm almost certain it should be -b rather than ~b. Certainly I just checked the Solaris man page for mailx, and it lists the BCC flag as being -b. I've never, ever heard of any command taking flags with a tilde rather than a dash. You should also probably put it before the recipient's address, and not after.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

differnce between working of at and crontab commands

h I would like to know the differnce (both working and how) between at command and crontab.. Thanks in advance Satish D (2 Replies)
Discussion started by: doddas
2 Replies

2. Shell Programming and Scripting

How to get shell commands working through ruby?

Hi all, I am a newbie currently trying to execute shell commands from ruby instead of a shell script.(This method is conceived only for solaris so no issues with porting to other OS and all) Eg: Consider the command 'ls" with a shell script ,I would use it like this bash# ls <all the... (4 Replies)
Discussion started by: wrapster
4 Replies

3. UNIX for Advanced & Expert Users

commands after .profile modification not working

Hi , I have modified .profile and after that i ran it as .profile. Now no command i working even ls is not working When i type ls , it is showing that -ksh not found I tried to run as . $home/.profile , it is saying as permission denied . How can we do that .. any idea.. Thanks... (2 Replies)
Discussion started by: arunkumar_mca
2 Replies

4. UNIX for Advanced & Expert Users

commands not working if the executed from forked process

Hi, I have an application where if it runs indivisually could able to execute commands (like system("ls")) and could able to execute tcl script. Same application if started from health monitor process (From health monitor process my application will be forked), it could not execute the... (1 Reply)
Discussion started by: chandrutiptur
1 Replies

5. Fedora

wall and write commands are not working

hi friends i am using fedora linux operating system on the server and two clients(with windows os) are connected to it(server ).but here wall and write cmds are not working to send messages from one system to another system . pls help me (4 Replies)
Discussion started by: sankar_vitam
4 Replies

6. Shell Programming and Scripting

Commands not working in script file

Hi All, I have created a shell script having some general copying and moving commands. Commands are working fine in Shell but while executing the shell script it is showing an error mv: cannot stat `/apps/orarpt/in/*': No such file or directory command is mv $IN_DIR* $ARCHIVE_DIR where... (5 Replies)
Discussion started by: maindola.amit
5 Replies

7. Shell Programming and Scripting

SED sub commands in KSH not working for me

I am using SED to edit a file (called file) the file contains the word "ERROR" and I want to use SED to: 1. Search for text "ERROR" If found, 2. Append new line with text "hoi" I tried: sed 's/ERROR/ a\hoi' file sed 's/ERROR/ a\ hoi' file I get all the time the error sed:... (7 Replies)
Discussion started by: Alex400
7 Replies

8. UNIX and Linux Applications

mplayer snapshot commands not working

About 8-12 months ago I wrote a script that pulled together several mplayer commands to perform various activities. One allowed me to press the s-key to take snapshots with my webcam. Useful for recording the sensors I build. Now it: vd=0 bash-4.1$ TV1="-tv... (2 Replies)
Discussion started by: slak0
2 Replies

9. Shell Programming and Scripting

Commands not working with ssh remote login

Hi Friends, I am unable to run our application commands on remote server using ssh (passwordless login enabled). But the same command running with telent perl script. please suggest. SSH: C:/bin>ssh -l monitor tl04cp01 exec "/home/monitor/123" /home/monitor/123: viewlog: not found. ... (7 Replies)
Discussion started by: suresh3566
7 Replies

10. Shell Programming and Scripting

Tilde expansion

(Using Bash 4.4) When I write something like dir="~/dox" ls $dir then I get the message that the directory '~/docs' does not exist. I understand that the tilde is not expanded at the time of the above assignment because of the quotes. But why is it not expanded at the time when the ls command is... (2 Replies)
Discussion started by: Ralph
2 Replies
mutt(1) 							   User Manuals 							   mutt(1)

NAME
mutt - The Mutt Mail User Agent SYNOPSIS
mutt [-nRyzZ] [-e cmd] [-F file] [-m type] [-f file] mutt [-nx] [-e cmd] [-F file] [-H file] [-i file] [-s subj] [-b addr] [-c addr] [-a file [...] --] addr|mailto_url [...] mutt [-nx] [-e cmd] [-F file] [-s subj] [-b addr] [-c addr] [-a file [...] --] addr|mailto_url [...] < message mutt [-n] [-e cmd] [-F file] -p mutt [-n] [-e cmd] [-F file] -A alias mutt [-n] [-e cmd] [-F file] -Q query mutt -v[v] mutt -D DESCRIPTION
Mutt is a small but very powerful text based program for reading and sending electronic mail under unix operating systems, including sup- port for color terminals, MIME, OpenPGP, and a threaded sorting mode. Note: This manual page gives a brief overview of mutt's command line options. You should find a copy of the full manual in /usr/share/doc/mutt-1.5.21, in text, HTML, and/or PDF format. OPTIONS
-A alias An expanded version of the given alias is passed to stdout. -a file [...] Attach a file to your message using MIME. When attaching single or multiple files, separating filenames and recipient addresses with "--" is mandatory, e.g. mutt -a image.jpg -- addr1 or mutt -a img.jpg *.png -- addr1 addr2. The -a option must be placed at the end of command line options. -b address Specify a blind-carbon-copy (BCC) recipient -c address Specify a carbon-copy (CC) recipient -d level If mutt was complied with +DEBUG log debugging output to ~/.muttdebug0. Level can range from 1-5 and effects verbosity. A value of 2 is recommended. -D Print the value of all configuration options to stdout. -e command Specify a configuration command to be run after processing of initialization files. -f mailbox Specify which mailbox to load. -F muttrc Specify an initialization file to read instead of ~/.muttrc -h Display help. -H draft Specify a draft file which contains header and body to use to send a message. -i include Specify a file to include into the body of a message. -m type specify a default mailbox type for newly created folders. -n Causes Mutt to bypass the system configuration file. -p Resume a postponed message. -Q query Query a configuration variables value. The query is executed after all configuration files have been parsed, and any commands given on the command line have been executed. -R Open a mailbox in read-only mode. -s subject Specify the subject of the message. -v Display the Mutt version number and compile-time definitions. -vv Display license and copyright information. -x Emulate the mailx compose mode. -y Start Mutt with a listing of all mailboxes specified by the mailboxes command. -z When used with -f, causes Mutt not to start if there are no messages in the mailbox. -Z Causes Mutt to open the first mailbox specified by the mailboxes command which contains new mail. -- Treat remaining arguments as addr even if they start with a dash. See also "-a" above. ENVIRONMENT
EDITOR Specifies the editor to use if VISUAL is unset. EMAIL The user's e-mail address. HOME Full path of the user's home directory. MAIL Full path of the user's spool mailbox. MAILDIR Full path of the user's spool mailbox if MAIL is unset. Commonly used when the spool mailbox is a maildir (5) folder. MAILCAPS Path to search for mailcap files. MM_NOASK If this variable is set, mailcap are always used without prompting first. PGPPATH Directory in which the user's PGP public keyring can be found. TMPDIR Directory in which temporary files are created. REPLYTO Default Reply-To address. VISUAL Specifies the editor to use when composing messages. FILES
~/.muttrc or ~/.mutt/muttrc User configuration file. /etc/Muttrc System-wide configuration file. /tmp/muttXXXXXX Temporary files created by Mutt. ~/.mailcap User definition for handling non-text MIME types. /etc/mailcap System definition for handling non-text MIME types. ~/.mime.types User's personal mapping between MIME types and file extensions. /etc/mime.types System mapping between MIME types and file extensions. /usr/bin/mutt_dotlock The privileged dotlocking program. /usr/share/doc/mutt-1.5.21/manual.txt The Mutt manual. BUGS
None. Mutts have fleas, not bugs. FLEAS
Suspend/resume while editing a file with an external editor does not work under SunOS 4.x if you use the curses lib in /usr/5lib. It does work with the S-Lang library, however. Resizing the screen while using an external pager causes Mutt to go haywire on some systems. Suspend/resume does not work under Ultrix. The help line for the index menu is not updated if you change the bindings for one of the functions listed while Mutt is running. For a more up-to-date list of bugs, errm, fleas, please visit the mutt project's bug tracking system under http://bugs.mutt.org/. NO WARRANTIES
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. SEE ALSO
curses(3), mailcap(5), maildir(5), mbox(5), mutt_dotlock(1), muttrc(5), ncurses(3), sendmail(1), smail(1). Mutt Home Page: http://www.mutt.org/ The Mutt manual AUTHOR
Michael Elkins, and others. Use <mutt-dev@mutt.org> to contact the developers. Unix January 2009 mutt(1)
All times are GMT -4. The time now is 05:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy