Doug McMahon wrote > there is in the release notes, not sure this 'qualifies'
I suppose that's the same as "changelog"? As in what you get when using the Update Manager? That functionality is of course already present, but I was thinking more along the lines of a mechanism that makes it easy for an application to issue a one time popup or notification of some sort to alert the user about a change that they otherwise would be totally unaware of, such as this "bug". Perhaps it's not a bug because it is intended functionality (and realistically not a big deal), but it becomes a issue when it can be logically assumed that people will not understand the change naturally, especially with such a widely used application as Bash. This is a core program used by many people every single day and although the change is easily understood, it's not if the user doesn't know about it. This "bug" seems to fall into a gray area: according to the maintainer it is a necessary enhancement; to the average user it is a bug because it *appears* that well established functionality has been removed. Average users cannot be expected to read every changelog. Ideally they would, but if mainstream user are to be attracted by Linux and Ubuntu in particular it's just not going to happen unless the information is directly presented to them in a friendly way. I understand the Update Manager provides this functionality to some extent (KDE's does it much better), but there's plenty of cases it's simply not feasible, like during a disrto upgrade. Would it not be awesome if, for example, Bash's latest *important* changes were presented in terminal the first time it was started after an update? Maybe not to some people, but at least they would have been aware of this crucial change in functionality. This particular instance of update should be "forced" knowledge, even if the delivery method (a gtk popup, a web page, etc.) is considered intrusive or annoying. I realize this methodology could be thoroughly abused (Windows is a glaring example), but.... I'm probably beating a dead horse here, but the point is this: I'm a relatively experienced user who is interested in development and release notes and so on and I ended up with this problem. Take that as you will (laziness/unperceptive behavior on my part, or whatever), but it still happened to me and caused confusion and disruption to my computer usage. This is not in line with Ubuntu's stated philosophy of being easy for everyone (because, as I said before, Bash is a core application and very important). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/725327 Title: bash 4.2 does not save history (~/.bash_history) when using close window -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
