a thoughtful web.
Good ideas and conversation. No ads, no tracking.   Login or Take a Tour!
comment by rob05c
rob05c  ·  3143 days ago  ·  link  ·    ·  parent  ·  post: Hubski coding livestream.

How so?





user-inactivated  ·  3142 days ago  ·  link  ·  

Wait really? Will you really?

Basically just please make what we write in the box be exactly what shows up on the screen. I've been asking for this for so long if it happens I'm gonna need a new cause.

rob05c  ·  3142 days ago  ·  link  ·  

Well, I'm more back-end. This is really insomniasexx's department. I tend to agree, it does seem a bit small for unindented paragraphs. But I'm not a typographer. I'll bring it up.

    gonna need a new cause.

You could always jump on the API bandwagon.

user-inactivated  ·  3141 days ago  ·  link  ·  

.

.

.

insomniasexx  ·  3139 days ago  ·  link  ·  

Ohhhh this is what you meant by the paragraph spacing.

forwardslash this is for you! There are two separate issues (correct me if I am wrong, flag) - one is that the paragraphs go away when you edit a post. And two: a single line space doesn't register as a new paragraph (I think there is a reason for this one though...)

user-inactivated  ·  3138 days ago  ·  link  ·  

Please please please just make what we type in the little box be exactly what shows up on the screen after submission if at all possible. WHY doesn't hitting enter make a new line?

EDIT: Surely I am not the only one who thinks about this way too much,

insomniasexx  ·  3138 days ago  ·  link  ·  

Lol. Okay - I looked it up. It's a thing with Markdown (which is not something we created, just hacked to use in Arc)

http://meta.stackexchange.com/questions/26011/should-the-markdown-renderer-treat-a-single-line-break-as-br

You indeed are not the only one:

    Hitting the carriage return key on a keyboard should give the user a new line in the output. This is simply typographical common sense.

    A markup should not break elementary common sense rules in order to provide other elevated functionality.

    The fact users use two carriage returns to create paragraphs [...] is irrelevant. The markup internal rules stipulate that [...] text formatting can break break because the lack of two carriage returns. That's fair enough. But text doesn't lose readability if instead of a new paragraph, every carriage return introduces a line break on the resulting text.

    Take a look at the user edit box here:

    [image that is now gone so use flag's image above]

    Is there anything in there that is not clear in terms of formatting? He doesn't use carriage returns and yet his line-break formatting style makes that particular text easy to read and appealing to the eye. The markup however made a mess of it. So, the markup actively ruined the user text. This cannot be.

    For the sake of some special formatting elements, like list detection the markup aggressively demands two carriage returns to break a line and doesn't accept the idea of a new-line break, unless the user explicitly forces it with the BR tag.

    The line that divides easy-of-use and formatting tyranny can be very thin. On this case it was crossed over. The text the user writes on his text box should have been formatted with single line-breaks. The end result would have been readable text, just like the user intended.

user-inactivated  ·  3138 days ago  ·  link  ·  

    The Markdown answer is to add two spaces at the end of the line (or a literal <br>, I suppose).

Can you make this automatic...? I'm out of my depth-ish.

insomniasexx  ·  3138 days ago  ·  link  ·  

I think we need to just see if there is a way to read a single line break from what is delivered when you press "submit" and turn it into a <br /> (or a <p></p>). We actually don't use <br /> tags for line breaks.

cc: forwardslash

user-inactivated  ·  3138 days ago  ·  link  ·  

insom why didn't we have this conversation years ago

syzo  ·  3143 days ago  ·  link  ·  

Unrelated to that request, but is there an issue tracker for hubski? (github's?)

rob05c  ·  3143 days ago  ·  link  ·  

Make a post tagged #bugski. There is github, but right now I think I'm the only one looking at it; and the only code there is Racket. Until the main Arc code is moved there, best to use #bugski.