Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with discussion
Search options not deleted
user 91359
The question you're asking is designed to solicit opinions or best-practices on a particular topic, with the goal of reaching community consensus.
2
votes
Proposed Question: What RFCs should a IT Professional know by number?
RFC 1149. Not the content, just the number so you know what your colleagues are talking about when they make jokes that bandwidth increases with carrier age.
- 4,832
14
votes
Accepted
4
votes
2
answers
52
views
Does unzip (and un-other-compress) deserve its own tag?
Do we need both the tags zip and unzip?
Or more generic: should we clean the un-$compress tags to $compress?
Our should we even consolidate some of these tags into compression?
Inspired by this si …
- 4,832