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)
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)
hello friends,
i wud like to get some suggestion for a Q i faced in an interview..........
the Q is...........
suppose a person is working on vi .the file is very large and he hasn't saved anything ........suddenly power goes off and system shuts down ...after power comes up the system is... (4 Replies)
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
LEARN ABOUT DEBIAN
coro::select
Select(3pm) User Contributed Perl Documentation Select(3pm)NAME
Coro::Select - a (slow but coro-aware) replacement for CORE::select
SYNOPSIS
use Coro::Select; # replace select globally (be careful, see below)
use Core::Select 'select'; # only in this module
use Coro::Select (); # use Coro::Select::select
DESCRIPTION
This module tries to create a fully working replacement for perl's "select" built-in, using "AnyEvent" watchers to do the job, so other
threads can run in parallel to any select user. As many libraries that only have a blocking API do not use global variables and often use
select (or IO::Select), this effectively makes most such libraries "somewhat" non-blocking w.r.t. other threads.
This implementation works fastest when only very few bits are set in the fd set(s).
To be effective globally, this module must be "use"'d before any other module that uses "select", so it should generally be the first
module "use"'d in the main program. Note that overriding "select" globally might actually cause problems, as some "AnyEvent" backends use
"select" themselves, and asking AnyEvent to use Coro::Select, which in turn asks AnyEvent will not quite work.
You can also invoke it from the commandline as "perl -MCoro::Select".
To override select only for a single module (e.g. "Net::DBus::Reactor"), use a code fragment like this to load it:
{
package Net::DBus::Reactor;
use Coro::Select qw(select);
use Net::DBus::Reactor;
}
Some modules (notably POE::Loop::Select) directly call "CORE::select". For these modules, we need to patch the opcode table by sandwiching
it between calls to "Coro::Select::patch_pp_sselect" and "Coro::Select::unpatch_pp_sselect":
BEGIN {
use Coro::Select ();
Coro::Select::patch_pp_sselect;
require evil_poe_module_using_CORE::SELECT;
Coro::Select::unpatch_pp_sselect;
}
BUGS
For performance reasons, Coro::Select's select function might not properly detect bad file descriptors (but relying on EBADF is inherently
non-portable).
SEE ALSO
Coro::LWP.
AUTHOR
Marc Lehmann <schmorp@schmorp.de>
http://home.schmorp.de/
perl v5.14.2 2012-04-13 Select(3pm)