[SOLVED] Number of characters permitted in a thread title
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.
Copy the contents of a txt file to other txt files (with similar names) by cp command
I had to spend 10 minutes in making the above statement fit in as the thread title,
I wanted it like this:
Quote:
How to copy the contents of a text file to other text files (with similar names) through the cp command
Other members may not be facing this problem, fine,
but still, any chances of increasing the permitted characters in the thread title ? (w.r.t the following quote)
Quote:
Please try to be as descriptive as possible. A subject that accurately describes your problem will make your thread much more likely to get a quick response.
Also descriptive doesn't mean you can't use -Z or --compress: '"cp" text file contents to other text files how?'. 41 chars, that and a pretty much OK description.
Do you really think it will waste too much space on LQ if you just permit x/2 more characters in the title (assuming x to be the number of characters currently permitted) ?
I don't think space (or what I think) really is the issue here (other than forum software settings versus screen estate) but people in general not giving finding fitting thread titles much thought. Then again I'm not the average user nor can I say anything authoritatively wrt these things but I'm sure that if a hundred unique LQ members or so file a bug report about this that it would warrant more attention.
How to copy the contents of a text file to other text files (with similar names) through the cp command
cp text_file text_file_with_similar_name
Surely the similarity of names does not affect this. Computers don't understand "similar", it's either the same file of it's a different file.
Also, the fact that it's a text file doesn't matter. cp just copies the data exactly, no matter what it is.
If you meant that the other files already exist, then remember that cp clobbers any existing destination files by default. If you have an alias or something that says it not to, use the -f option.
In the end, why not call it "How to copy files?" or "How to use the cp command?"?
The title of the thread doesn't have to include everything important about the question; it just needs to include enough so that the readers understand the general topic of the discussion, and can reasonably decide whether they might have the expertise to provide help in that area.
In other words, the main criterion I use when deciding which threads to click on is "do I know anything about this subject?" If I think I do, I'll check it out, if not, I'll pass on it. If the subject is too vague to tell, then it depends entirely on my mood at the time.
Speaking of which, the "through the cp command" part of the above is really the wrong way go about asking the question anyway. Unless you have some very specific reason for using that one command, it's generally better to simply state what you want to accomplish, and leave the how part of it to the discussion itself. Quite often the best solution will have nothing to do with the method the OP thinks should be used.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.