After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 698735 - No documentation for Terminal reset option
No documentation for Terminal reset option
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: docs
git master
Other All
: Normal normal
: ---
Assigned To: Maintainers of Gnome user documentation
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-24 13:42 UTC by Sindhu S
Modified: 2014-02-06 20:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch updated (5.37 KB, patch)
2014-02-06 12:55 UTC, Baptiste Mille-Mathias
none Details | Review

Description Sindhu S 2013-04-24 13:42:30 UTC
Currently there exists no documentation for Terminal reset and reset & clear options. Page: pref-reset.page.stub must be written. Thanks!
Comment 1 Baptiste Mille-Mathias 2014-01-30 17:18:22 UTC
Hi There,

I saw there is actually a page with some content (but still as a stub).
I would say this topic doesn't belong to preferences but rather to troubleshooting section. I've rename it to prob-reset.page, updated it a bit and changed the link to the guide page to point to troubleshooting.

the page is still a stub, so could you have a look and validate ?

changes commited as c1b12f69f466c62ba0c5259ad0b5a354fca0276a

https://git.gnome.org/browse/gnome-terminal/commit/?id=c1b12f69f466c62ba0c5259ad0b5a354fca0276a
Comment 2 Sindhu S 2014-01-30 17:27:09 UTC
(In reply to comment #1)
> Hi There,
> 
> I saw there is actually a page with some content (but still as a stub).
> I would say this topic doesn't belong to preferences but rather to
> troubleshooting section. I've rename it to prob-reset.page, updated it a bit
> and changed the link to the guide page to point to troubleshooting.
> 
> the page is still a stub, so could you have a look and validate ?

I ran a yelp-check validate, everything looks good.
thank you for writing this. I have 2 tiny nitpicks about content:

I would rewrite this paragraph - "After reading a binary file by mistake, or launching a command, it can happen the Terminal screen is unresponsive, has strange letters printed or does not work anymore."

as "If you read a binary file in Terminal, your terminal could become unresponsive and/or be filled with junk characters..."

Also "to obtain the prompt" is required as we _are_ giving the user instructions to recover the prompt. 

I don't understand the tip, could you perhaps rewrite it?

Thanks again for your work.
Comment 3 Baptiste Mille-Mathias 2014-02-06 12:55:52 UTC
Created attachment 268288 [details] [review]
Patch updated

Updated patch.

- Rename the stub to a page
- Tweak the sentence, but didn't take your work (Junk seems to me not the right word to use)
- Put "to obtain the prompt" first
- Add some context for the tip.
Comment 4 Baptiste Mille-Mathias 2014-02-06 20:20:37 UTC
I pushed the page as we are in development, we will have time to correct.

Cheers.

commit 2d082c4443ea85bf4a63954e6242ae00765cf407
Author: Baptiste Mille-Mathias <baptistem@gnome.org>
Date:   Thu Feb 6 13:44:55 2014 +0100

    Finish the reset terminal page.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.