LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   LQ Suggestions & Feedback (https://www.linuxquestions.org/questions/lq-suggestions-and-feedback-7/)
-   -   We need a way to "close" a thread other than [X] Solved (https://www.linuxquestions.org/questions/lq-suggestions-and-feedback-7/we-need-a-way-to-close-a-thread-other-than-%5Bx%5D-solved-4175628323/)

taylorkh 04-24-2018 09:47 AM

We need a way to "close" a thread other than [X] Solved
 
Thread tools allows a thread to be marked as solved. However, there are times when a thread ends in a "throw in the towel and go on to plan B."

I have such a thread which I started with a couple of seemingly simple questions about dnsmasq. In spite of some kind input from other members, an answer was not forthcoming. It seems that NetworkManager is getting in the middle of things and confusing the issue. Actually the NetworkManager applet is making things worse as far as a resolution.

A message to the NetworkManager mailing list got a response which informed me that one of the things I wished to do was "very difficult" with NetworkManager/dnsmasq and as to my other question... more look here, look there.

Bottom line... My LinuxQuestions thread did not provide a solution. I have moved on to plan B and do not wish to trouble anyone to attempt to answer the question. The information provided in the thread is probably of limited value as a reference; unlike a Solved thread. I think it would be valuable to be able to flag this post as... "nice try but no cigar" or something.

Ken

MensaWater 04-24-2018 10:32 AM

I think the point of the "SOLVED" is to let users searching the web know that the hit they just got contains a solution so they should look at it first among the 10,000 hits they see.

Marking it "SOLVED" here does not "close" it like it does in other forums.

Personally I don't like "closed" threads because much later other info can come to light or there may be details people later reading the thread don't know. Although I've chided people for adding irrelevant follow ups to old threads I do on occasion see the need for follow up. In fact the other day there was a thread I added a note to so that people would know it wasn't just an issue for the system the OP had described but in fact continues to be an issue for other systems.

jefro 04-24-2018 02:39 PM

There are good sides and bad sides to leaving stuff open. In general LQ is here to provide a resource. At some point someone may solve it or use the failed solutions in their search.

scasey 04-24-2018 08:05 PM

I didn't read Ken's idea as suggesting a close/locking of the thread, as you mods do with duplicate posts, for example, but a way to put some kind of header other than [Solved] on the thread with an additional thread tools option.

Two thoughts:
1) The OP (Ken in this case) could add a post to the thread to the effect of "I give up! I'm going to Plan B at <link to thread>"
2) The OP could modify the title manually.

frankbell 04-24-2018 08:25 PM

I think that "SOLVED" can be used to indicate that either fixing the problem or realizing the problem cannot be fixed, so long as the resolution is clearly indicated.

The latter is an unsatisfactory resolution, certainly, but it is still a resolution.

Just my two cents.

jeremy 04-25-2018 09:17 AM

Thanks for the feedback. A search of the LQS&F forum should provide some information about why we don't allow thread closures, but I can confirm that marking it as *SOLVED* does not close it in any way.

--jeremy

andreyssop 05-21-2018 05:31 PM

We need a way to "close" a thread other than X Solved
 
I need some help on how to close/lock the thread or remove the thread. I dont want any open replies/comments. Does anyone know how to lock the thread please?

taylorkh 05-21-2018 06:25 PM

OP here :) I have been giving this some more thought and reading the various replies.

"CLOSED" is not really what I meant - sorry if I was not clear. "DEAD END" might more what I am looking for. I tend to post questions in part to help me clarify what I am trying to do. Often times I will figure out the answer while composing the post because I have forced myself to think clearly.

Sometimes I may post a question which I have not fully thought through - often out of frustration. Based on the sage advice of other members it may sink into my brain that the answer was to ask the right question. The thread could not provide a solution as I had not described a valid problem. In other words is is rubbish. I would like to be able to flag these so others would not spend time trying to understand something meaningless.

Ken

ferrari 05-21-2018 07:56 PM

Perhaps 'INCONCLUSIVE' would also fit here.

Michael Uplawski 05-29-2018 02:42 AM

[Non-Problem] See there
 
Quote:

Originally Posted by ferrari (Post 5857728)
Perhaps 'INCONCLUSIVE' would also fit here.

Might it help to give the OP the authorization to modify an original thread-title, even after some time has passed? No extra functionality would have to be provided, no new action-links nor buttons. Keep it simple.

In a phpbb-thingy somewhere, I use to add indications like [ignore] or [not reproducible] or [for later] or [solved in release xx.x].

taylorkh 05-29-2018 05:27 AM

An excellent idea. I have on occasion marked a thread Solved and then found out that what I though was fixed was not really fixed.

Ken


All times are GMT -5. The time now is 09:04 AM.