Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You <em>must</em> create those files and folder yourself:</p> <ol> <li><p>Open Terminal.app (found under <code>/Applications/Utilities/</code>).</p></li> <li><p>At the prompt, a <code>$</code>, type each of these lines followed by <code>&lt;Enter&gt;</code> (don't type the <code>$</code>):</p> <pre><code>$ touch .vimrc $ touch .gvimrc $ mkdir .vim $ open .vim </code></pre></li> <li><p>At this point, the <code>~/.vim</code> folder is open in a new Finder.app window.</p></li> </ol> <p>But I'd respectfully suggest you to get accustomed to the command-line <em>and</em> Vim's basics <em>before</em> rushing to install plugins. </p> <p><strong><em>EDIT</em></strong></p> <p>You didn't follow the instructions, no wonder the plugin doesn't work.</p> <p>You have to move <code>cvim.zip</code> into <code>~/.vim</code> and run the command <code>$ unzip cvim.zip</code> in the terminal. Read the instructions more carefully and don't let Safari expand archives automatically.</p> <p>Now that you have <code>~/.vim/c</code>, here is what you should do to go forward.</p> <p>Supposing your <code>~/.vim</code> is empty (beside your <code>~/.vim/c</code>), move <strong>the whole content</strong> of <code>~/.vim/c</code> into <code>~/.vim</code>. After this operation, your <code>~/.vim</code> folder should look like that:</p> <pre><code>+ ~/.vim + c &lt;-- your folder + c-support + (many folders and files) + doc + csupport.txt + ftplugin + c.vim + make.vim + plugin + c.vim + README.csupport </code></pre> <p>When you are done, delete <code>~/.vim/c</code> and start Vim. The plugin should be installed and working.</p> <p>If your <code>~/.vim</code> folder is <em>not</em> empty (say it already has a bunch of folders and files like <code>~/.vim/color</code>, <code>~/.vim/syntax</code>, whatever…) you'll have to move <em>manually</em> each subfolder/file from <code>~/.vim/c</code> to the right place in <code>~/.vim</code>.</p> <p><strong><em>ENDEDIT</em></strong></p>
    singulars
    1. This table or related slice is empty.
    1. PONo vimrc, gvimrc and .vim on mac
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USromainl
    1. USromainl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONo vimrc, gvimrc and .vim on mac
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COi just want to install [this](http://www.vim.org/scripts/script.php?script_id=213)
      singulars
      1. PO
      1. USratkke
    2. COSo, i did what you say, and after that a read a instruction to install [this](http://www.vim.org/scripts/script.php?script_id=213] "Copy the zip archive cvim.zip to $HOME/.vim/ (Linux/Unix) and run unzip cvim.zip" i did it but plugin didn't work.
      singulars
      1. PO
      1. USratkke
    3. COHow did you "unzip" cvim.zip? What do you get in `~/.vim` afterward? How do you know it doesn't work?
      singulars
      1. PO
      1. USromainl
 

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