Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
29

'Executive summary' of the following answer: The key aim of reading questions is to help the asker Voting to close is thus (usually) something to do after comments or similar to improve questions have failed Rapid closing is ideally aimed at clear cases such as questioner agreeing, spam, massively off-topic, etc. Minimal working examples (MWEs) are a useful ...


27

There are a few things to say here. First off, the StackExchange 'back end' works in the same way for all sites, which means that 'we' (TeX-SX) have to use the structures as decided on by the 'Powers'. Occasionally that means we have some oddities. That leads to the second point: 'off topic' is (currently) intended not only to cover questions which are out-...


26

One I think uncontroversial close reason is for things which are typos or which cannot be reproduced: these are about TeX but are unlikely to help any future readers. Thus something like This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was ...


25

It seems to me that the practice may have outstripped the previous consensus. I understand that (as the original meta question posited) a question that is a bug report should be closed. Truly that is not because it is "too localized" but because it is not really a question: "I've found this bug" is a statement, not a question. The question "Why am I seeing ...


22

Since the question is fundamentally about WordPress capabilities and not TeX (as evidenced by your suggested answer) it is off topic. As for the "integrating LaTeX into Platform X" type questions, I think they would generally be off topic unless they specifically deal with the TeX side of things (such as how a particular TeX distribution works etc.)


22

As mentioned in a comment, a high number of views does not in itself mean that the question is a good one for the site. For example, a 'provocative' title may attract a lot of hits while meaning that the question does not fit the Q&A format or indeed be really about TeX at all. Views of questions come primarily from people searching for text, probably in ...


21

As the question indicates, almost all real (La)TeX documents will be created using a text editor. There are three distinct ways that might be done. Using a standard text editor with no (La)TeX-specific add-ons. This category covers for example using Notepad, TextEdit or 'vanilla' Emacs. Using a standard text editor with add-ons. This covers both simple ...


17

[Answering my own question: hopefully reasonable here!] Voting to close a question as 'unclear' should take place only after the questionner has been given a chance to improve the question. Based on the existing consensus for the previous set of closing reasons, that means giving people 48 h after the first comment requesting additions/clarification/changes ...


17

There is a difference between cosmetics that TeX should perform and cosmetics that purely rely on the typesetters choice. If the question is about how to turn on/off ligatures, implement auto kerning hyphenation, letterine, ornaments etc. or the specification is given and don't know how to realize in terms of TeX then it is obviously on-topic. But if it ...


17

As we have seen from the comments, every detail leads to another full blown discussion and I am not the TeX-SX correspondant so I'll try to be a user again. Because there is user involvement that might lead to confrontation and since we are extremely avoiding it, I have to be very careful with the sentences I am using. Otherwise it starts to get dissected ...


16

one possible reason is "user error, discovered by user". this is already a reason frequently used to apply the "too localized" designation, when a user mentions in a comment that s/he has found the problem (sometimes even before a suggested answer is posted, although often after one or more comments by other viewers). joseph suggests in a comment that ...


16

I think you have a point. Even though I find that specific question quite ridiculous, because whatever solution would just use the same idea as natbib, it's actually not a simple task and I don't think it'll get a reasonable answer, I voted for re-opening (and 2 other people have done so even before me). It is a question that suits the site, and it is ...


16

The primary goal of all Stackexchange sites is to become repositories of reliable information on whatever topic they cover, in our case, TeX, LaTeX, ConTeXt and their relations. To this end, questions whose answers can't be given definitively are not good questions as regards to the goals of the site, and are therefore closed. Now your question is by ...


15

Questions that work well on the StackExchange sites are ones for which a resolution is well-defined. If this is not the case - when the question is too broad (leading to no specific, concrete answer) or when a question solicits subjective commentary (quite often although not exclusive to questions tagged best-practices) - the risk of being closed as "too ...


15

