Written by lrslei the 3 Oct 12 at 09:47.

The usage of an appropriate behaviour of ayatana-scrollbar (like hovering) may help users to notice in which line they are during these in-text word searches.

This mockup should clarify;
http://ubuntuone.com/6PMEYqg4nr0WVDthBPtF9m

Sorry for my bad english

The usage of an appropriate behaviour of ayatana-scrollbar (like hovering) may help users to notice in which line they are during these in-text word searches. This mockup should clarify; http://ubuntuone.com/6PMEYqg4nr0WVDthBPtF9m Sorry for my bad english

Written by pedro6893 the 1 Nov 12 at 00:26.

If technically possible, there could be lines on the scrollbar indicating the position of matches through the document. We could put small, single pixel high, markings in every point of the scrollbar where there is a match to create a map of the search term occurrence.

Google chrome already implements this functionality and I find it very useful, this way I know where in the document am I and where are the other matches.

Ilustration: http://assets.techdreams.org/wp-content/uploads/2008/09/google-chrome-scrollbar -higlighting.png

If technically possible, there could be lines on the scrollbar indicating the position of matches through the document. We could put small, single pixel high, markings in every point of the scrollbar where there is a match to create a map of the search term occurrence. Google chrome already implements this functionality and I find it very useful, this way I know where in the document am I and where are the other matches. Ilustration: http://assets.techdreams.org/wp-content/uploads/2008/09/google-chrome-scrollbar-higlighting.png

Written by oldarney the 20 Aug 11 at 10:42.

Wouldn't it be nice if noobs always saw the manual for the commands they type in? Running man on everything usually does the trick. It would also encourage better documentation.
You would only be asked "Are you a noob?" once, when you first install ubuntu.

Wouldn't it be nice if noobs always saw the manual for the commands they type in? Running man on everything usually does the trick. It would also encourage better documentation. You would only be asked "Are you a noob?" once, when you first install ubuntu.

Written by oldarney the 20 Aug 11 at 10:49.

When you start typing "chm", hitting tab autocompletes to "chmod", it would be nice if it showed what TAB would do before you pressed it. It would be in an onion skin style and be as unobtrusive as possible.

When you start typing "chm", hitting tab autocompletes to "chmod", it would be nice if it showed what TAB would do before you pressed it. It would be in an onion skin style and be as unobtrusive as possible.

Written by oldarney the 20 Aug 11 at 10:59.

Make bad commands look mispelled before pressing enter.
Kinda like firefox spell checking.

http://lifehacker.com/assets/resources/2007/05/misspelling.png

Make bad commands look mispelled before pressing enter. Kinda like firefox spell checking. http://lifehacker.com/assets/resources/2007/05/misspelling.png

Written by oldarney the 20 Aug 11 at 11:05.

1.Shake the Terminal when you get a 'command not found'
2.Cause overscroll to bounce (optional)
3.Auto highlight selected text, like eclipse
4.Old Sci-fi "CRT monitor from space style" effect option

1.Shake the Terminal when you get a 'command not found' 2.Cause overscroll to bounce (optional) 3.Auto highlight selected text, like eclipse 4.Old Sci-fi "CRT monitor from space style" effect option

Written by oldarney the 20 Aug 11 at 14:50.

You know how, when you search google you get a dropdown list of things people search for commonly? Why not make a small database of those commands and add real suggestions to the terminal! This would bring an end to ALL linux noobs! MWUHAHAHHA It would almost make it too easy to use the terminal.

http://www.holytaco.com/25-funny-google-search-suggestions/

You know how, when you search google you get a dropdown list of things people search for commonly? Why not make a small database of those commands and add real suggestions to the terminal! This would bring an end to ALL linux noobs! MWUHAHAHHA It would almost make it too easy to use the terminal. http://www.holytaco.com/25-funny-google-search-suggestions/

Written by Carbonated Coffee the 25 Aug 11 at 05:41.

EDIT: Z-shell with the .zshrc file I posted, that command below, enables pre-execution spellchecks, auto-completes program names, nices foreground tasks and for further clarification, provides "Lists" when you press the "Tab" key. As said below, you can press tab on kill, cd, rm etc. and have a list of files in the current directory or processes to look at.)

Z-shell, known as zsh in the ubuntu repositories, can be configured to have spellcheck, and easier file navigation through it.

