102

There are two ways in which you can view a Question/Answer site. One is as a real-time "I've asked this question and I want a quick answer now" type of site, and the other is as a longer term repository of questions and definitive answers. I think that many of us here take this latter view of the site. As a result, we have lots of very high quality answers, ...


81

Several reasons: We vote a lot, and we vote up. We have a narrow scope, which means there are people who can answer almost any question. For some people, TeX and friends is almost a religion which they practise through this website. Oh and I forgot to say: We vote a lot. That's it I think. PS: Did I mention that we vote a lot?


76

None of our suggestions in New TeX site theme coming soon has been taken into consideration. None. You could have simply avoided asking about the changes and deploy them without notice. Alternatively, the Meta post about the site change might have been: Dear users of TeX.StackExchange, in a few days our sites will become all the same as Stack Overflow, ...


62

There is a lot of real anger about the changes here, and I think it's important to convey why this is. I'm going to try to do that from my own point of view: as a moderator, I'm not at all happy with the way things have been handled by the Powers That Be. (I think Rollout of new network site themes sums it up pretty well.) We (the 'TeX-sx community') have ...


55

I also often find myself dropping a comment instead of answering. In addition to what was already answered here, my reasons mostly are Might be too localized. If the answer to a huge question is a one-liner, then more often than not the real problem was a little thing the OP overlooked, having nothing to do with the perceived question at all. In that case, ...


54

status-review Width of main content Added .gif by @Milo I realise the middle section is just the boring bit where the users chat about their interests and the sidebars are the interesting places where stackexchange can insert revenue earning links, but really is it too much to ask that a question and answer site leaves more room for the questions and ...


53

As Tom and David mentioned in the comments, we just upvote. Even if one feels the urge to downvote a question or an answer, we encourage different approaches, like leaving a comment to help make the content better or point crass errors, or simply do not upvote the content at all (but still pointing what is going on). A question or answer that shows effort ...


52

Just to make an example, look at europecv stack exceeding which cannot be answered in the current form, as \documentclass{europecv} \usepackage[T1]{fontenc} \usepackage[magyar]{babel} \begin{document} x \end{document} gives no error whatsoever. In the .../tex/latex subtree of TeX Live there are currently 2066 directories, which correspond to more than ...


46

abraces by Werner Grundlingh (Werner). Origin: Asymmetric overbrace aobs-tikz by Claudio Fiandrino. Origin: Highlighting in Beamer using TikZ nodes autonum by Patrick Häcker (MMM). Origin: showonlyrefs and cleveref babyloniannum by Raphaël Pinson (ℝaphink). Origin: Typesetting Babylonian numerals? bib2gls by Nicola Talbot. Origin: Is there a program for ...


46

Boycott this site until and unless the old look is restored! If it's not restored, let's say goodbye and good luck to this site entirely. Why do I say this? It's because I suspect that the only way that the powers that be will ever respect and listen to our views is if we -- and especially the most active users -- state unequivocally that we refuse to go ...


45



44

Gratitude on the Stack Exchange network is provided by means of voting (bestowing reputation). We have a Text building block dedicated to this, which perhaps explains it best: Welcome to TeX.sx! Usually, we don't put a greeting or a "thank you" in our posts. While this might seem strange at first, it is not a sign of lack of politeness, but rather part of ...


44

From very early on in the life of the site, there has been a presumption that voting should be a broadly 'positive' action. In particular, the community here have generally felt that for most questions voting below -1 isn't really desirable: Please don't downvote below a score of -1, even if the question in its current form needs some improvement. A score ...


44

The StackExchange model is based round the idea that the sites are not forums, but that questions and answers should have some element of generality. As such, 'good' questions should be focussed on the matter in hand, ideally without many things that might make good forum posts. That's one reason that 'thanks' is discouraged and why community edits are ...


44



43

LaTeX Packages A-M Symbol legend: BitBucket, GitHub, Launchpad, Google Code, GitLab abc: Enrico Gregorio (egreg) abraces: Werner Grundlingh (Werner) accents: Javier Bezos accsupp: Heiko Oberdiek acro: Clemens Niederberger (clemens) acronym: Heiko Oberdiek with Tobias Oetiker adforn: cfr [LaTeX support only] adfsymbols: cfr [LaTeX support only] ...


43

Almost every question here can be answered by reading a manual (or the documented sources) so mostly I don't think a "read the manual" answer is appropriate (and definitely not that particular acronym which isn't that polite in most versions of its meaning). Sometimes, if I think the user really could have tried harder, I do mention the manual. If an answer ...


42

Voting is at least to some extent about popularity: questions which get lots of views are more likely to get lots of votes than those with fewer views. Highly complex technical questions don't attract as many views as more accessible questions, so some of the most tricky and perhaps 'insightful' questions attract relatively few votes. At the same time, some ...


41

I completely agree, and I've been thinking along similar lines recently. I can only answer for myself and not for anyone else, of course, and only describe what I now do. What I try to do now is make the "unanswered" list (and specifically those in my tags) my main point of call. I take a look at new questions, though I try to concentrate on helping ...


41

Our next interviewee: To be announced


41

I think any improvement on an existing answer is valid. It would be far more helpful to have current information than to have outdated yet functional answers. Even if this means you replace 50 lines of code with a new \usepackage and a single command. The reason should be obvious: Answers here are meant to benefit the community, which is always changing. ...


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