LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And *every* time I want to comment two or more parts of a post, I must manually (and slowly) separate the tags from the text they quote. In my opinion, this should have been changed long ago - it even surprises me to imagine why it was coded this way.
I have never found the few seconds it takes to type quote and /quote to be slow. So in my opinion, there is no pressing need to change the forum's source code. Is reducing the time to make a post by a few seconds worth the trouble?
Personally, I am quoting in the way, that the OP favors, himself, since the 1990s, because it was obligatory in the German Usenet. Not technically imposed but you where shot, twice, if you did not...
And it is completely my own personal opinion, that this technically imposed/proposed “separate phrases, paragraphs, sections” by closing and opening quote-tags were not an improvement (I changed my wording).
The choice of “what shall be quoted” must remain my own. The current implementation of quoting on LQ is just honoring this simple fact. It does not impose anything, but lets you do the work. As it should be.
You can even remove all the styling-buttons and leave us with a list of supported tags. I will still not quarrel; and I wonder if it would not have been best to do exactly that from the start.
Cheerio.
Last edited by Michael Uplawski; 09-18-2018 at 12:51 AM.
Reason: clarification.
I understand where you say that you take a long quote and break it up using end-quote tags and re-using the start of the quote tag. I do this myself.
What are you proposing exactly?
I see: "Separated lines are very nice to make the whole process easy"
However is this not in relation to how the quoted person, wrote their post?
Here I'm writing one or two sentences per line.
I actually do this to try to make things more clear to people. This is my style.
Meanwhile, some posters may have ridiculously, lengthy run-on sentences, use little in the way of punctuation, even use their own made up terms or special colloquialisms which make their posts difficult to read. Those same posts would also be more difficult to break up and quote sections of them, but because of how the writer combined the text.
Perhaps I'm missing a correct description of what you see to be a problem?
Repositioning a tag that is in the middle of a long line of course code is harder than repositioning tags alone on lines. Further, "[]/" are not considered part of the same word when I click the tag name - harder to select means longer to do.
Typing {[]/} is not so easy in many keyboards around the world, including the standard in my country, ABNT2. And typing "[quote]" is not all I want, since I can use the "=[number]" to make the quoting much better.
LinuxQuestions is a place where several people are developers, or deal somehow with source code and configuration files. Why it has a bad (or hard) way of giving us the source code when we quote posts? Put good coding practices in these. One liners obfuscate things, and LQ fora can move away from these ideas.
And the "alt" texts are not shown to me as hover hints in Firefox. Hint is a different kind of thing, I guess, because I see hover hints in other pages.
I should have seen this coming. I am out of this thread, too.
My suggestion would really be to remove all buttons which serve to introduce tags of any kind and just list the supported tags. Ω
I should have seen this coming. I am out of this thread, too.
My suggestion would really be to remove all buttons which serve to introduce tags of any kind and just list the supported tags. Ω
The quote button is very good, in my opinion, because it keeps all the formatting and tagging a post was made with. Copying the text will not (normally and without fancy workarounds) keep those, and they are important to thread readers.
Personally, I am quoting in the way, that the OP favors, himself, since the 1990s, because it was obligatory in the German Usenet. Not technically imposed but you where shot, twice, if you did not...
And it is completely my own personal opinion, that this technically imposed/proposed “separate phrases, paragraphs, sections” by closing and opening quote-tags were not an improvement (I changed my wording).
The choice of “what shall be quoted” must remain my own. The current implementation of quoting on LQ is just honoring this simple fact. It does not impose anything, but lets you do the work. As it should be.
You can even remove all the styling-buttons and leave us with a list of supported tags. I will still not quarrel; and I wonder if it would not have been best to do exactly that from the start.
Cheerio.
I'd like to suggest an android and apple apply tag app for cell phones. seems everyone knows how to phone apps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.