The Bourne Again shell was suppose to make life for script developers easy, as it combined the best of Korn, Bourne and C shell. Z-shell can utilize most of the same stuff, and with a decently-coded .zshrc file, it can have curses-like menus for commands like kill and cd, integrating easy-to-use inline menus in the terminal window.

Additionally, if a GUI were built around it, then customization would be as easy as running a Python script, navigating the GUI and restarting Terminal to apply changes. And since it's the entire shell that's being replaced, the same ease of use that would be in gnome-terminal would also be in xterm.

Don't believe me? then copypaste the following in a terminal window and check it out:
sudo apt-get install zsh curl && curl http://stuff.mit.edu/~jdong/misc/zshrc > ~/.zshrc && zsh

EDIT: Z-shell with the .zshrc file I posted, that command below, enables pre-execution spellchecks, auto-completes program names, nices foreground tasks and for further clarification, provides "Lists" when you press the "Tab" key. As said below, you can press tab on kill, cd, rm etc. and have a list of files in the current directory or processes to look at.) Z-shell, known as zsh in the ubuntu repositories, can be configured to have spellcheck, and easier file navigation through it. The Bourne Again shell was suppose to make life for script developers easy, as it combined the best of Korn, Bourne and C shell. Z-shell can utilize most of the same stuff, and with a decently-coded .zshrc file, it can have curses-like menus for commands like kill and cd, integrating easy-to-use inline menus in the terminal window. Additionally, if a GUI were built around it, then customization would be as easy as running a Python script, navigating the GUI and restarting Terminal to apply changes. And since it's the entire shell that's being replaced, the same ease of use that would be in gnome-terminal would also be in xterm. Don't believe me? then copypaste the following in a terminal window and check it out: sudo apt-get install zsh curl && curl http://stuff.mit.edu/~jdong/misc/zshrc > ~/.zshrc && zsh And to perma-replace it at the user level: sudo chsh -s /bin/zsh

Written by Lachu the 9 Sep 11 at 11:38.

Allow to remember command you type into terminal with ability to select parameters. This option would be useful to make bookmarks. Gnome-terminal should have this option. Gnome-terminal should have many bookmarks pre-installed, like remove file, cd, etc.

Allow to remember command you type into terminal with ability to select parameters. This option would be useful to make bookmarks. Gnome-terminal should have this option. Gnome-terminal should have many bookmarks pre-installed, like remove file, cd, etc.

Written by Ronius the 17 Sep 11 at 19:30.

Regular users of the terminal are unlikely to be too pleased with changes that get in the way with what they're used to doing. New users are also likely to be frightened off by the coldness of a new terminal window.

Maybe what is needed is a program aimed at teaching those new to the terminal how to use it? This program would include auto-complete for new words, and a split-panel that will automatically come up with the help and manual for the command used once the return key is pressed. Also any other combination of the solutions here could be added to it.

Regular users of the terminal are unlikely to be too pleased with changes that get in the way with what they're used to doing. New users are also likely to be frightened off by the coldness of a new terminal window. Maybe what is needed is a program aimed at teaching those new to the terminal how to use it? This program would include auto-complete for new words, and a split-panel that will automatically come up with the help and manual for the command used once the return key is pressed. Also any other combination of the solutions here could be added to it.

Written by brk0_0 the 19 Sep 11 at 18:07.

Emilis Dambauskas @ GitHub proposed and made a teak that make a separator line between commands:

http://lifehacker.com/5840450/add-a-handy-separator-between-commands-in-your-te rminal-on-mac-os-x-and-linux

This would be great for improving usability and accessibility of terminal in Ubuntu.

This is how it looks like:
http://fastcache.gawkerassets.com/assets/images/17/2011/09/terminalseparators.p ng

Emilis Dambauskas @ GitHub proposed and made a teak that make a separator line between commands: http://lifehacker.com/5840450/add-a-handy-separator-between-commands-in-your-terminal-on-mac-os-x-and-linux This would be great for improving usability and accessibility of terminal in Ubuntu. This is how it looks like: http://fastcache.gawkerassets.com/assets/images/17/2011/09/terminalseparators.png

Written by inder.vs the 2 Oct 11 at 07:20.

like in many programming software where one never need to learn all the commands.

like in many programming software where one never need to learn all the commands.

Written by michael.j.daniel the 4 Oct 11 at 08:00.

Have a Wiki where each page corresponds to a terminal command. Each page contains a list of pairs. The first item in the pair is an English command, ie, "Where is file foo on my computer?" The second item of the pair is the Linux translation of the English command, ie, "Find / -name foo -print". When using a terminal, search and find, in the wiki, the English command you want. Then type the corresponding Linux translation into the terminal.

