Hit ctrl+a+d which will detach the screen session. To get it back type screen -ls and note the process id. Then screen -r (process id) to reattach. Tom Morton On 22 Dec 2011, at 13:38, "Bináris" <wikiposta(a)gmail.com> wrote: 2011/12/22 John <phoenixoverride(a)gmail.com> Please help, how. I am not very familiar with Linux. After having a look at help and man, I just typed in "screen". The result is: [Press Space or Return to end.] Getting 60 pages from wikipedia:hu... Sleeping for 4.0 seconds, 2011-12-22 14:34:45 Sleeping for 4.3 seconds, 2011-12-22 14:34:50 Getting 60 pages from wikipedia:hu... Getting 60 pages from wikipedia:hu... Sleeping for 4.4 seconds, 2011-12-22 14:34:57 Getting 60 pages from wikipedia:hu... Sleeping for 4.5 seconds, 2011-12-22 14:35:03 Getting 60 pages from wikipedia:hu... Sleeping for 4.6 seconds, 2011-12-22 14:35:09 Getting 60 pages from wikipedia:hu... Sleeping for 4.3 seconds, 2011-12-22 14:35:15 So the messages still come, but at random cursor positions. :-) I quit with space, and now it looks like the same at the normal prompt, messages don't begin at the leftmost position any more. -- Bináris _______________________________________________ Pywikipedia-l mailing list Pywikipedia-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

I see the problem: my script was already running when I used screen. Now I started another connection, and used screen, started the script and detached it, and this way it works. Thank you for the idea and the help. However, it would be nice to be able to suppress unnecessary messages. Every script should have this feature. I often experience that a large amount of screen output makes programs run slower. -- Bináris

Hi Merlijn, Op 22-12-2011 21:48, Merlijn van Deen schreef: I think we can distinguish two kinds of output: 1. Output for user interaction (diff, followed by user interaction) 2. Various levels of information If a bot is running in autonomous mode all messages fall in the second category. We should probably start using the python logging module and define an output level (see https://en.wikipedia.org/wiki/Syslog) for every message. Sounds like a nice programming project. Who is up to the challenge? ;-) Maarten

Hello Dr. Trigon, On 24 December 2011 22:21, Dr. Trigon <dr.trigon(a)surfeu.ch> wrote: I think this misses the point of switching to the Logging module. The benefit of the Logging module is the possibility of assigning 'logging levels' to a message, e.g. DEBUG, INFO or WARNING, and the user can then configure the verbosity. Essentially, we would need to re-implement the user interface module to pass through the logging module, which allows for creating different output modules. But as far as I know, the rewrite already does this - or at least partially ;-) Merlijn

On 25 December 2011 10:57, Dr. Trigon <dr.trigon(a)surfeu.ch> wrote: from rewrite than to re-develop them for trunk. In a perfect world, everybody should already be using rewrite and it should be 100x more awesome than trunk. In reality, we might want to consider backporting parts instead of trying to get people to switch. Merlijn

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyway I have to thank this thread (!!) since I did not know the 'logging' module from python - know even my bot does... ;))

On 22 February 2012 11:24, Bináris <wikiposta(a)gmail.com> wrote: python bot.py 2>&1 > /dev/null ? Furthermore, the logging module is *not* difficult and a lot of useful wrapper functions for pywikipedia already exist in the rewrite branch: http://svn.wikimedia.org/viewvc/pywikipedia/branches/rewrite/pywikibot/bot.… (around line 217) Best, Merlijn

Well, at the moment I cannot dig into that project. First I have to understand put_async as described in the other thread, and have a lot of other pending projects... So it remains for a while as it is. -- Bináris