![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Please enter a FULL description of your problem: ------------------------------------------------ When opening a file in psql, ~ (the user's home dir) is resolved when using tab completion to find the file, but when you hit enter and psql actualy tries to open it, you get a file not found error. |
#3
| |||
| |||
|
|
When opening a file in psql, ~ (the user's home dir) is resolved when using tab completion to find the file, but when you hit enter and psql actualy tries to open it, you get a file not found error. |
#4
| |||
| |||
|
|
Bas Scheffers writes: When opening a file in psql, ~ (the user's home dir) is resolved when using tab completion to find the file, but when you hit enter and psql actualy tries to open it, you get a file not found error. This is not a bug. If there is not file named ~ then it can't be opened. |
#5
| |||
| |||
|
|
Bas Scheffers writes: =20 When opening a file in psql, ~ (the user's home dir) is resolved when using tab completion to find the file, but when you hit enter and psql actualy tries to open it, you get a file not found error. =20 This is not a bug. If there is not file named ~ then it can't be opened. |
#6
| |||
| |||
|
|
This is not a bug. If there is not file named ~ then it can't be opened. I am not trying to open a file named ~, I am using it as part of a file |
#7
| |||
| |||
|
|
Peter Eisentraut wrote: Bas Scheffers writes: When opening a file in psql, ~ (the user's home dir) is resolved when using tab completion to find the file, but when you hit enter and psql actualy tries to open it, you get a file not found error. This is not a bug. If there is not file named ~ then it can't be opened. Sure looks like a bug to me. |
#8
| |||
| |||
|
|
This is not a bug. If there is not file named ~ then it can't be opened. I am not trying to open a file named ~, I am using it as part of a file name, ie: ~/ewap/sql/ewap.sql. (where ~=/home/bas) This is perfectly valid on any unix system and especialy since tab completion of \i supports it, so should the function that does the actual opening of the file, I would think... |
#9
| |||
| |||
|
|
Bruce Momjian <pgman (AT) candle (DOT) pha.pa.us> writes: Peter Eisentraut wrote: Bas Scheffers writes: When opening a file in psql, ~ (the user's home dir) is resolved when using tab completion to find the file, but when you hit enter and psql actualy tries to open it, you get a file not found error. This is not a bug. If there is not file named ~ then it can't be opened. Sure looks like a bug to me. I think so too. If tab completion can find the file then we ought to be willing to open it. Changing tab completion to not find the file would be okay too, or at least consistent. It's the inconsistency that leads me to call it a bug. |
![]() |
| Thread Tools | |
| Display Modes | |
| |