Advantages:
Keeps the shell and tools small; this is a trouble shooting necessity.
Get exact, correct command to enter, every time.
Don't need to read man pages.
Less code to create, test, and maintain.
fewer bugs to find, document, and fix.
Ordinary users can help create wiki.
Can easily be developed incrementally and in parallel.
The wiki can help create standardized tests for the commands.

This is already happening at https://wiki.ubuntu.com/TranslateEnglishToLinux

Have a Wiki where each page corresponds to a terminal command. Each page contains a list of pairs. The first item in the pair is an English command, ie, "Where is file foo on my computer?" The second item of the pair is the Linux translation of the English command, ie, "Find / -name foo -print". When using a terminal, search and find, in the wiki, the English command you want. Then type the corresponding Linux translation into the terminal. Advantages: Keeps the shell and tools small; this is a trouble shooting necessity. Get exact, correct command to enter, every time. Don't need to read man pages. Less code to create, test, and maintain. fewer bugs to find, document, and fix. Ordinary users can help create wiki. Can easily be developed incrementally and in parallel. The wiki can help create standardized tests for the commands. This is already happening at https://wiki.ubuntu.com/TranslateEnglishToLinux

Written by michael.j.daniel the 13 Oct 11 at 17:42.

Create a new shell, "Ensh" for instance, that accepts questions and commands in simple English and processes them, answering the questions and carrying out the commands.

Create a new shell, "Ensh" for instance, that accepts questions and commands in simple English and processes them, answering the questions and carrying out the commands.

Written by deltrem the 20 Jan 12 at 20:26.

I want two buttons: Share Commands and See Commands.

1. I click Share
2. select some commands that I have just typed
3. write a description for the commands
4. the commands and their description go to an Ubuntu moderation
5. if the moderation approves, they appear in the See Commands of people who have the same computer configuration / hardware as I have.

I want two buttons: Share Commands and See Commands. 1. I click Share 2. select some commands that I have just typed 3. write a description for the commands 4. the commands and their description go to an Ubuntu moderation 5. if the moderation approves, they appear in the See Commands of people who have the same computer configuration / hardware as I have.

Written by pascalio the 16 Dec 11 at 15:58.

Show a more objective indicator as well (perhaps within brackets), such as the percentage of the battery that is remaining, as it can be found if you travel to the history tab of the power statistics.

Show a more objective indicator as well (perhaps within brackets), such as the percentage of the battery that is remaining, as it can be found if you travel to the history tab of the power statistics.

Written by ross9885 the 24 Dec 11 at 19:10.

Graph battery voltage and current draw in the System Monitor and it's applet. Allow the user the opportunity to figure out clever ways of conserving power based on real data from their machine.

Graph battery voltage and current draw in the System Monitor and it's applet. Allow the user the opportunity to figure out clever ways of conserving power based on real data from their machine.

Written by addiks the 14 Jan 13 at 12:53.

What i currently do to achieve that goal is that i use the program 'ginn' with a custom 'whiches.xml' file. But ginn does not work with the vanilla (raw/untouched) version of unity, because unity grabs and locks the root multitouch handle(s) of the system. To resolve that i have written a script which downloads ('apt-get source unity') the unity sources, patches the sources to disable multitouch, build the packages and installs them. (I have also patched ginn, but that again is another story. I can provide the whole patcher-package if someone is interested.)

That process is very annoying because everytime unity gets updates i have to kill ginn (otherwise the updated/unpatched unity crashes after update because it cannot grab MT), update unity, run the patcher und do a 'unity --replace', all manually.

The cheapest solution would be to provide a configuration in a file or even a simple flag-file that disables multitouch in unity completely. You would create a file '~/.unity/disableMultitouch.flag' and the problem is gone, unity does not use multitouch anymore. You can run whatever multitouch program you want to.

This solution also would not interfere with beginners because they would never get the idea to create such a file. Its just a helper for developers who like to customize their system.

The file that needs to be patched for this to work is in the 'unity' package, in the sources the file '/plugins/unityshell/src/unityshell.cpp' in the method UnityScreen::InitGesturesSupport (currently line 3383-3407).

