04-12-2004
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi,
i access unix through secure shell (SSH) from my pc running on windows. Can i save files from unix directly into windows-run pc?. e.g. vi files into notepad???
thanks alot,
-a (6 Replies)
Discussion started by: alikun
6 Replies
2. Shell Programming and Scripting
Apologies if this isn't quite the right thread
I have a vi session and I have set a lot of tags with 'mx'. can I save this session preserving these tags so when I go back to the session I don't have to reset them all?
cheers (0 Replies)
Discussion started by: ajcannon
0 Replies
3. Gentoo
Hi Guys,
I dont know if this is the right thread to post this but i didnt find a better category. I am planning to buy a new desktop and i would need your suggestions for that. The desktop will be mainly for
1) FPS and MMORPG gaming in Windows (Quake, UT and WOW)
2) Linux for programming... (3 Replies)
Discussion started by: s4g3
3 Replies
4. Shell Programming and Scripting
Hi everybody,
I have a prog who is filtering an image with a lot of parameters. The user has two choices :
-Running the script with default values
-Running the script manually (i.e choosing himself the parameters values)
What I would like to do is that if he wants, the users can keep... (4 Replies)
Discussion started by: Moumou
4 Replies
5. Red Hat
Hi all,
firstly apologies if this is in the wrong category.
I have been making livecds (fedora based) and to change eg the background i use below in the ks file.
this works fine, however when i install the livecd it loses the changes.
How can i make the changes so that they stay when... (5 Replies)
Discussion started by: davewilks
5 Replies
6. Shell Programming and Scripting
I am trying to do some changes at bashrc file located at /etc directory of my server. First I tried to edit bashrc via FTP downloaded on my pc changed it and loaded back, but it seems like changes are not reflecting.
Therefore I tried to change it via putty shel using vim bashrc command. but... (4 Replies)
Discussion started by: ninadgac
4 Replies
7. Shell Programming and Scripting
Hi all,
I need to save my files at c, d or any drive location via script.
Requirement.
Say for example i have 10 files at location /usr/bi/ci location.
10 files naming
a.ksh
b,ksh
c.ksh and so on
I want to save the files and its content at some location (any drive on local... (4 Replies)
Discussion started by: j_panky
4 Replies
8. Solaris
Greetings.
I am trying to save a file to a usb from solaris 10.
If I do rmformat, I see my usb, but can't find a location to tell things to save to or figure out how to save/view the files on the disk.
Any help/thoughts/etc would be appreciated.
Thanks!
~K (20 Replies)
Discussion started by: kuriosity_prime
20 Replies
9. Red Hat
Hi All ,
I want a Good Specification For Building a Coustum PC must Have With Intel Motherboard and Intel Processor , And Must Have Virtualization , Cos im Gonna Install Redhat Enterprise Virtualization Based PC and Gonna install win Xp , Win 7 as a Guest Os in it .. Any one Have Good Spec for... (2 Replies)
Discussion started by: babinlonston
2 Replies
10. AIX
There's no Vim in AIX (6 and 7), but Vi is natively available.
I want to save my configuration for Vi like `set nu` to number lines in files.
I couldn't find configuration related to Vi in /etc/ or /usr/etc/ folders.
Please help me with that. (4 Replies)
Discussion started by: Chinggis6
4 Replies
LEARN ABOUT HPUX
dtwsmgetworkspaceinfo
DtWsmGetWorkspaceInfo(library call) DtWsmGetWorkspaceInfo(library call)
NAME
DtWsmGetWorkspaceInfo -- get detailed workspace information
SYNOPSIS
#include <Dt/Wsm.h>
int DtWsmGetWorkspaceInfo(
Display *display,
Window root,
Atom aWorkspace,
DtWsmWorkspaceInfo **ppWsInfo);
DESCRIPTION
The DtWsmGetWorkspaceInfo function works with the CDE workspace manager, dtwm(1), and returns detailed information on a specific workspace.
The display argument is the X display.
The root argument is the root window of the screen of interest.
The aWorkspace argument is the workspace name (converted to an X atom).
The *ppWsInfo argument is the address of a variable to receive the returned pointer to the workspace information data.
The DtWsmWorkspaceInfo structure contains at least the following members:
Atom workspace The workspace name (con-
verted to an X atom).
unsigned long bg The pixel ID used for the
background color of the
backdrop.
unsigned long fg The pixel ID used for the
foreground color of the
backdrop.
Atom backdropName The backdrop file name
(converted to an X atom).
The file must be in either
X Bitmap file format (with
extension .bm) or X Pixmap
file format (with extension
.pm). The workspace man-
agement services look for
the file along the same
path used for searching
icons. The directory
/usr/dt/backdrops is the
default directory if the
file cannot be found along
the icon search path.
int colorSetId The colorset number used
for this workspace, which
affects the backdrop color
and the button color for
this workspace on the front
panel.
char *pchTitle The title displayed in the
button for this workspace
on the front panel. This
string is interpreted in
the locale in which the CDE
workspace manager, dtwm(1),
is running. The title is
different from the
workspace name. The
workspace name, when con-
verted from an X atom, is
used as the identifier for
a workspace in the
workspace manager function
calls. The CDE workspace
manager, dtwm(1). also uses
the workspace name as a
resource name; thus, the
characters used in a
workspace name are
restricted to the charac-
ters in the X Portable
Character Set. The
workspace name for a
workspace created from the
front panel is generated
automatically by the CDE
workspace manager, dtwm(1).
Window *backdropWindows A pointer to an array of
windows that make up the
backdrop.
int numBackdropWindows The number of elements in
the backdropWindows array.
RETURN VALUE
Upon successful completion, the DtWsmGetWorkspaceInfo function returns Success and the workspace manager returns in *ppWsInfo a pointer to
a DtWsmInfo structure that contains information about the workspace aWorkspace; otherwise, it returns a value not equal to Success.
APPLICATION USAGE
If the DtWsmGetWorkspaceInfo function is not successful, failure may be due to a memory allocation error or failure to find the correct
workspace information (that is, the CDE workspace manager, dtwm(1), is not running). The application must use the DtWsmFreeWorkspaceInfo(3)
function to free the data returned in *ppWsInfo. The *backdropWindows pointer may be useful for applications that are interested in some
events on the root window. Since the backdrop covers the root window, the backdrop catches the button events before they reach the root.
SEE ALSO
Dt/Wsm.h - DtWsm(5), dtwm(1), DtWsmGetWorkspaceList(3), DtWsmFreeWorkspaceInfo(3).
DtWsmGetWorkspaceInfo(library call)