SQLite Forum

Timeline
Login

6 forum posts by user crustyoz

2020-03-18
13:24 Edit reply: Request for comment: New ANALYZE syntax (artifact: 71a6ea8000 user: crustyoz)

Would you consider adding another command (e.g. ANALYZE_SETTINGS) which configures ANALYZE? Might be some confusion with name since ANALYZE is a bit vague as a function label.

The default conditions, whatever they might be, can be modified by the new command and the modifications remain in effect until the next use of the configure command or end of session. Then ANALYZE command syntax remains unchanged.

13:23 Reply: Request for comment: New ANALYZE syntax (artifact: fdbccfd475 user: crustyoz)

Would you consider adding another command (e.g. ANALYZE_SETTINGS) which configures ANALYZE? Might be some confusion with name since ANALYZE is a bit vague as a function label.

The default conditions, whatever they might, can be modified by the new command and the modifications remain in effect until the next use of the configure command or end of session. Then the ANALYZE command syntax remains unchanged.

2020-03-15
12:53 Reply: (email) Lack of paragraph wrapping in text/plain emails makes them hard to read (artifact: 3bad3235e4 user: crustyoz)
In the olden days that I remember well, mechanical typewriters 
used a 10 character per inch font. On a 8.5"x11" or A4 page with 
1" margins that allows for 65 characters on a line.

I've used that as a guide for __all__ plain text that I write, 
by pressing the __Enter__ at around that 65 character line 
length. My editor has a line width set for that without 
auto-wrap and I can use the reformat keyboard command to rewrap 
a paragraph to suit.

Replying to this thread interrupted me doing edits to 
application documentation written by me several years ago where 
that convention is followed, so it is fresh in mind.

It has the nice advantage that each line is fully readable in 
the Fossil side-by-side diff display.

Because the editor lets you write in a "stream of consciousness" 
does not mean you must use it that way.

Having written the above and clicked the __Review__ button, I am 
reminded that HTML ignores such niceties and wraps to the window 
width unless non-plain text markup is imposed. So, I enclosed 
this text in back-ticks.
2020-03-13
13:06 Reply: a css to improve readability of this forum (artifact: bddae034e5 user: crustyoz)

The proposed css is targetted at use on a cellphone. The text is too large for a desktop and leaves the right half of a wide screen empty.

On a cellphone, the text is still slightly too large but is quite readable. It wraps at the screen edges but bounding boxes are off-screen on the right side.

Clearly, there is need for media queries to make good use of this css where it is most appropriate.

The Bulma CSS library uses the following break points for its media queries:

mobile: up to 768px
tablet: from 769px
desktop: from 1024px
widescreen: from 1216px
fullhd: from 1408px

and they seem to work well in my experience with cellphone, iPad, and 1920x1200 wide screen desktop.

12:05 Reply: will the posts from the mailing list be migrated to here? (artifact: 1fa24cc4d0 user: crustyoz)

The underlying thesis of markdown is that it looks acceptable in plain text. As shown below, your text quoted here is now in markdown format. Your use of asterisk and underscore both transform to italic text. If you want bold text then use double asterisk or double underline, as here and here. The forward slash is not a recognised formatting character in markdown.

Due to the markdown assumption that without annotation, adjacent lines can be merged into one paragraph, your joke is becomes a series of in-line sentences without poetic formatting.

Two adjacent newlines separate paragraphs by presenting a blank line between paragraphs. Not sure what you mean by "Are newlines newlines in plain text" since a newline, chr(10), is valid plain text. If you are on MS-Windows then the carriage return, chr(13), will be ignored in the translation to HTML.

The linked text "Markup style" above the compose/reply textarea provides a summary of Fossil's two markup definitions.

Your previous post is copied verbatim below:

OK, I'm going to belabor this with one additional post. This one.

The first message I sent was with "markdown" as the markup style.

This message is being sent with "plain text" as the markup style.

Being thick, and content with plain ASCII, I now post this and this and /this/ to see how it will appear in the forum and also in my email client, Thunderbird.

Here's another joke: Why is 6 afraid of 7? Because 7, 8, 9, and 10. Feel free to share this joke will all your eight-year-old friends.

Are newlines newlines in plain text?

2020-03-12
23:25 Reply: will the posts from the mailing list be migrated to here? (artifact: d8ad621cb8 user: crustyoz)

Using markdown, here is what would match your plaintext email version:

Knock knock.
Who's there?
Little old lady.
Little old lady who?
I didn't know you could yodel.

The five lines have been indented by 4 spaces. This caused markdown to treat it as code.

Or, prefixed and followed by lines with 3 backticks:

Knock knock.
Who's there?
Little old lady.
Little old lady who?
I didn't know you could yodel.