StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15036128
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-23T01:53:21.327
FavoriteCount
0
LastActivityDate
2013-02-23T02:05:00.413
LastEditDate
2013-02-23T02:05:00.413
LastEditorUserId
1526010
OwnerUserId
1526010
ParentId
15033864
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think @Kent's answer (the function) is the "most correct" when doing complex searches/substitutions. It's easier to change afterward, and to understand it also after a while, it's also quicker to write than this. But I think it can be interesting if it's possible to do this with a "oneliner". I welcome comments about this not working, I find it interesting myself if it's possible, not if it's the "best solution". A "oneliner" for all situations described in the original question. <pre><code>:v/str3/s/\v(.*str1&.*str2)@=.{-}\zsxxx/yyy/g </code></pre> Explanation: <ul> <li><code>:v/str3/</code> all lines NOT containing "<code>str3</code>"</li> <li><code>s/</code> substitute</li> <li><code>\v</code> "very magic" (to not have to escape regex expressions like <code>{}</code>), <a href="http://vimdoc.sourceforge.net/htmldoc/pattern.html#/%5Cv" rel="nofollow"><code>:h \v</code></a></li> <li><code>(.*str1&.*str2)@=</code> positive look-ahead, <a href="http://vimdoc.sourceforge.net/htmldoc/pattern.html#/%5C@=" rel="nofollow"><code>:h \@=</code></a> <ul> <li><code>.*str1</code> any character 0 or more ("greedy") followed by "<code>str1</code>", the preceding <code>.*</code> is important for both <code>&</code> and <code>@=</code> to work</li> <li><code>&</code> pattern before and after <code>&</code> must be present, different than <code>|</code> that is using "or", both patterns must start at same place, thats why <code>.*</code> is used before <code>str1/2</code>, <a href="http://vimdoc.sourceforge.net/htmldoc/pattern.html#/%5C&" rel="nofollow"><code>:h \&</code></a></li> <li><code>@=</code> the atom before (in the parentheses) should be present, but the pattern is not included in the match, the atom must however start at the beginning of the line for this to work (<code>.*</code> makes sure of that).</li> </ul></li> <li><code>.{-}</code> any character 0 or more ("not greedy"), <code>{-}</code> instead of <code>*</code> is important if more than one occurrence of <code>xxx</code> should be substituted (not enough with the <code>g</code> flag in this case)</li> <li><code>\zs</code> sets the start of the match (what to substitute).</li> <li><code>xxx</code> finally, the string to substitute</li> <li><code>/yyy/</code> replace the match with <code>yyy</code></li> <li><code>g</code> all occurences on the line</li> </ul> This gives the same result as using the example in @Kent's answer, it will handle any order of <code>str1</code>, <code>str2</code>, <code>str3</code> and <code>xxx</code>. I repeat that this is an alternative if for some reason a function is not an alternative. As I understand OP, e.g. <code>str2</code> is always after <code>str1</code> in his case, so this is more a general solution for situations like this (and perhaps more of academic interest).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POA VIM search/replace pattern
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. US244an
UserOwnerUserId
1. US244an
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.