Well, typing it is cumbersome so you can do in ~/.bash_aliases or ~/.bashrc
alias emacs='emacs > /dev/null 2>&1' I agree though, that is annoying, and a lot of GTK programs do that. And sending the output to null isn't really the right answer, since you'll miss actual errors that are important. As far as I can tell, it's a compiled flag on gtk, so filing a bug against gtk is probably the best thing to do. You could rebuild the gtk deb from the source deb and change that and install it too, if you want to do that. Tim Kelley On Mon, Apr 27, 2015 at 2:16 PM, Juha Heinanen <j...@tutpro.com> wrote: > Tim Kelley writes: > > > If you just use the console emacs, you can install the emacs-nox version > of > > 24. > > In this case, i used x11 emacs, but started it from console. > > > In anycase, they’re just warnings, and can be ignored. > > Yes, I know, but the warnings consume the whole page of the terminal > window and I cannot anymore see, what was there without scrolling back, > which is annoying. > > > It’s just > > stating something some other packager did was deprecated but still > > functional .. you can start emacs with emacs >/dev/null 2>&1 if you like, > > or not start it from the terminal and start from an icon or menu. > > Typing emacs >/dev/null 2>&1 is too cumbersome and starting from menu > looses the directory where I am. For example, if the current dir has a > file that I want to edit, I just used to type > > emacs file > > but now I get all the garbage to the window which is not good. > > Is there anything that can be done to get rid of those warnings? Which > package the bug lies? Is there any hope that the bugs are fixed before > the next Debian release? > > -- Juha >