What i currently do to achieve that goal is that i use the program 'ginn' with a custom 'whiches.xml' file. But ginn does not work with the vanilla (raw/untouched) version of unity, because unity grabs and locks the root multitouch handle(s) of the system. To resolve that i have written a script which downloads ('apt-get source unity') the unity sources, patches the sources to disable multitouch, build the packages and installs them. (I have also patched ginn, but that again is another story. I can provide the whole patcher-package if someone is interested.) That process is very annoying because everytime unity gets updates i have to kill ginn (otherwise the updated/unpatched unity crashes after update because it cannot grab MT), update unity, run the patcher und do a 'unity --replace', all manually. The cheapest solution would be to provide a configuration in a file or even a simple flag-file that disables multitouch in unity completely. You would create a file '~/.unity/disableMultitouch.flag' and the problem is gone, unity does not use multitouch anymore. You can run whatever multitouch program you want to. This solution also would not interfere with beginners because they would never get the idea to create such a file. Its just a helper for developers who like to customize their system. The file that needs to be patched for this to work is in the 'unity' package, in the sources the file '/plugins/unityshell/src/unityshell.cpp' in the method UnityScreen::InitGesturesSupport (currently line 3383-3407).

Written by addiks the 21 Jan 13 at 18:10.

As an alternative to a text-file or flag-file configuration (which isn't very beginners-friendly), there could be a way to configure and/or disable multitouch in the GUI system-settings like with the current custom keyboard shortcuts and a simple switch (checkbox, button, slider, ...) to disable multitouch in unity completely so another multitouch-program like ginn can be used. This is not as cheap to implement as #1 but the result would be easier to use for everyone.

As an alternative to a text-file or flag-file configuration (which isn't very beginners-friendly), there could be a way to configure and/or disable multitouch in the GUI system-settings like with the current custom keyboard shortcuts and a simple switch (checkbox, button, slider, ...) to disable multitouch in unity completely so another multitouch-program like ginn can be used. This is not as cheap to implement as #1 but the result would be easier to use for everyone.

Written by Porky the 1 Nov 12 at 21:39.

Add a button in one of the submenus of the system settings that enables the user to toggle on/off the saving of the results filtering between sessions.

Add a button in one of the submenus of the system settings that enables the user to toggle on/off the saving of the results filtering between sessions.

Written by AndrewLuecke the 6 May 12 at 12:36.

When running an app:
1) Capture Stderr.
2) Analyse Stderr for missing libraries problem.
3) If something was missing, scan packagekit for the file, offer to install it. ("Libsdl.so.1 is missing, would you like to install LibSDL?")
4) Relaunch the app.

Benefits:
1) VERY easy to develop
2) Allows Ubuntu to self diagnose app launching problems.
3) Far better backwards compatibility.
4) Tar.gz's will be easier to run.

