StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18754518
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-12T02:47:41.363
FavoriteCount
0
LastActivityDate
2013-09-12T03:03:33.777
LastEditDate
2013-09-12T03:03:33.777
LastEditorUserId
103
OwnerUserId
103
ParentId
9968408
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Because moving the slimv plugin to <code>~/.vim</code> fixed it, I suspect the problem is that MacVim's default <code>/Applications/MacVim.app/Contents/Resources/vim/runtime/ftplugin/lisp.vim</code> is being sourced before the <code>ftplugin/lisp/slimv-lisp.vim</code> file provided with slimv. Both of those files (<code>lisp.vim</code> and <code>slimv-lisp.vim</code>) start with code like this: <pre><code>" Only do this when not done yet for this buffer if exists("b:did_ftplugin") finish endif " Don't load another plugin for this buffer let b:did_ftplugin = 1 </code></pre> and so whichever file gets sourced first will prevent the other file from running since vim does <code>finish</code> (exits the script) if it detects that another *lisp*.vim script was run previously and therefore set the <code>b:did_ftplugin</code> buffer-local variable. You can tell this is happening by running MacVim from the command line with the arguments: <pre><code>-V20macvim-log.txt hello.lisp </code></pre> Then quit the MacVim session that starts up, and look at the macvim-log.txt file it created. Search for <code>b:did_ftplugin</code> and you'll see it referenced each time <code>lisp.vim</code> or <code>slimv-lisp.vim</code> runs, and you can see that <code>lisp.vim</code> runs first, which prevents <code>slimv-lisp.vim</code> from working. Moving your slimv install from the <code>/Applications/MacVim.app/</code> dir to your <code>~/.vim</code> dir will change the order so that <code>slimv-lisp.vim</code> is sourced before <code>lisp.vim</code>, and then slimv will work.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMacVim: slimv does not start
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsvec
UserOwnerUserId
1. USsvec
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMacVim: slimv does not start
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.