Making locate_header_by_msgid() and other functions preserve the thread display?

I'm using locate_header_by_msgid(msgid,1) with version:

=====================================
slrn 1.0.1
S-Lang Library Version: 2.2.4
Compiled on: Feb 18 2014 22:09:18
Operating System: Linux

COMPILE TIME OPTIONS:
  Backends: +nntp -slrnpull -spool
  External programs / libs: -canlock -inews +ssl -uudeview +iconv
  Features: +decoding +emphasized_text +end_of_thread +fake_refs +gen_msgid
     -grouplens -msgid_cache +piping +rnlock +spoilers -strict_from
  Using 64 bit integers for article numbers.

DEFAULTS:
  Default server object:     nntp
  Default posting mechanism: nntp
=====================================

Could locate_header_by_msgid() not collapse all threads when bringing 
back an article from the server? In other words, when the second 
argument to locate_header_by_msgid() is 1 and the article isn't present 
in the article list?

Collapsing all uncollapsed threads on retrieving an article from the 
server is interfering with a macro I tried to write, and I'd prefer not 
to have to work around this behavior.

Other functions, such as the "expunge" intrinsic, also collapse all 
threads. It would be nice if all functions left the threading display 
alone (except when the function's purpose is to change the thread 
display, of course). Speaking from a usage point of view, collapsing all 
threads for seemingly unrelated functions feels like a side-effect.

Thanks for considering this.

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs