Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This not too elegant postprocessing solution seems to work for me (GNU bash, version 3.1.17(6)-release (i686-pc-cygwin)). (Unless I didn't test some border case as usual :))</p> <p>Don't need to eval things, there are only 2 kinds of quotes.</p> <p>Since compgen doesn't want to escape spaces for us, we will escape them ourselves (only if word didn't start with a quote). This has a side effect of full list (on double tab) having escaped values as well. Not sure if that's good or not, since ls doesn't do it...</p> <p>EDIT: Fixed to handle single and double qoutes inside the words. Essentially we have to pass 3 unescapings :). First for grep, second for compgen, and last for words command itself when autocompletion is done.</p> <pre><code>_find_words() { search=$(eval echo "$cur" 2&gt;/dev/null || eval echo "$cur'" 2&gt;/dev/null || eval echo "$cur\"" 2&gt;/dev/null || "") grep -- "^$search" words.dat | sed -e "{" -e 's#\\#\\\\#g' -e "s#'#\\\'#g" -e 's#"#\\\"#g' -e "}" } _words_complete() { local IFS=$'\n' COMPREPLY=() local cur="${COMP_WORDS[COMP_CWORD]}" COMPREPLY=( $( compgen -W "$(_find_words)" -- "$cur" ) ) local escaped_single_qoute="'\''" local i=0 for entry in ${COMPREPLY[*]} do if [[ "${cur:0:1}" == "'" ]] then # started with single quote, escaping only other single quotes # [']bla'bla"bla\bla bla --&gt; [']bla'\''bla"bla\bla bla COMPREPLY[$i]="${entry//\'/${escaped_single_qoute}}" elif [[ "${cur:0:1}" == "\"" ]] then # started with double quote, escaping all double quotes and all backslashes # ["]bla'bla"bla\bla bla --&gt; ["]bla'bla\"bla\\bla bla entry="${entry//\\/\\\\}" COMPREPLY[$i]="${entry//\"/\\\"}" else # no quotes in front, escaping _everything_ # [ ]bla'bla"bla\bla bla --&gt; [ ]bla\'bla\"bla\\bla\ bla entry="${entry//\\/\\\\}" entry="${entry//\'/\'}" entry="${entry//\"/\\\"}" COMPREPLY[$i]="${entry// /\\ }" fi (( i++ )) done } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POProperly handling spaces and quotes in bash completion
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USEugene
    1. USEugene
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POProperly handling spaces and quotes in bash completion
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. This solution works for the original examples, but if I add ‘rock 'n roll’ to words.dat, it fails. My real-life use of the autocompletion actually involves words with apostrophes, and that’s the reason I originally used `eval`. It’s easy enough (though not very elegant) to fix, by adding an extra ‘search and replace’ to the `for loop, and then add another for loop for strings beginning with '. The only remaining problem, as far as I can see, is that the autocompletion does not advance one cursor position if you have written an entire word, including any closing quotes.
      singulars
      1. PO
      1. USKarl Ove Hufthammer
    2. CORegarding my comment above. It looks like the situation is slightly worse than I thought. Auto-completion inside a word containing apostrophes (e.g., trying to autocomplete ‘rock 'n ro’, either written using escaped spaces and apostrophe, or single or double quotes) doesn’t work. The reason is that the `search` variable is not in its correct expanded form. Some extra substitutions seems possible, but I haven’t been able to get this to work correctly for all the three different ways of escaping.
      singulars
      1. PO
      1. USKarl Ove Hufthammer
    3. COYes, compgen seems to be stripping all qoutes... Which means they must be escaped inside _find_words
      singulars
      1. PO
      1. USEugene
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload