Alien-wxWidgets
view release on metacpan or search on metacpan
inc/bin/patch view on Meta::CPAN
a B<-o> switch; if that file already exists, it is backed up
first.
If I<patchfile> is omitted, or is a hyphen, the patch will be
read from standard input.
Upon startup, patch will attempt to determine the type of
the diff listing, unless over-ruled by a B<-c>, B<-e>, B<-n>, or B<-u>
switch. Context diffs [see L<"note 2">], unified diffs,
and normal diffs are applied by the I<patch> program itself,
while ed diffs are simply fed to the I<ed> editor via a pipe [see L<"note 3">].
I<Patch> will try to skip any leading garbage, apply the
diff, and then skip any trailing garbage. Thus you could
feed an article or message containing a diff listing to
I<patch>, and it should work. If the entire diff is indented
by a consistent amount, this will be taken into account.
With context diffs, and to a lesser extent with normal
diffs, I<patch> can detect when the line numbers mentioned in
the patch are incorrect, and will attempt to find the
inc/bin/patch view on Meta::CPAN
As each hunk is completed, you will be told whether the
hunk succeeded or failed, and which line (in the new file)
I<patch> thought the hunk should go on. If this is different
from the line number specified in the diff you will be
told the offset. A single large offset MAY be an indication that a hunk was installed in the wrong place. You
will also be told if a fuzz factor was used to make the
match, in which case you should also be slightly suspicious.
If no original file is specified on the command line,
I<patch> will try to figure out from the leading garbage what
the name of the file to edit is. In the header of a context diff, the filename is found from lines beginning with
"***" or "---", with the shortest name of an existing file
winning. Only context diffs have lines like that, but if
there is an "Index:" line in the leading garbage, I<patch>
will try to use the filename from that line. The context
diff header takes precedence over an Index line. If no
filename can be intuited from the leading garbage, you
will be asked for the name of the file to patch.
No attempt is made to look up SCCS or RCS files [see L<"note 6">].
inc/inc_Module-Load/Module/Load.pm view on Meta::CPAN
return $file;
}
sub _who { (caller(1))[0] }
sub _is_file {
local $_ = shift;
return /^\./ ? 1 :
/[^\w:']/ ? 1 :
undef
#' silly bbedit..
}
1;
__END__
=pod
=head1 NAME
patches/wxMSW-2.8.0-setup.patch view on Meta::CPAN
// Define this to use wxURL class.
#define wxUSE_URL 1
@@ -990,7 +990,7 @@
// Default is 0.
//
// Recommended setting: 1 if you intend to use OpenGL, 0 otherwise
-#define wxUSE_GLCANVAS 0
+#define wxUSE_GLCANVAS 1
// wxRichTextCtrl allows editing of styled text.
//
@@ -1051,7 +1051,7 @@
#define wxUSE_DRAGIMAGE 1
-#define wxUSE_IPC 1
+#define wxUSE_IPC 1
// 0 for no interprocess comms
#define wxUSE_HELP 1
// 0 for no help facility
patches/wxMSW-2.8.0-setup_u.patch view on Meta::CPAN
// Define this to use wxURL class.
#define wxUSE_URL 1
@@ -990,7 +990,7 @@
// Default is 0.
//
// Recommended setting: 1 if you intend to use OpenGL, 0 otherwise
-#define wxUSE_GLCANVAS 0
+#define wxUSE_GLCANVAS 1
// wxRichTextCtrl allows editing of styled text.
//
@@ -1051,7 +1051,7 @@
#define wxUSE_DRAGIMAGE 1
-#define wxUSE_IPC 1
+#define wxUSE_IPC 1
// 0 for no interprocess comms
#define wxUSE_HELP 1
// 0 for no help facility
patches/wxMSW-2.9.0-setup.patch view on Meta::CPAN
// Define this to use wxURL class.
#define wxUSE_URL 1
@@ -1098,7 +1098,7 @@
// Default is 0.
//
// Recommended setting: 1 if you intend to use OpenGL, 0 otherwise
-#define wxUSE_GLCANVAS 0
+#define wxUSE_GLCANVAS 1
// wxRichTextCtrl allows editing of styled text.
//
@@ -1159,7 +1159,7 @@
#define wxUSE_DRAGIMAGE 1
-#define wxUSE_IPC 1
+#define wxUSE_IPC 1
// 0 for no interprocess comms
#define wxUSE_HELP 1
// 0 for no help facility
( run in 0.488 second using v1.01-cache-2.11-cpan-de7293f3b23 )