[SOLVED] LISTS Function broken by [*]

andrew.comly · 07-24-2017, 08:43 AM

LISTS
I would like to use your site's list function to create a multilayed list within a post (linux questions.org):

1. declare array
2. assiagn array
3. List all elements in array - Usually write array[@]; but array[*] OK too
4. display 1st element of array
5. pass array to function

a. trait one

b. trait two

Attempt 01:

declare array
assiagn array
List all elements in array - Usually write array[@]; but array
OK, too.
display 1st element of array
pass array to function
1. trait one
2. trait two

This fails because of the "but array[*] OK, too." code, more specifically because "[*]" ends up triggering a new list item.

How does one escape a certain subsection of the {Left Bracket}LIST=1]...[/LIST]codeblock?

Attempt 02:
A workaround is closing the list and then recontinuing the list later on:

declare array
assign array
List all elements in array - Usually write array[@]; but

array[*] OK, too.

(Hopefully this will start counting from "4".)
display 1st element of array
pass array to function
1. trait one
2. trait two

But alas, no. Even though "=4", still the list starts back up again from 1. And the "array[*] OK, too." segment is on it's own line, not where it should be, which is on the end of the above line.

How do we do this??

rtmistler · 07-25-2017, 09:01 AM

Quote:

Originally Posted by andrew.comly

LISTS
I would like to use your site's list function to create a multilayed list within a post (linux questions.org):

1. declare array
2. assiagn array
3. List all elements in array - Usually write array[@]; but array[*] OK too
4. display 1st element of array
5. pass array to function

a. trait one

b. trait two

Attempt 01:

declare array
assiagn array
List all elements in array - Usually write array[@]; but array
OK, too.
display 1st element of array
pass array to function
trait one
trait two

This fails because of the "but array[*] OK, too." code, more specifically because "[*]" ends up triggering a new list item.

How does one escape a certain subsection of the {Left Bracket}LIST=1]...[/LIST]codeblock?

Attempt 02:
A workaround is closing the list and then recontinuing the list later on:

declare array
assign array
List all elements in array - Usually write array[@]; but

array[*] OK, too.

(Hopefully this will start counting from "4".)
display 1st element of array
pass array to function
trait one
trait two

But alas, no. Even though "=4", still the list starts back up again from 1. And the "array[*] OK, too." segment is on it's own line, not where it should be, which is on the end of the above line.

How do we do this??

I'm thinking a couple of things here about your post:

It should maybe be in LQ Suggestions and Feedback?
1. It seems to be asking how to form multi-layer lists using the BBCodes for the site
2. But then it discusses using bash like notation
Are you proposing a change to LQ?
Are you asking how to use the existing LQ features?
Are you saying you cannot accomplish a sub-list and have the first list continue?

Can you please clarify your question?

[list=1][*]It should maybe be in LQ Suggestions and Feedback?[list=a][*]It seems to be asking how to form multi-layer lists using the BBCodes for the site[*]But then it discusses using bash like notation[/list][*]Are you proposing a change to LQ?[*]Are you asking how to use the existing LQ features?[*]Are you saying you cannot accomplish a sub-list and have the first list continue?[/list]

andrew.comly · 07-25-2017, 11:56 PM

ISSUE 1:

Quote:

Originally Posted by rtmistler

Can you please clarify your question?

I sure wish I could do better in asking clearer questions, but every time I re-read the xy question article, I still just can't do a better job.

ISSUE 2:

Quote:

Originally Posted by rtmistler

I'm thinking a couple of things here about your post:[list=1]...

It seems to be asking how to form multi-layer lists using the BBCodes for the site

Yes, I am asking how to form multi-layer lists using the LinuxQuestions markdown codes. You have mentioned "BB Codes"! That's interesting term, may I verify that "BB Codes" is the official term to describing the below site coding methods?

Underline
{left bracket}U]...[/U]

List
{left bracket}list]...{left bracket}/list]

URL link
{left bracket}URL=https://...php]link title here[/URL]

ISSUE 3:

Quote:

Originally Posted by rtmistler

...
...
Are you asking how to use the existing LQ features?
Are you saying you cannot accomplish a sub-list and have the first list continue?

Yes, I would like to learn how to use current features. More specifically, even though I am fully capable of making a two tiered lists, I don't know how to escape the new item code "[*]".

Quote:

Originally Posted by rtmistler

...
1. ...
2. But then it discusses using bash like notation
...

I guess the sample list I made wasn't the absolute most simple example I could have made. Perhaps would the following be better?

Sample list

First {How do I get rid of this annoying blank line between the title of the list "Sample list" and this current 1st item "First"?} **Question 2
Second
Third
1. The letter A (I would like to write a {left bracket} {star} {right bracket} here!) **Question 1
2. The letter B
Fourth
Fifth

Question 1: The letter A (I would like to write a {left bracket} {star} {right bracket} here!), hence the title lists function broken by "[*]".
Question 2: Why the extra blank line between the title of the list ("Sample list") and the 1st item ("First")?

andrew.comly · 07-26-2017, 12:06 AM

Quote:

Originally Posted by rtmistler

[indent][color=green][list=1][*]It should maybe be in LQ Suggestions and Feedback?...

hmmm...

This BBcode looks quite interesting

Quote:

{left bracket}noparse][list=1][*]It should maybe be in LQ Suggestions and Feedback?{left bracket}/noparse]

Eureka!
"noparse" means the same as "\"(backward slash) does in bash or sed!! It escapes the automatic processing of the special characters! This answers Question 1

e.g.
Solution:
Sample list

First
Second
Third
1. The letter A [*]
2. The letter B
Fourth
Fifth

andrew.comly · 07-26-2017, 12:18 AM

Question 3:
How can I make a same line indentation. i.e. when I use Name {left bracket}indent]description[/indent], the description runs down to the next line. How do I make tabs/indents and still remain on the same line?

e.g.
NAME{space}{space}{space}{space}{space}{space}{space}{space}Definition
Apple{space}{space}{space}{space}{space}{space}{space}{space}a fruit containing pectin.

e.g. C langage: printf
prinf("a\sb",var1) **\s space, \t tab, \n newline

e.g. MathJax
To add more space, use \, for a
thin space a b ; \; for a wider space a b. \quad and \qquad are large spaces: a b , a
b .

andrew.comly · 07-26-2017, 04:16 AM

I found the reference for BB Code.

So I guess by the above reference there is no answer to question 2. But what about question 3?

rtmistler · 07-26-2017, 07:06 AM

Quote:

Originally Posted by andrew.comly

I found the reference for BB Code.

So I guess by the above reference there is no answer to question 2. But what about question 3?

The BB Codes weren't designed to account for every single possibility.

I understand your desired intention, however the only ways I know of to do that using the LQ web interface are;

Manually type using spaces, running the slight risk that variable sized fonts may alter things in appearance. However the LQ site seems to work OK for me if I do that intentionally
Same as above, however put it all within [code] blocks because the use of [code] BB Codes around something, preserves the formatting and this may preserve the spacing a bit better and use a fixed font since that's how code is best shown.

I'll move this thread to the S&F forum because I can see now that it really is about how to use LQ site features. Perhaps Jeremy may add to the answer.

andrew.comly · 07-27-2017, 11:31 PM

Quote:

Originally Posted by rtmistler

The BB Codes weren't designed to account for every single possibility.

I guess sometimes I can be too curious.

Moreover, I finally found the BB Codes link!!

Thus, the essential questions have been answered, THANKS SO MUCH for your patience!