08-27-2017
Hi.
A Google search for
man xed turned up many hits, among them:
Linux Manpages Online - man.cx manual pages)
which produces:
Quote:
NAME
xed − text editor for X
SYNOPSIS
xed [-s] [-p string] [-nb] [-P] [-ttymode] [-fn font]
[-x N] [-nsb] [-help] [-version] [file]
DESCRIPTION
Xed is the standard text editor, conveniently re-written for use in the standard windowing system.
Xed is a completely backward-compatible implementation of the ed line-oriented text editor. See the ed(1) manual page for a description of the basic ed syntax and command set; what follows is a description of the features unique to xed.
OPTIONS
-s
Suppresses diagnostics.
−p string
Specifies a command prompt. This may be toggled on and off with the ’P’ command.
-nb
Turns off automatic file backup. By default, xed will back up a file to filename before writing to that file.
...
Google and
man are your friends ... cheers, drl
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I have been using the hostdump.sh backup script for over a year now and have recently run into a problem. I'm now getting the following error at the end of my jobs;
/bin/mt -f: error fsf'ing tape.
This script uses the native 'ufsdump'. So, I try to go back and read the last dump on the tape... (11 Replies)
Discussion started by: Solaris
11 Replies
2. UNIX for Dummies Questions & Answers
When using hostdump.sh to backup a system I can do it fine. But how can I restore what I backuped up?
:)
Thx in advance (2 Replies)
Discussion started by: merlin
2 Replies
3. UNIX for Dummies Questions & Answers
Hello everyone my ? is about backups. I'am running SCO OS 505 and currently backing up the hole HD. Well the back up is taking too long and this is becoming a problem for the users since we are a 24-7 bussines, I whant stop backing up every thing on the HD. What are the most important files and... (1 Reply)
Discussion started by: kikkin
1 Replies
4. UNIX Desktop Questions & Answers
I've been handed the task of backing up some of our system files on a Solaris box. No probs. Zipped the logs that needed backing up but my superiors do not want it on tape, they want it spanned on CD's. The CD-Writer is available on a MS box. FTP'd the zipped logs across too the MS Machine but now... (1 Reply)
Discussion started by: mccrack_2003
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
6. Shell Programming and Scripting
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Discussion started by: aarora_98
6 Replies
7. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
8. Shell Programming and Scripting
Hello all,
I'm using nas4free as a SAN and am having troubles getting a backup of it's data to work properly. I've posted in the nas4free forums, but haven't received much help.
Here is the code I'm using:
#!/bin/sh
{... (1 Reply)
Discussion started by: dpatino
1 Replies
9. UNIX for Advanced & Expert Users
Hi Experts,
Need your support
Redhat 6.5
I want to create a user with all(read, write, execute) privileges except that user should not be able to create any new user from his login
to perform any task. (10 Replies)
Discussion started by: as7951
10 Replies
LEARN ABOUT DEBIAN
resourceeditor
resourceEditor(1) PythonCard Developers resourceEditor(1)
NAME
resourceEditor - Resource editor used as part of the PythonCard GUI framework
SYNOPSIS
resourceEditor [file] [switches]
DESCRIPTION
The resourceEditor is the most common starting point for constructing a PythonCard application. Using this tool, you can create, position,
size, describe and connect not only your application's windows and all of the components they contain (buttons, fields, and other con-
trols), but also its menus and supporting dialogs. A direct-manipulation interface enables you to create, drag, and size window components
in the grand tradition of Integrated Development Environments (IDEs). The resourceEditor also incorporates a menu editor and a background
editor for managing the non-component portions of your PythonCard application.
Scripting is not integrated into the resourceEditor. Instead, you should use your favorite Python script editor to write the code that
gives your application its intelligence and behavior (for instance, you could use codeEditor(1), also part of the PythonCard GUI frame-
work).
SWITCHES
Note that switches must come after any filename in order to be recognized.
-p Show property editor
-m Show message watcher
-l Enable logging
-s Show shell
-m Show namespace
-d Show debug menu
NOTES
The resourceEditor utility also provides additional functionality that is not discussed in this manpage, because it is somewhat difficult
to completely describe usage of a GUI program in a text-based manpage. For more detailed usage instructions or for more information on the
PythonCard GUI framework in general, you should install the pythoncard-doc package and take a look at the various walk-throughs, tutorials
and samples included with it.
Once the pythoncard-doc package is installed, the documentation is installed to /usr/share/doc/pythoncard-doc, and is also available via
Debian's doc-base infrastructure - find it in the Devel section using dwww(1), doc-central(1) or dhelp(1).
If you would rather not install the pythoncard-doc package, you can find essentially the same information on the PythonCard website:
http://pythoncard.sourceforge.net
BUGS
Although it is considered to be stable, this is still development-level software.
Please report bugs in this or any PythonCard component to the Debian Bug Tracking system using reportbug(1).
AUTHOR
This manpage was written by Kenneth J. Pronovici <pronovic@debian.org>, for use by the Debian project. Content was based on previously-
existing PythonCard documentation in other forms.
SEE ALSO
codeEditor(1), findfiles(1),
PythonCard GUI Framework August 2003 resourceEditor(1)