mineo

First-time StreetComplete user here. I just answered a few of these "street has a sidewalk" questions myself. Upon first clicking on one of them, I was able to answer this question for each side of the street individually. The visual selection that you mentioned only applies to one side.

I believe hash -d and supsequent expansion of those paths only works in ZSH, which calls this "static named directories" (http://zsh.sourceforge.net/Doc/Release/Expansion.html#Static...).

Similarly, man and woman in Emacs generate a ToC that imenu (M-x imenu) can use.

The announcement already mentions that ProxyJump is meant to be a simplified version of indirection, not a completely new feature.

Or use the reader view.

This is why you don't let cats anywhere near your keyboard ;-)

I agree on the section definitions. It's very hard to remember which underline I need to use because every project (or even document) can just define their own order implicitly. The sphinx project recommends a specific order somewhere in their documentation that I look up every time I need to write rst, but markdowns just-count-the-hashes is much easier.

To be honest, I don't find this to be true. To email a patch, you usually have to

* figure out if you can use git-request-pull or git-send-email * sign up for a mailing list (which, depending on the mailing list software the project uses, can take anywhere between a few seconds and annoyingly large amounts of minutes) * optionally figure out how to not receive the whole traffic of the ML or set up custom email filters * figure out if you have to CC the people responsible for the area of the code you're going to send a patch for (which might be written down in a wiki, some CONTRIBUTING file or somewhere else) * figure out if the project wants an extra cover letter for the patch series or not (and optionally search the man pages for how to write one).

With GitHub, I just use [hub](https://hub.github.com/) or an Emacs package or plugins for other editors to

* fork the repository * (without additional tools, I now have to add my newly created remote) * push to my own remote * create the pull request after reading CONTRIBUTING<tab>

which so far has been the exact same workflow for every project I've seen (ymmv of course).

Note that not all of those use Phabricator as a bug tracker (KDE, lighttpd, LLVM, Haskell, I imagine a lot of bugs for Wikimedia are reported through project chat pages on the wikis themselves).

The same thing exists for regional and inter city trains in germany that the Deutsche Bahn is responsible for: http://www.apps-bahn.de/bin/livemap/query-livemap.exe/dn?L=v...

If by "hardcodes" you mean "can be changed in the configuration file", then yes, that's true.

Fun fact: google code now has a " We have some known issues with hg repositories. " banner up since a few days ago.

503s for me, here's the article on the Internet Archives Wayback Machine: https://web.archive.org/web/20150517152126/http://dnf.baseur...

This might sound a bit stupid, but I was looking into F# a while ago (26 days ago, if the timestamps of the few files I wrote don't lie :-) ) and now I'm wondering I could have found those things (especially RWFP because I usually don't like learning from videos) if I start on fhsarp.org?

http://fsharp.org/about/learning.html does not list them, and going from http://fsharp.org/about/index.html via the "Language Reference" link to https://msdn.microsoft.com/en-us/library/dd233181.aspx doesn't list RWFP in the sidebar anymore.

It's possible to "lock" [0] conversations on GitHub. This means that only collaborators of the repository are able to add comments to the issue/pull request.

[0] https://help.github.com/articles/locking-conversations/

Some of the movies those kids had already seen are rated 16+ as well.

You can just use udiskie (https://pypi.python.org/pypi/udiskie) to automatically mount exernal drives, even if you're not running a DE.

They were talking about Austria (in Europe), not Australia :-)

That's because gcc is trying to compile it as C, not C++. You need to call the file "test.cpp" or explicitly use g++ instead of gcc to compile it. (You'll also need to "#include <assert.h>" or it won't compile.)

The website doesn't seem to work reliably at the moment, here's the archive.org version: https://web.archive.org/web/20131021002154/http://www.ibibli...

That should be "foldl f z (x:xs) = foldl f (f z x) xs" because the function f takes two arguments (the whole thing boils down to "(((z `f` x_1) `f` x_2) ... `f` x_n)").