Sebastien Bacher wrote 11 hours ago: #13
why do people care so much about a warning printed on the command line
there? the issue is only a warning one, not a crasher or something
breaking any software
--
I do find this warning very annoying for two reasons: first, seeing the
warning itself everytime I run emacs is annoying enough to me as I do
this a lot of times from command-line everyday; second, I am used to the
way of launching emacs as emacs some_file so that after emacs pops
out I still have the command-line prompt but with this warning I have to
hit an extra Enter to get back to the prompt.
Well okay, now I realized that I could have used alias emacs=emacs
2/dev/nullto get around my problem but maybe a newbie to Ubuntu
got so pissed off by this small thing for similar reasons that he ended
up switching back to Windows.
My point is, (assuming this bug is now a very easy-to-fix one after
fixes to lucid is done), why couldn't Ubuntu developers care a bit more
about users' experience and make their Ubuntu journey smoother other
than filled with little bumps which users are supposed to either put up
with or be able smoothen by themselves?
--
g_set_prgname() called multiple times
https://bugs.launchpad.net/bugs/501670
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
