Metasploit-framework: executing pry for a module imports unwanted history

[Auxilus]

Steps to reproduce

How'd you do it?

1. use _module_
2. history
3. pry
4. history

History after step 4 should contain previously executed pry command (even from outside the msf )

Expected behavior

using pry for a module shouldn't import the pry history (at least not that was executed outside msf)

Current behavior

msf5 exploit(multi/handler) > history                                        
1  use exploit/multi/handler
2  history
msf5 exploit(multi/handler) > pry                                            
[1] pry(#<Msf::Modules::Mod6578706c6f69742f6d756c74692f68616e646c6572::MetasploitModule>)> exit

msf5 exploit(multi/handler) > history
1   use exploit/multi/handler
2   history
3   pry                                                                      
4   puts a                                                                  
5   n                                                                        
6   next
7   step
8   p hostname
9   continue
10  s
11  n
12  next
13  step
14  finish
15  next
16  Pry.commands.alias_command 'n', 'next'
17  next
18  p @login
19  n
20  next
21  exit
22  n
msf5 exploit(multi/handler) >

[wvu-r7]

You're deep in Readline now, son.

[Auxilus]

no way to fix?

[wvu-r7]

All you, buddy. :)

[Auxilus]

there is a issue open with same problem at https://github.com/pry/pry/issues/1266