StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17268664
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-24T05:41:50.310
FavoriteCount
0
LastActivityDate
2013-06-24T13:33:56.373
LastEditDate
2013-06-24T13:33:56.373
LastEditorUserId
546861
OwnerUserId
546861
ParentId
17268045
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
<code>2>></code> The behavior you describe is due to how <code>{count}</code> works with line-wise commands: it doesn't perform the command <code>{count}</code> times but considers <code>{count}</code> as the number of lines on which to act. You can get a glimpse at how Vim does its thing by doing <code>2:</code>, this is what you should get in the command-line: <pre><code>:.,.+1 </code></pre> Doing <code>2>></code> is thus the equivalent of: <pre><code>:.,.+1> </code></pre> "Indent this line and the one below by one level". In normal mode, just hit <code>>></code> to indent the current line by one level and repeat until you are at the right level. If you want <code>2></code> to indent by two levels, you must first visually select the line: <code>V2></code> or <code>v2></code>. If you want to "fix" the indentation of the current line so that it matches the indentation of the surrounding lines (the most common scenario for such a task), hit <code>==</code>. <code>10G</code> <code>G</code> expects a <code>{count}</code> to jump to the corresponding line. Without a <code>{count}</code> it defaults to jumping to the last line: you can see it as a convenient shortcut for <code>{lines in buffer}G</code>. So you are inverting things a little: <code>G</code> is not "jump to last line", it's "jump to line <code>{count}</code> but without a <code>{count}</code> so let's go the last one". -- Startedit -- Let's reverse-engineer <code>G</code> for fun: <ol> <li><code>G</code> is first conceived as the normal mode equivalent of <code>:number<CR></code>.</li> <li>It is decided that, instead of doing <code>G23</code>, the <code>{count}</code> mechanism is used so we have <code>23G</code>. <code>G</code> is not an operator: it doesn't wait for a target.</li> <li>But what do we do with <code>G</code>, without a <code>{count}</code>?</li> <li>Generally, a buffer has two "special" lines: the first and the last. Maybe we can decide what the default destination for <code>G</code> is? Why not? We hate wasted keys!</li> <li><code>G</code> is not much shorter than <code>1G</code> but it's shorter so that could be a good idea to make <code>G</code> jump to the first line.</li> <li>But what about the last line? <code>12G</code> is OK when we know there are 12 lines in the buffer but what about 1257 lines? What about an unknown number of lines? Is it that efficient to look up the number and type <code>2431G</code>? No, at that point, we might as well do <code>:$<CR></code>. Well, why don't we use <code>G</code>, here? It is vastly shorter and quicker than any other way to reach the last line.</li> </ol> (this is pure speculation, of course, I have no idea what Bill Joy had in mind when he designed <code>G</code>.) -- Endedit -- Fixing Vim Generally, Vim doesn't need to be "fixed". Instead, you must learn how it works and how to leverage its power. Most of it makes a lot of sense: when you'll "get it" the reward will be huge. Also, the behavior of everything is explained in <code>:help</code>: learning how to use it is the number one skill you must grow if you are serious about using Vim.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy doesn't '2>' mean indent 2 levels on vim?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USromainl
UserOwnerUserId
1. USromainl
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy doesn't '2>' mean indent 2 levels on vim?
 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
 VTUpMod
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.