Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xtell(1) [debian man page]

XTELL(1)						      General Commands Manual							  XTELL(1)

NAME

       xtell - sends a message to another computer running xtelld

SYNOPSIS

       xtell [-v] [user[:tty][@host[:port]]] [message]

       write  user [tty]

DESCRIPTION

       How to use it: suppose you want to send a message to user gubas on computer trener.fsport.uniba.sk Just type:

       prompt:~% xtell gubas@trener.fsport.uniba.sk Hi

       To send multiple lines long message to user 7tokarova at computer pascal.fmph.uniba.sk, type

	prompt:~% xtell 7tokarova@pascal.fmph.uniba.sk
	Hi
	How are you today
	Please answer
	^D

       in this case, finish sending messages with EOF (CTRL D)

       If you want to send message to user holik on local computer, you can do it either by typing:

	prompt:~% xtell holik@localhost Hi

       or simply:

	prompt:~% xtell holik Hi

       To send message to certain tty, append the tty to username, separated by colon:

	prompt:~% xtell stanys:ttyp2@reaktor.ip.fmph.uniba.sk 'Sveikas Tomai'

       will send message 'Sveikas Tomai' to user stanys on ttyp2 at computer reaktor.ip.fmph.uniba.sk

       To specify other port than the default 4224, append the port to computer name, separated by colon:

	prompt:~% xtell bosa@radon.dnp.fmph.uniba.sk:4000 'Ahoj'

       assumes the xtell daemon runs at computer radon on port 4000, and sends the message 'Ahoj' to user bosa.

       Option -v turns verbose mode on. Xtell will then display some messgaes about connecting, which is usefull especially when the connection is
       slow.

       Example:

	prompt:~% xtell -v rybar@dmpc.dbp.fmph.uniba.sk

       xtell invoked without parameters will ask user for username and host to send the message to.

       If the user has created in his/her/its home directory the file .xtell-log, and the file is writable by nobody, all messages will be written
       to this file as well as to the screen (handy when the screen is overwritten and you could not see the message).

       xtell checks the environmental variable XTELLPROMPT.  If it exists, it is used as prompt for messages.

       Last  notice:  if you do not think zsh is the best shell, (besides doing a mistake) replace prompt:~% in above text with prompt:~$ or what-
       ever :-)

AUTHOR

       Radovan Garabik (garabik@melkor.dnp.fmph.uniba.sk)

SEE ALSO

       xtelld(8), write(1), talk(1), talkd(8), tty(1)

BUGS

       What happens to .xtell-log when two messages arrive simultaneously? There is no locking implemented.

																	  XTELL(1)

Check Out this Related Man Page

YUDIT(1)							  LINUX COMMANDS							  YUDIT(1)

NAME

       yudit - Unicode Editor for The X Window System

SYNOPSIS

       yudit [ -e encoding ] [[ file-name [ file-name...  ]]

DESCRIPTION

       yudit is an unicode text editors.

       When a user runs yudit for the first time $HOME/.yudit, $HOME/.yudit/data, and $HOME/.yudit/fonts are created.

       The  configuration file can be edited inside yudit. For the detailed description of usage and configuration take a look at the on-line man-
       ual.

       If you are planning to save files with yudit please note that the format preferred by edit for unicode files is UTF8.

       yudit can convert between different encodings, but if you do not need a GUI consider uniconv.

ARGUMENTS

       -e encoding
	      The encoding determines how yudit interacts with character streams: file input, file output, cut and paste. XInput encoding  is  set
	      up to use an independent, fixed encoder.

	      If you received yudit through the yudit distribution, the following encodings are inclusively supported:

	      UTF8,  UTF7,  8859_1, 8859_2, 8859_5, 8859_7, 8859_9, KOI8_R, JIS, SJIS, EUC_JP, ISO2022_KR, EUC_KR, JOHAB, UHC, GB2312_7, GB2312_8,
	      HZ, BIG5, CTEXT_JA, 10646 JAVA.

	      For a detailed description of these please refer to uniconv man page.

       file-name
	      is the file yudit should read into its buffer at start-up.

ENVIRONMENT

       The environment variable HOME should point to the user's home directory, where the yudit configuration file (.yuditrc) is kept. If the file
       is corrupt yudit exits with an error dialog. Errors messages are usually replicated in the standard error output of the yudit.

SEE ALSO

	mytool, uniconv, uniprint

AUTHOR

       This  program   was  written by gsinai@iname.com (Gaspar Sinai), Tokyo, 10 November, 1997 (yutex) and was updated on 1 December 1997.  Many
       thanks to Andrew Weeks at University of Bath for releasing his TrueType to postscript (ttf2pfa) program which formed the base  of  printing
       support in yudit.

       This  manual  page  was copied from old yudit 1.6 distribution by Radovan Garabik <garabik@melkor.dnp.fmph.uniba.sk> and modified for yudit
       2.4 distribution for Debian/GNU system before being edited for yudit 2.8.  It may contain obsolete information.

LINUX COMMANDS
							    Nov 5 1997								  YUDIT(1)
Man Page