Home
last modified time | relevance | path

Searched refs:pathnames (Results 1 – 25 of 87) sorted by relevance

1234

/openbsd/gnu/usr.bin/cvs/doc/
H A Dcvsclient.aux46 'xrdef {Response pathnames-title}{The "pathname" in responses}
47 'xrdef {Response pathnames-pg}{23}
48 'xrdef {Response pathnames-snt}{Section'tie5.10}
H A Dcvsclient.info32 Node: Response pathnames62340
H A Dcvsclient.info-275 be another response instead. Note that it returns two pathnames.
786 File: cvsclient.info, Node: Response intro, Next: Response pathnames, Prev: Requests, Up: Proto…
813 File: cvsclient.info, Node: Response pathnames, Next: Responses, Prev: Response intro, Up: Prot…
819 is somewhat misleading; it actually indicates a pair of pathnames.
H A Dcvsclient.info-310 File: cvsclient.info, Node: Responses, Next: Text tags, Prev: Response pathnames, Up: Protocol
215 module. PATHNAME is relative to cvsroot, unlike most pathnames in
/openbsd/gnu/usr.bin/perl/
H A DREADME.vos81 pathnames over OpenVOS-style greater-than-separated pathnames.
82 OpenVOS-style pathnames should work in most contexts, but if you have
85 cannot process OpenVOS pathnames containing a slash character in a
H A DREADME.cygwin48 The only dependencies come from hard-coded pathnames like F</usr/local>.
304 Cygwin pathnames are separated by forward (F</>) slashes, Universal
306 pathnames should not be used. Names may contain all printable
311 subject to the translations applied to POSIX style pathnames, but
317 Since cygwin-1.7 pathnames are UTF-8 encoded.
/openbsd/usr.sbin/config/
H A Dgram.y110 %type <list> pathnames
169 pathnames:
171 pathnames '|' PATHNAME { ($$ = $1)->nv_next = new_nsi($3, NULL, 0); };
177 XFILE pathnames fopts fflgs rule { addfile($2, $3, $4, $5); };
/openbsd/gnu/usr.bin/perl/t/op/
H A Dpwent.t18 my ($where, $args, @pathnames) = @_;
19 foreach my $prog (@pathnames) {
/openbsd/gnu/usr.bin/cvs/vms/
H A DMakefile.am36 pathnames.h \
H A DMakefile.in122 pathnames.h \
/openbsd/gnu/usr.sbin/mkhybrid/src/
H A Dmkisofs.c783 char *pathnames = 0; in FDECL2() local
1130 pathnames = optarg; in FDECL2()
1327 if (pathnames) { in FDECL2()
1329 if (strcmp(pathnames, "-")) { in FDECL2()
1330 if ((pfp = fopen(pathnames, "r")) == NULL) { in FDECL2()
1331 fprintf(stderr, "unable to open pathname list %s\n",pathnames); in FDECL2()
/openbsd/gnu/usr.bin/binutils/ld/
H A Dmpw-make.sed32 # Fix pathnames to generated files.
57 # Edit pathnames to emulation files.
/openbsd/gnu/usr.bin/binutils/opcodes/
H A Dmpw-make.sed6 # Fix pathnames to include directories.
/openbsd/gnu/usr.bin/binutils/gdb/nlm/
H A Dconfigure.in35 dnl arbitrary data or pathnames.
/openbsd/gnu/usr.bin/binutils/bfd/
H A Dmpw-make.sed7 # Fix pathnames to include directories.
/openbsd/usr.bin/vi/docs/USD.doc/vi.ref/
H A Dspell.ok248 pathnames
/openbsd/gnu/llvm/llvm/docs/CommandGuide/
H A Dllvm-config.rst105 without **-l** or pathnames. Useful for linking against a not-yet-installed
/openbsd/gnu/usr.bin/perl/cpan/Pod-Simple/t/
H A Dperlcygo.txt16 … ntsec, binary/text mounts). The only dependencies come from hard-coded pathnames like /usr/local.…
161 Cygwin pathnames can be separated by forward (/) or backward (\) slashes. They may also begin with …
163 … letter is a Win32 pathname (and not subject to the translations applied to POSIX style pathnames).
H A Dperlcyg.pod53 The only dependencies come from hard-coded pathnames like C</usr/local>.
414 Cygwin pathnames can be separated by forward (F</>) or backward (F<\>)
425 to the translations applied to POSIX style pathnames).
/openbsd/gnu/lib/libreadline/
H A DCHANGELOG355 - changed symlinks to relative pathnames on all platforms
417 - rlfe can perform filename completion for relative pathnames in the
/openbsd/gnu/usr.bin/gcc/gcc/doc/
H A Dhostconfig.texi66 behaves like Unix (only forward slash separates pathnames), define
/openbsd/usr.bin/vi/docs/interp/
H A Dinterp160 11: Functions to return pathnames.
/openbsd/gnu/usr.bin/perl/cpan/Archive-Tar/t/
H A D04_resolved_issues.t256 ### retain leading '/' for absolute pathnames.
/openbsd/gnu/usr.bin/cvs/src/
H A Doptions.h.in93 * so if you have other software which relies on absolute pathnames,
/openbsd/gnu/usr.bin/cvs/
H A DFAQ1160 names) instead of merely aliases for relative pathnames.
1184 The & references say to interpret those pathnames relative to the
1284 pathnames), then they are in the same Repository.
1290 pathnames in the ./CVS/Repository file, since most commands (other
1293 If you configure CVS to use relative pathnames in your
1649 You should either reconfigure CVS to use absolute pathnames to the
2000 against pathnames within the Repository and
2002 a <command> to execute for matching pathnames.
2188 large list of relative pathnames.
2545 relative pathnames, you don't have to do anything else.
[all …]

1234