On Mon, Jan 2, 2012 at 11:18:47AM -0500, Andrew Dunstan wrote:
It's worked for things I've wanted, I haven't tried it for psql
stuff
Yeah, but it's a bit hacky. I might well not want $HOME reset.
Here's a small patch that does what I think would suit me and
Alvaro.
On 08/26/2012 10:13 PM, Bruce Momjian wrote:
On Mon, Jan 2, 2012 at 11:18:47AM -0500, Andrew Dunstan wrote:
It's worked for things I've wanted, I haven't tried it for psql
stuff
Yeah, but it's a bit hacky. I might well not want $HOME reset.
Here's a small patch that does what I think
On 01/01/2012 04:05 PM, Andrew Dunstan wrote:
On 12/31/2011 04:26 PM, Aidan Van Dyk wrote:
On Sat, Dec 31, 2011 at 3:17 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Andrew Dunstan's message of sáb dic 31 12:52:02 -0300
2011:
It's not a big thing, but I just found
On 12/31/2011 04:26 PM, Aidan Van Dyk wrote:
On Sat, Dec 31, 2011 at 3:17 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Andrew Dunstan's message of sáb dic 31 12:52:02 -0300 2011:
It's not a big thing, but I just found myself in a shared environment
wanting to be able
It's not a big thing, but I just found myself in a shared environment
wanting to be able to set alternative locations for the psql startup
file and history. I know there's the HISTFILE variable, but I can't
easily set that automatically unless I can at least have my own .psqlrc.
ISTM it should
Excerpts from Andrew Dunstan's message of sáb dic 31 12:52:02 -0300 2011:
It's not a big thing, but I just found myself in a shared environment
wanting to be able to set alternative locations for the psql startup
file and history. I know there's the HISTFILE variable, but I can't
easily
On Sat, Dec 31, 2011 at 3:17 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Andrew Dunstan's message of sáb dic 31 12:52:02 -0300 2011:
It's not a big thing, but I just found myself in a shared environment
wanting to be able to set alternative locations for the psql startup
