Proposal: "Do not treat <'s as HTML tags" set on by default
-
A significant percentage of newbie posters systematically forget to check this option on, so that their snippets of code are unreadable. My proposal tries to remedy this while having the least impact on more seasoned users:
- This option is a user profile dependent config option.
- Existing users keep their status quo (i.e. the option is initially set off for them.)
- Starting from the date the patch is applied, new users will have the option set on by default.
- Every time an user posts a message, the option used (set on/set off) gets saved to her profile as the default for subsequent posts.
What do you think of this? Regards Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
-
A significant percentage of newbie posters systematically forget to check this option on, so that their snippets of code are unreadable. My proposal tries to remedy this while having the least impact on more seasoned users:
- This option is a user profile dependent config option.
- Existing users keep their status quo (i.e. the option is initially set off for them.)
- Starting from the date the patch is applied, new users will have the option set on by default.
- Every time an user posts a message, the option used (set on/set off) gets saved to her profile as the default for subsequent posts.
What do you think of this? Regards Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
good idea for me the best solution would be that the parser will not handle html tags inside the
and
sections -
good idea for me the best solution would be that the parser will not handle html tags inside the
and
sectionsI wouldn't like to be deprived of the possibility of embedding tags inside <pre> sections. It allows me to write things like: Change the function declaration to
extern object clone(const object& x);
Furthermore, newbies usually paste the code without any <pre> (they probably don't know this can be used.) Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
-
A significant percentage of newbie posters systematically forget to check this option on, so that their snippets of code are unreadable. My proposal tries to remedy this while having the least impact on more seasoned users:
- This option is a user profile dependent config option.
- Existing users keep their status quo (i.e. the option is initially set off for them.)
- Starting from the date the patch is applied, new users will have the option set on by default.
- Every time an user posts a message, the option used (set on/set off) gets saved to her profile as the default for subsequent posts.
What do you think of this? Regards Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
This is an excellent suggestion Joaq! Nish
Extending MFC Applications with the .NET Framework [NW] (coming soon...) Summer Love and Some more Cricket [NW] (My first novel) Shog's review of SLASMC [NW] My photography efforts on Usefilm [NW] Come with me if you want to live
This post was made from Trivandrum city, India on a 0.0001 KB/s net connection
-
I wouldn't like to be deprived of the possibility of embedding tags inside <pre> sections. It allows me to write things like: Change the function declaration to
extern object clone(const object& x);
Furthermore, newbies usually paste the code without any <pre> (they probably don't know this can be used.) Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
Again, a very valid point. Even I sometimes mark part of the code inside a pre block as bold Nish
Extending MFC Applications with the .NET Framework [NW] (coming soon...) Summer Love and Some more Cricket [NW] (My first novel) Shog's review of SLASMC [NW] My photography efforts on Usefilm [NW] Come with me if you want to live
This post was made from Trivandrum city, India on a 0.0001 KB/s net connection