If you can manage to demonstrate the problem you’re struggling with within 20 or 30 lines of a fully compilable Minimal Working Example, your question most likely won’t be closed as too localized. What makes questions too localized is not including a full document or including several problems in one question (this might trigger other closing reasons as ...


14

Very basic (La)TeX questions are a tricky area as at least to some extent many of them could be covered by the concept 'read a manual'. There should be a space for asking good basic questions, certainly when they are phrased such that the question is clear, self-contained and likely to help future user. More problematic are basic questions where that's not ...


14

Let's review the complete original question to see of there's any reason to close it. Title: "Just reducing the f***ing huge space before the first line" This is obscene language. Sean later took the time to clean it. Question text: "Please help me to make the rest of my life better, found nothing here..." This is not a question. Code: was added without ...


14

Troubleshooting questions are quite welcome but the issue has always been how to answer them. The usual pattern is that a series of comments, none of which can really be viewed as an answer, are posted and we end up with the user saying 'Ah this solves it'. However, normally this comment thread is tied to the issue for the questionner, and it's unlikely that ...


14

One man's bug is another man's feature... I don't think whether the OP considers it to be a bug is that relevant. If the problem has been identified and fixed by the package author in an updated version of the package then we can consider treating the question by some special mechanism for "bug reports" otherwise it is best to assume that it's a permanent ...


13

Quoting from Joel Spolsky's answer: Why is there a green Honda Civic parked out in front of my house? This is too localized because: Who cares? Is it even still there? Go check. What are the chances that this question could ever be answered in a way that would benefit anyone else? Now is it there? In order not to be ...


13

I would have to disagree here with Stefan here. While I am not what most would consider a newbie, I am by no means an expert on general LaTeX usage as I have mostly focused on only what I need at the moment, or think I will need coming up in the foreseeable future. And hence, I don't use abstract, or figure names. Looking at those two posts, they seem ...


12

Here is perhaps a sequence of events that lead to the closure, as well as some motivation behind it: It has been decided by the TeX.SE community to host "Answer the unanswered" sessions (see Regular “Let's deal with unanswered questions” chat meetings?) in an attempt to reduce the number of unanswered or open questions. These "janitorial sessions" are there ...


12

As I see this question it's a perfect candidate for http://math.stackexchange.com (as already suggested by a comment to that question). They users there aren't bad in TeX either, because they use it with MathJax. Because there is already a specialized SX site for this I agree that we should consider such questions as off-topic on TeX.SX. However, migration ...


12

I consider these questions to have been properly closed as “Unclear”. Question #1: listing's lst@BeginWrite gobbles '->' and '=>' from input After a request for a minimal example, there has been no answer in more than a year. I'd consider this question as impossible to answer because it's unclear what the problem is: my answer was ...


12

The feature you're requesting already exists. When closing as Off Topic, you can add a custom reason if you feel that the default ones are not appropriate. In this case a comment is automatically posted with the reason you wrote in that box. I don't remember at the moment if other close reasons generate auto-comments (in the case of choosing Off Topic). ...


12

Flagging using the generic 'needs mod attention' function is fine (though we tend to be conservative about closing). Whilst we can add a limited number of custom close reasons for the site, the number of uses has never seem worth it: we don't have one big use of flagging.


11

I think that another point is missing here: Answers for caption are different than answers for abstract. There is a common thing -- changing setup of \...name, but for captions there are other possibilities, and this makes it hard to "read only the part of the other question that is relevant to me, when this part is not really seperated". So in my opinion, ...


11

Just to stir up the soup. I agree with Alan Munn on this issue but with a slightly different motivation. I'm actually quite bothered by the word swiftly. I don't mind if the question stays open or closed, either way the issue is not resolved so no need to insist on practice because next year it would really be an ancient issue but as you can see it's ...


11

The reason such question are often closed it that bugs which will be fixed soon make the question "too localiced in time" because soon they issue will be gone and there is no suitable answer beyond "update the package". Note that our "no bug questions" policy is (or should be) IMHO mostly about questions which directly cover a bug, like "why do I get this ...


11

I don't think this can be answered in all generality. If the purpose of the question is more like "how can I program this effect myself", I doubt it would be considered a duplicate of a question "what package do I have to use". But in this specific case, The effect which was asked about is tricky to achieve because it requires patching into and ...


Only top voted, non community-wiki answers of a minimum length are eligible