Sponsored Content
Full Discussion: paste in x11 xterm
Operating Systems OS X (Apple) paste in x11 xterm Post 302275451 by tau on Saturday 10th of January 2009 02:07:46 PM
Old 01-10-2009
Thanks but didn't work.

Tom
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

X11 and its problems.....

I was running X11 through Terminal by "xinit" and I got the error: XFree86 Version 4.3.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already... (4 Replies)
Discussion started by: gnerd
4 Replies

2. OS X (Apple)

x11

Tried to install x11 on my powerbook with tiger (apple support can't help me) I want x11 so I can install open office I don't know anything about mac ' (3 Replies)
Discussion started by: Josiah Olson
3 Replies

3. Windows & DOS: Issues & Discussions

cygwin-x/can't install xorg-x11-f100 & xorg-x11-fnts

Hello All. Really a newbie to Linux/Unix. Trying to get into Linux. Using XP PE currently. Installed cygwin and trying to intall cygwin-x. Everything else is setup nice but i can't seem to install these two packages (without whom xwin won't start) 1. xorg-x11-f100 2. xorg-x11-fnts Tried the... (1 Reply)
Discussion started by: binodbdrchand
1 Replies

4. Solaris

X11 Display

Hi all, How to setup X11 on Solaris? ~Vinodh' Kumar (1 Reply)
Discussion started by: vino_hymi
1 Replies

5. UNIX for Advanced & Expert Users

Xterm configuration : how to copy/paste in the CLIPBOARD

Hi, I can paste what is in the CLIPBOARD but I can't get xterm copy. and in fact I think I'm not able to select well with the cursor (I don't want to use the mouse)... here is my ~/.Xresources file : XTerm*highlightSelection: true XTerm*VT100.translations: #override \n\ None ... (5 Replies)
Discussion started by: xib.be
5 Replies

6. UNIX for Dummies Questions & Answers

X11 privileges

Hi What privileges I need to install X11? Or, in other words, can I install X11 without root privileges? The only user that installed X11 will use it. If it depends on OS version, here is the list of operating systems: Linux Red Hat Enterprise AS/ES 4.0/4.5/5 ... (1 Reply)
Discussion started by: lleontiev
1 Replies

7. Solaris

libgtk-x11-2.0.so.0

I have the lib libgtk-x11-2.0.so.0 in /usr/local/lib, but I still get an error as below, please help. ld.so.1: firefox-bin: fatal: libgtk-x11-2.0.so.0: open failed: No such file or directory (2 Replies)
Discussion started by: keekee
2 Replies

8. UNIX for Advanced & Expert Users

[Solved] putty+x11:How do I pass X11 display rights to "su"?

I can log into a unix system with Putty. I've set the "X11 forwarding" checkbox, and I've verified that I can display an X11 window back on my laptop. What I need to be able to do is "su" to another uid after logging in and then run something which display a window back on my laptop, with the... (2 Replies)
Discussion started by: dkarr
2 Replies

9. Solaris

Solaris11.4 - no X11

After some problems, I have installed Solaris 11.4. The warnings saidWARNING: /pci@0,0/..... (xhci1): Connecting device on port 5 failed WARNING: /pci@0,0/..... (xhci1): Connecting device on port 6 failed Preparing image for use Unable to mount media Requesting System Maintenance Mode (See... (4 Replies)
Discussion started by: kebabbert
4 Replies
Pod::PlainText(3pm)					 Perl Programmers Reference Guide				       Pod::PlainText(3pm)

NAME
Pod::PlainText - Convert POD data to formatted ASCII text SYNOPSIS
use Pod::PlainText; my $parser = Pod::PlainText->new (sentence => 0, width => 78); # Read POD from STDIN and write to STDOUT. $parser->parse_from_filehandle; # Read POD from file.pod and write to file.txt. $parser->parse_from_file ('file.pod', 'file.txt'); DESCRIPTION
Pod::PlainText is a module that can convert documentation in the POD format (the preferred language for documenting Perl) into formatted ASCII. It uses no special formatting controls or codes whatsoever, and its output is therefore suitable for nearly any device. As a derived class from Pod::Parser, Pod::PlainText supports the same methods and interfaces. See Pod::Parser for all the details; briefly, one creates a new parser with "Pod::PlainText->new()" and then calls either parse_from_filehandle() or parse_from_file(). new() can take options, in the form of key/value pairs, that control the behavior of the parser. The currently recognized options are: alt If set to a true value, selects an alternate output format that, among other things, uses a different heading style and marks "=item" entries with a colon in the left margin. Defaults to false. indent The number of spaces to indent regular text, and the default indentation for "=over" blocks. Defaults to 4. loose If set to a true value, a blank line is printed after a "=headN" headings. If set to false (the default), no blank line is printed after "=headN". This is the default because it's the expected formatting for manual pages; if you're formatting arbitrary text documents, setting this to true may result in more pleasing output. sentence If set to a true value, Pod::PlainText will assume that each sentence ends in two spaces, and will try to preserve that spacing. If set to false, all consecutive whitespace in non-verbatim paragraphs is compressed into a single space. Defaults to true. width The column at which to wrap text on the right-hand side. Defaults to 76. The standard Pod::Parser method parse_from_filehandle() takes up to two arguments, the first being the file handle to read POD from and the second being the file handle to write the formatted output to. The first defaults to STDIN if not given, and the second defaults to STDOUT. The method parse_from_file() is almost identical, except that its two arguments are the input and output disk files instead. See Pod::Parser for the specific details. DIAGNOSTICS
Bizarre space in item (W) Something has gone wrong in internal "=item" processing. This message indicates a bug in Pod::PlainText; you should never see it. Can't open %s for reading: %s (F) Pod::PlainText was invoked via the compatibility mode pod2text() interface and the input file it was given could not be opened. Unknown escape: %s (W) The POD source contained an "E<>" escape that Pod::PlainText didn't know about. Unknown sequence: %s (W) The POD source contained a non-standard internal sequence (something of the form "X<>") that Pod::PlainText didn't know about. Unmatched =back (W) Pod::PlainText encountered a "=back" command that didn't correspond to an "=over" command. RESTRICTIONS
Embedded Ctrl-As (octal 001) in the input will be mapped to spaces on output, due to an internal implementation detail. NOTES
This is a replacement for an earlier Pod::Text module written by Tom Christiansen. It has a revamped interface, since it now uses Pod::Parser, but an interface roughly compatible with the old Pod::Text::pod2text() function is still available. Please change to the new calling convention, though. The original Pod::Text contained code to do formatting via termcap sequences, although it wasn't turned on by default and it was problematic to get it to work at all. This rewrite doesn't even try to do that, but a subclass of it does. Look for Pod::Text::Termcap. SEE ALSO
Pod::PlainText is part of the Pod::Parser distribution. Pod::Parser, Pod::Text::Termcap, pod2text(1) AUTHOR
Please report bugs using <http://rt.cpan.org>. Russ Allbery <rra@stanford.edu>, based very heavily on the original Pod::Text by Tom Christiansen <tchrist@mox.perl.com> and its conversion to Pod::Parser by Brad Appleton <bradapp@enteract.com>. perl v5.18.2 2013-11-04 Pod::PlainText(3pm)
All times are GMT -4. The time now is 08:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy