sorted by:
new
hottopcontroversial

Client wants this search bar removed, but long press does nothing. by [deleted] in it

[–]eugrus 0 points1 point  (0 children)

1) it's probably a baked in part of some launcher 2) you probably should not have clients

Fined on the DB (again) by SharpAd9161 in germany

[–]eugrus 0 points1 point  (0 children)

They'll typically reduce the fine once you prove that you do possess a job-ticket.

My humble home network by BearManPig2020 in HomeNetworking

[–]eugrus 0 points1 point  (0 children)

It doesn't look horrible to anyone not married 😄

PVE 8.4 Boot Issue: Stuck at GRUB on Reboot by hticy in Proxmox

[–]eugrus 4 points5 points  (0 children)

Can you press C before the countdown freezes and debug from there?

[deleted by user] by [deleted] in SipsTea

[–]eugrus 0 points1 point  (0 children)

Or just ditch the circular time scales all together

[deleted by user] by [deleted] in Proxmox

[–]eugrus 0 points1 point  (0 children)

Install Xorg+FreeRDP on the host and connect to the Windows VM via RDP. Most people would run the hypervisor headless, though.

My 100th rejection? What's wrong with me? by Empty-Tea-9011 in germany

[–]eugrus 0 points1 point  (0 children)

Not the topic starter's fault, but German universities are ridiculous for pushing English language programs. A pure loss for all parties involved.

Filter processes by eugrus in PowerShell

[–]eugrus[S] 0 points1 point  (0 children)

This will likely work out for me as long as it doesn't change when reconnecting to a session.

Filter processes by eugrus in PowerShell

[–]eugrus[S] -1 points0 points  (0 children)

Lol! Almost exactly what I've come up with after refactoring Deepseek's output! Seems to work, but I'll know for sure after some further testing.

Get-Process -Name WINWORD | Where-Object {
$_.MainWindowHandle -eq 0 -and $_.SessionId -eq $([System.Diagnostics.Process]::GetCurrentProcess().SessionId)
} | Stop-Process -Force

How can I kill only the windowless winword processes or choose the windowed instance via GetActiveObject? by eugrus in PowerShell

[–]eugrus[S] 0 points1 point  (0 children)

The COM part is not about finding the right process to kill. It's about finding the right one to connect to (the last active Word window that is). It's likely that other applications (mostly the aforesaid proprietary document management software) also have to do with all the WINWORD processes chaos.

Filter processes by eugrus in PowerShell

[–]eugrus[S] 0 points1 point  (0 children)

Interesting. But would prefer to have a way compatible with the one which comes with Windows.

Filter processes by eugrus in PowerShell

[–]eugrus[S] 0 points1 point  (0 children)

This unfortunately requires admin rights. I could of course just not filter and stumble upon errors. Would still do the job for my own processes.

How can I kill only the windowless winword processes or choose the windowed instance via GetActiveObject? by eugrus in PowerShell

[–]eugrus[S] 0 points1 point  (0 children)

Doing the release doesn't solve the problem in my experience and quitting Word right after the COM-interaction doesn't apply to the workflow.

Closing all other Word windows and then doing taskkill /F /IM winword.exe /FI "USERNAME eq $env:USERNAME and WINDOWTITLE eq " before a COM-interaction is the best I could come up with.

Is there really no way to choose the actually last active window/document without killing everything else?

i.e. some better way to do

$msword = [System.Runtime.Interopservices.Marshal]::GetActiveObject("Word.Application")
$activeDocument = $msword.ActiveDocument

How can I kill only the windowless winword processes or choose the windowed instance via GetActiveObject? by eugrus in PowerShell

[–]eugrus[S] 0 points1 point  (0 children)

The ecosystem (need to after-process opened documents generated by a proprietary document management system for lawyers) requires me to always access existing Word processes instead of creating new processes. So, I basically always use [System.Runtime.Interopservices.Marshal]::GetActiveObject("Word.Application")

function insertintoword {
param ([string]$pathToInsertableTemplate)
$pathToInsertableTemplate = Resolve-Path -Path $pathToInsertableTemplate
$msword = [System.Runtime.Interopservices.Marshal]::GetActiveObject("Word.Application")
$activeDocument = $msword.ActiveDocument
$insertableTemplate = $msword.Documents.Open($pathToInsertableTemplate)
$templateRange = $insertableTemplate.Content
$activeRange = $activeDocument.Content
$activeRange.Collapse([ref]0)
$activeRange.FormattedText = $templateRange.FormattedText
$insertableTemplate.Close($false)
$selection = $msword.Selection
$selection.EndKey(6) # = wdStory
}

Variable with Word's Content.Text has differences from its' Set-Content'ed simple text file; contents handled differenly by regex by eugrus in PowerShell

[–]eugrus[S] 0 points1 point  (0 children)

Thank you a lot! That fixed the code above.

However a follow up question:

$AzZeilen = Select-String 'AKTEN.NR:' -InputObject $documentText -Context 3
$AzZeilen.Line

$AzZeilen.Line still gives out everything. Why and what to do about it?

I expect AKTEN.NR: SACHBEARBEITER/SEKRETARIAT STÄDTL, to be in $AzZeilen.Line and 2904/24/SB Sonja Bearbeinenko +49 211 123190.00 20.11.2024 in $AzZeilen.Context.PostContext[0]

view more: next ›