pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Incorect path
2+ messages / 2 participants
[nested] [flat]

* Incorect path
@ 2019-02-11 15:19 PG Doc comments form <noreply@postgresql.org>
  2019-02-11 15:50 ` Re: Incorect path David G. Johnston <david.g.johnston@gmail.com>
  0 siblings, 1 reply; 2+ messages in thread

From: PG Doc comments form @ 2019-02-11 15:19 UTC (permalink / raw)
  To: pgsql-docs@lists.postgresql.org; +Cc: sasa.s.v.stankovic@gmail.com

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/9.4/tutorial-sql-intro.html
Description:

At https://www.postgresql.org/docs/9.4/tutorial-sql-intro.html it is
written:
$ cd ..../src/tutorial
$ make
---
$ cd ..../tutorial
$ psql -s mydb

The four dots are not valid, either remove two of them or replace all four
with proper path such as ../..


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Incorect path
  2019-02-11 15:19 Incorect path PG Doc comments form <noreply@postgresql.org>
@ 2019-02-11 15:50 ` David G. Johnston <david.g.johnston@gmail.com>
  0 siblings, 0 replies; 2+ messages in thread

From: David G. Johnston @ 2019-02-11 15:50 UTC (permalink / raw)
  To: sasa.s.v.stankovic@gmail.com; pgsql-docs@lists.postgresql.org

On Mon, Feb 11, 2019 at 8:25 AM PG Doc comments form
<noreply@postgresql.org> wrote:
> At https://www.postgresql.org/docs/9.4/tutorial-sql-intro.html it is
> written:
> $ cd ..../src/tutorial

> The four dots are not valid, either remove two of them or replace all four
> with proper path such as ../..

Your solutions are equally invalid even if they can be executed -
likely with a different error than what you are seeing now.

The current command is symbolic in nature since where in the local
filesystem tree src/tutorial exists is unknown.

If this is "fixed" at all, so that it is a valid and useful command,
the change would be to simply make src/tutorial a relative path:

cd src/tutorial

I personally find no confusion with the existing code, which points
out that the where you cd to requires being in the right initial
location, but would accept a purely relative path.

I would not accept randomly adding relative ancestor navigation since
the only reason it is being suggested is due to misunderstanding the
intent of the original.

David J.




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2019-02-11 15:50 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-02-11 15:19 Incorect path PG Doc comments form <noreply@postgresql.org>
2019-02-11 15:50 ` David G. Johnston <david.g.johnston@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox