Filling the indent area with dots is not a sensible default IMO. Often when I work on a query I am going to reuse it in an application. If PgAdmin III or psql filled the indent area with dots then they would be included when I copied the query I'd written.<p>Even though I always reformat the query, and even though the text editor I use -- vim / neo-vim -- supports rectangular text selection, I would be annoyed at such dots.
Beyond "sensible defaults", it's also important to have the defaults specified sensibly. For robust application development, mainly when working with large software systems, I find it best to disallow "unset" configuration options and the implicit behaviour they entail. That is, every option must have its setting explicitly specified in the configuration. The defaults should exist as a "full" configuration, similar to the configuration file pgcli comes with. Unset configuration options result in a runtime error during application startup.<p>Also, I believe I first heard of pgcli from an HN comment, and since then I have been a daily user of it.
<p><pre><code> Expanded mode in psql is a way to output the results of a
query if the output is too wide to fit in the screen when
shown as a table. This can be toggled by \x on or \x off.
[...] In pgcli, we have the ability to do this but this is
not enabled by default. It has to be enabled via the config
file (~/.config/pgcli/config) by the user.
I don't think we'll change this behavior.
</code></pre>
Why not? Seems quite sensible a thing to do when the output otherwise wouldn't fit.
This is a serious, genuinely curious and open-ended comment - I'm not arguing for a position here or making a point and can accept any response.<p>Do people here think the world would be a better place if installing something didn't require reading any documentation (not even 45 minutes of it) or necessarily spend any time making choices?<p>For example, if it were possible to requisition a new AWS instance and install a Ruby on Rails configuration with "sensible" defaults on it, in, say, < 30 seconds, and it being secure and properly configured so that a newbie without any experience can immediately deploy apps on it securely and without understanding the parts involved or making choices?<p>I can see arguments for both sides.
Actually a really nice command-line interface with autocomplete to postgres. I'm usually rapidly dissappointed with all the GUI offerings to Postgres so this is a breath of fresh air. Defaults definitely seemed reasonable as per TFA
Oh, for a command-line SQL client.<p>I was expecting this to be about web pages.<p>"Yes, of course I want to sign up for your "newsletter" offering me the latest deals every hour on the hour!" Click on the invisible x to opt out. (Very Facebook.)