I'm rather against (too frequent) attempts to produce FAQ type documents.
There are lots of "systematic" documents available -- for instance, package documentation, books, guides and so forth. I'm all in favour of them, of course, and of encouraging people to use them.
But I think, mostly, a site like this is valuable precisely because it does something a ...
Using the Advanced Super Ninja Search Options, you can search for user:10827 hasaccepted:0 closed:0 sorted by "newest". This searches TeX.SX for posts by User 10827 (you) that has no accepted answer (hasaccepted:0) and is not closed (closed:0), filtered according to the posted date. Currently there are 5 such questions (see below).
You can as well add the ...
One thing one can do is to perform a Google image search for
site:tex.stackexchange.com <search term(s)>
I am using this sometimes to find possible duplicates, and, according to my experience, this turns out to work surprisingly well.
Actually, I sometimes wish that users asking questions could do that search themselves. If they end up not ...
Searching for xyz finds results that are listed in the text only and not the code part, unless that code part is set using the <pre>...</pre> tags. So, this type of search excludes code segments that are not set via the <pre>...</pre> tags (indented by 4 spaces).
If you want to search within those segments, you need to use code:"<...
The closest that I know of (or actually just found out about) is code:"\widthof". This seems to search only for text that has been marked as code. As for its developmental status:
It's not a secret, but it's not polished either...I was interrupted in the middle of implementing it and haven't re-visited it in a while. You're welcome to use it and we won't ...
You can only link the two databases containing posts and comments using the SEDE. The following query lists questions on the main site, sorted by their last activity date (oldest to newest) with these attributes:
select top 1000
p.id as [Post Link],
p.lastactivitydate as [Last Active]
from posts p
The "Advanced Search Tips" tooltip is at right from the "Search" button on the search page:
To search for answers by tohecz in the tag [tex-core] the query
user:11002 is:answer [tex-core] works. To find the correct user ID, either visit the profile of the user (and the ID is in the address), or look him in the user ...
As https://meta.stackexchange.com/a/143432/163868 describes you can find them by searching. Use the search term hasaccepted:0 to only find questions with no accepted answer, answers:1 to only find questions with at least one answer and use user:me to only find posts by you, i.e. search for
hasaccepted:0 answers:1 user:me
You can also use a user id instead ...
Recently, the network implemented a date range specification as part of the "Ninja Search Options". From the linked post, here's an extract on the implementation:
This is now implemented, here are some examples:
created:2012 (created between 2012-01-01 and 2012-12-31)
created:2012-04 (created between 2012-04-01 and 2012-04-30)
While I'm not against such organization of content, boosting your search skills from novice to Ninja might also help find what you're looking for.
We already collate such question in Often referenced questions, where answers point to common FAQ-like questions.
First of all, understand that having duplicates on a site is not a bad thing. They provide multiple landing points for visitors seeking a very similar solution. That's correct: Different questions leading to the same solution.
Perhaps someone is asking for the sum 12+15 while someone else is interested in finding the product 3×9. The example may seem ...
Searching within a set of favourites has been re-implemented under the new elasticsearch engine (around January 2013) across the entire network. The following search options are available:
infavorites:mine - search within your own list of favourites;
infavorites:<userid> - search within numerical <userid>'s favourites (yes, you can search ...
Searching for posts that contains code can be achieved using the boolean operator hascode. More specifically, hascode: with yes/true/1 returns only posts that contain code blocks; no/false/0 returns only posts that contain no code.
Searching for posts where inline code (via backticks or <code>...</code> markdown) contains a specific <string&...
You'll have to route your query through SEDE. I think the reason here is the difference between the stored content of the post (what you actually typed) and the baked content (what is visualized through the browser). This difference is needed because of Stack Exchange accepting Markdown as input.
This query hopefully provides what you're looking for:
The search help page has been heavily updated since the implementation of the new elasticsearch search engine. Most of the Ninja search techniques that were considered "advanced" have been included as reference.
For me, effective searching spawns from using a combination of search criteria. For example, mixing search terms with tags and user specification ...
It's true that you need to know what to search for in order to find an answer, yet you don't know the answer to your question to begin with. So, it's definitely difficult to never ask a question that hasn't already been asked. Overcoming this obstacle comes from spending time on the site, but could also be avoided by visiting the chat room first and asking ...
There doesn't exist a native way of doing that on the network. However, as already mentioned in Schrödinger's cat's answer, you can use the image search option with Google, targeting this site via
Note though that this may only be valuable in select instances where posters did use images. Some threads only post an image in the ...
As a typographical side note, the following mnemonic describes the difference between an orphan and a widow:
"An orphan starts alone, a widow ends alone."
An orphan refers to a single word or line left at the bottom of a page, with the remainder of the paragraph appearing in the next column or following page;
A widow refers to a single word or line that ...
in addition to the suggestions provided by werner, there's also a
very nice meta question
Often referenced questions
which can be checked for possible duplicates.
if something is there, good. if it's not, and you find a really great duplicate in your further search, add it to the list, to make the next person's job (or your own next search) easier.
There is a special "unanswered" list which can be sorted by date: https://tex.stackexchange.com/unanswered/tagged/?tab=newest
For everybody who is like me hiding the left hand sidebar, this can be hard to find as it hides behind the three horizontal lines at the top left of the headline:
If I remember correctly there are some differences and the two list ...
If you can't find a question that would be the same as what you ask, simply go ahead and ask a question on the main site.
What you want is impossible, but not because TeX wouldn't be capable of such things (well, LuaTeX shall be able to solve this), but because it cannot know whether the number is after the word like in your examples, or before the word like ...
You could try out Stack2RSS or another solution (see Stack Apps), that make use of the Stack Exchange API.
The date must be given in Unix time. For Windows users an online ...