Quoting (Again!)
-
Repro:
- Highlight User 'A' post in post 1 as if you were going to do a quote reply
- Read User 'B' post in post 2
- Click the 'Reply' button to User 'B' in post 2
- Wonder why the fuck you're quoting User 'A' in post 1, but replying User 'B' in post 2
-
Post 2.
-
-
Post 2.
Same thing highlighting post 2 and replying to OP, from the look of it.
Edit: Actually it looks like it treated that as just a reply to post 2.
-
It's highlighting any text that prompts 'quote reply', then clicking the reply button. My repro steps are specific so that you can see exactly how the error is generated.
-
I know, I was trying something a bit different.
Actually
What if I highlight one, reply to another, and highlight-quote a third post?
Hmm
-
You report this on meta.d? Seems like our bug category isn't checked anymore (or only rarely).
-
- I'm not reporting Any additional reports to meta.d Ever.
- I'm banned until October 5th for my last bug report.
They can come here.
-
Oh, forgot that you were the one they banned. My bad.
-
Why should we work as unpaid bug testers anyway?
-
I don't mind reporting bugs if they will be worked on. If I'm stuck using the software, I want it to be improved. I'm halfway tempted to make an unofficial official bug tracker for Discourse so that Jeff can't delete bugs and go 'Oh, what bug' (Or feature request)
-
I dare you.
-
I managed to set Redmine up pretty easily for a work project.
-
Redmine works reasonably well, and the overhead is very low. We used it for a while before switching to JIRA Agile. Yeah, go ahead and make fun, it works for us though.
-
I normally just use GitHub's (or BitBucket's) built in bug tracker, but this project didn't have a code base behind it, so I figured I'd see what else was available for free.
-
Give me a second... I got this.
-
I managed to set Redmine up pretty easily for a work project.
I should probably clarify. When I said "pretty easily", I meant that I found this guide full of CLI commands, which happened to work:
Paging @blakeyrat.
-
I vaguely recall using Redmine before. We couldn't get a stock Ruby on Rails install to work, but someone somewhere had a VM appliance already working so we just downloaded and booted it.
-
I bought a domain and set up a bug tracker, give me like 3 minutes for it to update and i'll link it.
-
I bought a domain and set up a bug tracker, give me like 3 minutes for it to update and i'll link it.
What is this I don't even...
-
I bought a domain and set up a bug tracker, give me like 3 minutes for it to update and i'll link it.
I think this would be called "salting the wound". I dig it.
-
I think the phrase is "cutting off your nose to spite your face".
-
-
More like "cutting off your nose and throwing the bloody thing at your foe."
-
Ok, the caching takes a few more than 3 minutes to update.
It will be located at
I will have an official post when it's done propagating.
-
I will pay you 5 English pounds if you manage to make that site rank higher than the official Discourse site on Google for the search term "Discourse".
-
In what way is it burning bridges or nuking? @codinghorror bans @Matches, so @matches goes and spends actual money to buy a domain name to allow him to do the thing @codinghorror banned him for. A thing that helps @codinghorror's business.
It's closer to fucking Stockholm Syndrome.
-
Redirects to here:
-
Does it link directly to the issues page? (Caching on my phone is being a bitch)
-
Yup.
-
http://what.thedailywtf.com/t/the-new-official-unofficial-discourse-bug-tracker/3103
I will start populating it tonight with @Yamikuronue's list of things. I am current unavailable, so it will be another 4 hours or so.
-
Looks good in current (desktop OSX) build of Chrome.
-
I can make this happen.
-
oh jeez.
someone else doing a bugtracker (of non-dicsourse bugs) via dicsourse!
-
The idiocy is spreading.
-
By the looks, it's probably a step up for them. Maybe I should start a fee service setting up bug trackers.
-
http://discourse.codecombat.com/category/bugs
someone else doing a bugtracker (of non-dicsourse bugs) via dicsourse!
Sort of. The description in the category says:
If you can, it'd be awesome to post bugs in the GitHub issues12 instead of here, but if you want to discuss a bug more, then you can post bugs here in this Bugs category. If they're bugs in particular levels, look for threads on those levels already. If you have time, please make your bug report super great!
So, I've never used Github's tracker, but I presume the discussion capabilities are limited. This isn't as stupid as Jeffnco.
-
-
please make your bug report super great!
sounds just like dicsourse's stated objective?
-
Github's tracking is not terrible but it's not exactly thorough.
-
"'Yields falsehood, when proceeded by its quotation' yields falsehood, when proceeded by its quotation."
I'm not sure why I mention this now, but I'm sure it is relevant to discussing Dis&Curse somehow.
Filed under: Dating myself again.. who else here has even heard of that book?
-
who else here has even heard of that book?
Ask the reverse. Who hasn't? It won a Pulitzer prize, in case someone wants a clue, and it mostly hasn't dated too much.
-
I am very pleased indeed to find out that I was mistaken. You are right, the book has not gotten dated much at all, quite the contrary, but it is from 35 years ago, and most of my younger colleagues don't seem to be familiar with it, nor do most of them want to try reading it. Pity, that.
-
Ask the reverse. Who hasn't? It won a Pulitzer prize, in case someone wants a clue, and it mostly hasn't dated too much.
I probably have, but I will admit to being insufficiently familiar with it to know what book you are talking about.
-
Filed
https://bitbucket.org/masamunewos/discoursebugs/issue/5/highlighting-user-text-causes-incorrect
-
I probably have, but I will admit to being insufficiently familiar with it to know what book you are talking about.
Gödel, Escher, Bach: An Eternal Golden Braid, which is perhaps the most accessible entry to Computer Science that I've encountered.
It's a big book, and shouldn't be read in a hurry. A background in real CS makes it a lot easier read. The only parts that have really dated all that much are those that deal with AI, where we know a lot more than we did when the book was written. The other parts — the large majority of the book — are still valid now.
-
Gödel, Escher, Bach: An Eternal Golden Braid
Ok - I'll admit to being ignorant. Until this thread, I'd never even come across the title, nor from a quick skim of PikiWeedia, do I recall the book even being alluded to.
(The subjects of some of the content I'm well aware of - it's the book itself I've no recollection of.)
-
Ok - I'll admit to being ignorant. Until this thread, I'd never even come across the title, nor from a quick skim of PikiWeedia, do I recall the book even being alluded to.
It's not the easiest of books to find in the UK; it never received the sort of exposure that it got in the US. I was very happy when I found a copy.
-
Definitely heard of it, but never read it, and don't really know anything about it. Didn't even know it had anything to do with CS.
-
Definitely heard of it, but never read it, and don't really know anything about it. Didn't even know it had anything to do with CS.
The basic topic is recursion, but it's not just looking at simple recursion; it's looking at embedding concepts in concepts, ideas in ideas, entities within themselves. It is superb even if some of the things mentioned have proved to be outdated by subsequent research (in particular, we know a lot more about AI than we did, and it looks like intelligence isn't really what it was thought to be back when Hofstadter wrote GEB). I also recommend the book for how it doesn't just talk about theory, but also how it also interlinks with music and art (hence Bach and Escher).