When running an app: 1) Capture Stderr. 2) Analyse Stderr for missing libraries problem. 3) If something was missing, scan packagekit for the file, offer to install it. ("<a href="#">Libsdl.so.1 is missing, would you like to install LibSDL?"</a>) 4) Relaunch the app. Benefits: 1) VERY easy to develop 2) Allows Ubuntu to self diagnose app launching problems. 3) Far better backwards compatibility. 4) Tar.gz's will be easier to run.

Written by LSenf the 11 May 12 at 13:44.

Just as #1, but instead of monitoring console output, the cleaner solution should be to handle the error directly in the linker (or whatever causes these errors ;) ).

The linker itself could then call another program handling the user dialogs, installation proposals etc.

Furthermore, the second program should also offer a console interface in case the error occurs in a non-graphical environment.

Just as #1, but instead of monitoring console output, the cleaner solution should be to handle the error directly in the linker (or whatever causes these errors ;) ). The linker itself could then call another program handling the user dialogs, installation proposals etc. Furthermore, the second program should also offer a console interface in case the error occurs in a non-graphical environment.

Written by Леонид the 29 May 12 at 08:14.

1. Search in current layout.
2. If no found, switch text to next layout ("wdtn"->"цвет") and search again.
3. Repeat for all system layouts.

1. Search in current layout. 2. If no found, switch text to next layout ("wdtn"->"цвет") and search again. 3. Repeat for all system layouts.

Written by yogeshsehgal99 the 14 Sep 12 at 18:48.

As the picture makes the login screen more attractive and makes the user feel it could be easy like windows!
This problem is reported by many of the Ubuntu users on net
Add the picture in login screen to promote open source

As the picture makes the login screen more attractive and makes the user feel it could be easy like windows! This problem is reported by many of the Ubuntu users on net Add the picture in login screen to promote open source

Written by kundan.thakur the 6 Oct 12 at 06:38.

sometimes we just start the pc and go off in the kitchen to bring our cup of coffee so if a song or video plays in the background until login takes place that will be a good addition to ubuntu. of course it must be user selected .
Or may be news from web in the background of the login window.
its asking too much i know

sometimes we just start the pc and go off in the kitchen to bring our cup of coffee so if a song or video plays in the background until login takes place that will be a good addition to ubuntu. of course it must be user selected . Or may be news from web in the background of the login window. its asking too much i know

Written by ceti331 the 5 Mar 13 at 19:32.

Quick Solution,Idea [1] Put "Workspace Switcher" inplace of the trashcan. The trashcan is rarely used (cleanup), wheras workspace-switcher is hugely useful to see an overview and manage current tasks. Put the trashcan as part of the scrollable launcher list.
ubuntus' "Workspace Switcher" should be in the corner just like Windows' "show-desktop"

[1.1] make the "Workspace Switcher" respond to scrollwheel events (prev/next desktop), when its in the corner

Idea [2]make the top-left and bottom right of the launcher special locations where the user can dock any item

Idea [3] remove the 'close,minimise,maximize' buttons from the top for a maximized application - replace with Window Menu ,or a drop-down window-list - (you rarely want to close the maximized app, hiding it may be more common.)

Idea [4] put previous/next desktop icons in the topleft, topright of the top panel- a little like E16 window-manager

idea [5] generally turn the window-title into a dropdown-list of all open windows , as another form of workspace switching

Quick Solution,Idea [1] Put "Workspace Switcher" inplace of the trashcan. The trashcan is rarely used (cleanup), wheras workspace-switcher is hugely useful to see an overview and manage current tasks. Put the trashcan as part of the scrollable launcher list. ubuntus' "Workspace Switcher" should be in the corner just like Windows' "show-desktop" [1.1] make the "Workspace Switcher" respond to scrollwheel events (prev/next desktop), when its in the corner Idea [2]make the top-left and bottom right of the launcher special locations where the user can dock any item Idea [3] remove the 'close,minimise,maximize' buttons from the top for a maximized application - replace with Window Menu ,or a drop-down window-list - (you rarely want to close the maximized app, hiding it may be more common.) Idea [4] put previous/next desktop icons in the topleft, topright of the top panel- a little like E16 window-manager idea [5] generally turn the window-title into a dropdown-list of all open windows , as another form of workspace switching

Written by ceti331 the 5 Mar 13 at 19:38.

Put additional hooks for clicks in the screen corners
see amiwm, windows8 and pekWM for inspiration (although pekwm uses screen-edges).
"amiwm"& win8 uses clicks in the topright to switch desktops.
if the user could bind this to any function it would help.

Put additional hooks for clicks in the screen corners see amiwm, windows8 and pekWM for inspiration (although pekwm uses screen-edges). "amiwm"& win8 uses clicks in the topright to switch desktops. if the user could bind this to any function it would help.

Written by PaddyLandau the 18 Mar 13 at 17:26.

At the moment, the bottom of the Launcher is a special area, which contains only the Trash.

Allow the user to decide which icons go there (only the Trash by default). So:

The bottom of the Launcher would become similar to the top, where:

* You can move icons to the bottom (from the top);
* Move icons from the bottom (to the top);
* Unlock icons;
* Change the order of the icons.

I would suggest that a separator be placed between the top and bottom parts to make them clearly distinguishable from each other.

At the moment, the bottom of the Launcher is a special area, which contains only the Trash. Allow the user to decide which icons go there (only the Trash by default). So: The bottom of the Launcher would become similar to the top, where: * You can move icons to the bottom (from the top); * Move icons from the bottom (to the top); * Unlock icons; * Change the order of the icons. I would suggest that a separator be placed between the top and bottom parts to make them clearly distinguishable from each other.

Written by mayanksuman the 4 Apr 13 at 10:32.

Minimum Hover time after which the list of screenlets parallel to the unity sidebar appear should be specified in appearnace setting (default may be 0.5second). If the window list is too long the list should slide as the mouse pointer is taken to upper or lower portion of the list or just by using mouse wheel.

Minimum Hover time after which the list of screenlets parallel to the unity sidebar appear should be specified in appearnace setting (default may be 0.5second). If the window list is too long the list should slide as the mouse pointer is taken to upper or lower portion of the list or just by using mouse wheel.