Re: Regedit output to STDOUT / force registry files sync

[Lei Zhang]

On 3/19/07, Vit Hrachovy  wrote:
> Hi,
> I'm trying to find some elegant method to access registry keys added
> during one WINE session, i.e. without restarting WINE.
>
> Test case description:
>         1. Open WINE session
>                 wineconsole --backend=user cmd
>         2. During session, insert some new registry key
>                 regedit new-entry.reg
>         3. Try to access the new registry entry from bash
>                 cat ~/.wine/system.reg |grep AutoHotkey
>                 (fails)

Accessing the Wine registry directly is probably not the right way to
do it, you should go through the Windows registry API calls, i.e.
RegQueryValue.
>     4. Close WINE session
>
> I've found there was at times an option to save registry periodically,
> but this can't help me here.
>
> This problem can be solved in two ways, both of them can be helpful:
>
> a) Create small program to force sync of registry in memory with
> registry files - 'wineflushregistry'.
>
> b) Enhance regedit to be able to output to STDOUT. By default registry
> search output is done to a specified file. It can be redirected to
> STDERR, though. (tested on 0.9.29, 0.9.33)

If you can get it to go to stderr, why not just use shell redirection
to redirect stderr to stdout?
> Enhancing regedit
>
> regedit /es
> "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App
> Paths\AutoHotkey.exe"
>
> which will be similar to (non-functional)
>
> regedit /e /dev/stdout
> "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App
> Paths\AutoHotkey.exe"
>
> Regards
> Vit Hrachovy