<ul>
<li>Внешний список
  <ul>
  <li>Вложенный список</li>
  </ul>
  Продолжение элемента внешнего списка
</li>
<li>Следующий элемент внешнего списка</li>
</ul>

   • §¦Внешний список

  
       • §¦Вложенный список
  
  Продолжение элемента внешнего списка
   • §¦Следующий элемент внешнего списка

• Как видно, "Продолжение элемента внешнего списка" вообще выпало из списка.
• Начальная позиция "Продолжение ..." в данном примере 2, т.е. совпадает с таковой в html.
  Соответственно если начать текст с позиции 0, то и в hlf он будет стоять с начала строки, и как результат - склеится с предыдущей строкой.
• И почему-то между внешним и вложенным списком интервал 2 строки. Если убрать из исходного html некоторые переносы строк, то лишних интервалов не будет.

Sample markdown source:

Test
====

Definition list

term1
:	definition1 \
	sample

In html:

<h2>Test</h2>
<p>Definition list</p>
<dl>
<dt>term1</dt>
<dd>
definition1<br />
sample
</dd>
</dl>

Resulting hlf:

.Language=English,English
.Options CtrlStartPosChar=§¦


@Contents
$ #Test#

 Definition list

 term1
     §¦definition1
sample

That is wrong, because in Far help it looks like this:

Definition list

term1
    definition1 sample

I suppose the correct handling would be to indent next line after <br />, like this:

 term1
     §¦definition1
     §¦sample

Old behaviour: on invoking commands, set the current PowerShell location and
the process current directory to the active panel path.

New behaviour: on invoking commands, set the current PowerShell location to the
active panel path. Do not change the process current directory.

Some "lazy" scripts may be affected. Note that PowerShell scripts should not
rely on the process current directory, they should use PS provider locations.

NB Changing the process current directory could be removed long time ago.

Long paths

Windows PowerShell (used by PSF up to v5) has many problems with long paths.
In particular it cannot set the current location to a long path. PSF in such
cases asked users how to proceed with kind of useful but annoying dialogs.

PowerShell Core (used by PSF v6+) works better with long paths. In particular
it sets the current location just fine. Thus, these annoying errors are gone.
But if we keep temporarily changing the process current location then we get
new kind of errors (generic .NET and OS issue, not PowerShell).

That is why we finally retire changing the current directory.
This started to be clearly inconvenient in some cases.

NOTE PS and other applications may still have long path issues.
Try to avoid anything PowerShell "intensive" in long path locations.

This works

$host | Out-FarPanel

This used to work but fails after some changes in Far about user screen

42
$host | Out-FarPanel

42 triggers ShowUserScreen. It is now kind of modal in Far and panels cannot be set current.

We need either exit user screen or make the switch to panels and opening async.

Сейчас что до что после заголовка интервал одинаков - 1 строка.

Как правило, я каждый раз редактирую потом hlf вручную, чтобы между текстом, и последующим заголовком было две строки.

Возможно стоит сделать это настраиваемым.

Is it possible to make active panel location per active directory where far was launched. And the other way - is it possible to set location in powershell after exiting Far per path in active panel when exiting?

Hello!
It would really great, if you consider some common channels of distribution, which much simplify install and upgrade.
Chocolatey is good example for it - you can specify dependencies which will automatically installed with you package (if them not exists already) and all your prereq are already exists in choco library.
Also, it comply with your current install method - it use nuget packages as container and then run powershell script that place files to its places. Also, they have some nice inbuild ps function like Get-AppInstallLocation to place module files into Far installation folder.

P.S. Many thanks for this plugins!

Hello Roman,

hope you are doing well. I have a couple of questions:

• I don't seem to be able to figure out how to make far use powershell 6, is this possible?
• Is it possible to have far execute powershell by default, eg without the ps: prefix?

Many thanks,
Andrew

How can I modify TabExpansion2 to complete in lowercase.

# Now
ls . -Force -Directory

# Wanted
ls . -force -directory

Thanks!

Такие как div, details, summary.

Их присутствие в исходном маркдаун обусловлено потребностью генерировать из него не только hlf, но и html.
Div в частности бывает необходим для того чтобы добавить информацию о стиле вложенного элемента.

В настоящий момент перед конвертацией в hlf удаляю всё неподдерживаемое скриптом.

Впервые устанавил FarNet, по инструкции https://github.com/nightroman/FarNet#install-using-powershell
При запуске падает.

bug_report.txt

C:\Apps\Far3\Plugins>dotnet --version
7.0.306

C:\Apps\Far3\Plugins>dotnet --info
.NET SDK:
 Version:   7.0.306
 Commit:    f500069cb7

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19045
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\7.0.306\

Host:
  Version:      7.0.9
  Architecture: x64
  Commit:       8e9a17b221

.NET SDKs installed:
  7.0.306 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.19 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.19 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

For the last two years, I used daily as my shell environment
ConEmu + FarManager + PowerShellFar.

The startup task on ConEmu was
>d:\Bin\Far\Far.exe /w ps:$Psf.StartConsole()
as suggested here.

Also, I had made a multiple-color, two-lines custom prompt for my PowerShellFar Console.

I have build the majority of my ps scripts (100s) around the above environment,
utilizing the PowershellFar library, which I find extremely helpful.

After my FarNet update today, when I opened my shell I've got the error:

ps:$Psf.StartConsole()                                                                                 
ERROR: RuntimeException:                                                                               
Method invocation failed because [PowerShellFar.Actor] does not contain a method named 'StartConsole'. 

I traced the latest commits and History, and I've noticed that on version 5.2.0
Retired command console, and on 5.2.1 Editor console -> Interactive

To my opinion, Interactive is totally different experience compared to Console,
and PowershellFar's Console was one of the main strengths.

Please restore back PowershellFar Console!

Markdown:

# Header 

term
:	definition  
	[link](#Contents) `code`

Hlf:

.Language=English,English
.Options CtrlStartPosChar=§¦


@Contents
$ #Header#

 term
     §¦definition
     §¦~link~@Contents@#code#

PowerShellFar 5.2.3
Script Write-Red.ps1

    function Write-Red ($text) {
        $color = $host.UI.RawUI.ForegroundColor
        $host.UI.RawUI.ForegroundColor = 'Red'
        $text
        $host.UI.RawUI.ForegroundColor = $color
    }

    Write-Red 'must be red, it is not in PSF 5.2.3'
    Write-Red 'must be red, it is'

It is a generic PS script, not specific for Far.
We can call it by powershell.exe

powershell.exe .\Write-Red.ps1

and it writes two red lines.

To make colored output, the script uses ForegroundColor instead of Write-Host -ForegroundColor .... This technique allows redirection of output, i.e. we can

powershell.exe .\Write-Red.ps1 > log.txt

and log.txt contains our two lines. This is not possible with Write-Host.

This technique of colored output is commonly used in PS, e.g. by

• Invoke-Build, see Write-Build
• psake, see WriteColoredOutput

The problem

If we invoke the above script in PSF (or use the mentioned or similar tools in PSF):

ps: .\Write-Red.ps1

then the first line is not colored, as we expect.

The problem is caused by a known change in Far, to be discussed with its author.

When trying to install / update FarNet, I get error 400 (bad request), NuGet works. Tested on Windows 10 and Windows 10 Developer Virtual Machine from Microsoft without any changes (.NET 4.8 included with system).

Consider such source sample:

Test 1
======

[Sample _link_](http://example.com)

<h2>Test 1</h2>
<p><a href="http://example.com"><em>Sample</em> link</a></p>

This produces such hlf link: ~Sample ~@http://example.com@#link#. (Notice that link-part is here outside the link. But ok.)

Now consider another sample:

Test 1
======

[_Sample_ link](http://example.com)

<h2>Test 2</h2>
<p><a href="http://example.com"><em>Sample</em> link</a></p>

Such input now causes an error: Invalid or not supported HTML: Expected <a href=...>...</a>. At test2.html:2:34

I suppose that simplest way would be just to skip any formatting in link's body.

Example:

#I @"packages\FSharp.Management\lib\net40"
#r @"FSharp.Management.PowerShell.dll"

open FSharp.Management

// Let the type provider infer the signatures of available cmdlets
type PS = PowerShellProvider< "Microsoft.PowerShell.Management;Microsoft.PowerShell.Core" >
PS. // <- [Tab] here

As a result, FSharpFar correctly shows the menu with PS command names. But on selection it inserts names literally, i.e.

PS.Add-Content

Non-standard F# names should be escaped, i.e.

PS.``Add-Content``

Hello,
I'm trying to run the latest (7.0.5) FarNet package under the latest stable (3.0.6060) or nightly (3.0.6117) Far manager build. But after installing the package, Far manager is failing to start, crashing on FarNet plugin.
I have tried to install some previous FarNet version (7.0.1), but no luck either.
Windows 11 22H2 Build 22621.963.
Any help/suggestions?
Thanks in advance!
bug_report.txt
far.mdmp.zip

# Contents

a. text
   [link](https:\\)

@Contents
$ #Contents#

   1. §¦text~link~@https:\@

Ожидаемое поведение: пробел между text и link.

I could not find information about netcore support.
Also dotnet template for it would be great.

I'm playing with FarNet and I'm not able to make DemoExplorer working. How is it supposed to work?
@nightroman

When editing a PowerShell script in Far Editor, pressing Tab on an empty line with the cursor past the end of line (such as when Auto Indent is enabled) causes the following exception to be thrown:

IndexOutOfRangeException:
Index was outside the bounds of the array.

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at PowerShellFar.EditorKit.NeedsTabExpansion(IEditor editor)
   at PowerShellFar.EditorKit.OnKeyDownPSFile(Object sender, KeyEventArgs e)
   at FarNet.Editor0.AsProcessEditorInput(ProcessEditorInputInfo* info)
   at ProcessEditorInputW(ProcessEditorInputInfo* info)

An example of how to reproduce this:

• Open a PowerShell script, or edit a new one, in Far Editor.
• Set the following options, if not already set:
  [x] Cursor beyond end of line
  [x] Auto indent (not required for the example, but it makes my life easier 😄 )
• Enter the following starting at any column > 1:

    if ($foo -eq "bar")<Enter>
    {<Enter>

• At this point the cursor is on an empty line directly underneath the opening brace, "{".
• Now, press Tab and you will see the message box referring to the exception. Selecting "[ More ]" will display the exception and stack trace in a new modal Editor.

Versions

• Far Manager 3.0.4949 x64
• FarNet and PowerShellFar 5.2.3

Thanks in advance,
Buck

Are there any plans to support .Net Core 3.0 or 3.1 instead of / in addition to .Net Framework?

Following the discussion #19 and recent NuGet breaking changes (retired API).
It makes sense to remove the module FarPackage from PowerShellFar.
Reasons:

1. Users should use the online install/update scenario described in README instead of using local FarPackage. This reduces chances of FarPackage being out of date and related issues.
2. FarPackage distribution with PowerShellFar is awkward anyway because in many cases using it requires Far Manager exit. This makes little sense for having FarPackage in PowerShellFar\Modules.

It was tempting to ShowUserScreen from RawUI set-members and it was done in
PSF 5.2.2. It is a bad idea. PS core may call these members unexpectedly, and
from other threads, too.

In other words, raw console API must not be bound to Far API, at least not to
ShowUserScreen.

Symptoms in 5.2.2

Type something in the command line and call PSF TabExpansion. As a result, the
user screen is shown unexpectedly and the completion menu is shown at the left
most position, not at the expected caret position on typing.

It turns out PS plays with ForegroundColor when we call TabExpansion. We
cannot control and avoid such calls. Even if we add an ugly workaround for this
use case, we will not solve the problem in other similar cases.

... instead of derived from .fsproj. Otherwise, most of the checker operations fail with "the file is not included in the project".

v1.0.1 uses the work around read only results borrowed from TabExpansionPlusPlus:

if ($result.CompletionMatches.IsReadOnly) {
    $private:collection = New-Object System.Collections.ObjectModel.Collection[System.Management.Automation.CompletionResult]
    foreach($_ in $result.CompletionMatches) {
        $collection.Add($_)
    }
    $result.GetType().GetProperty('CompletionMatches').SetValue($result, $collection)
}

It works but it makes incorrect ReplacementIndex and ReplacementLength.
E.g. for ... [cmd= as if we are about to replace just =, not [cmd=.
Note that some ... is essential, v1.0.1 works fine for a one-liner [cmd=.

See #2 for the introduction of coming changes and the reasons.

Remove the obsolete wrapper New-CompletionResult.
New-Object System.Management.Automation.CompletionResult should be used instead.

Remove support for obsolete profile names *TabExpansionProfile*.ps1.
Names like *ArgumentCompleters.ps1 should be used instead.

Add new functions Register-InputCompleter and Register-ResultCompleter.
They should be used instead of adding completers directly to options.
Old adding to options still works but this may change later.

Improve the work around read-only result collections.

Upgrade the sample TabExpansionProfile.ps1 according to the above notes.
Fix some minor code defects, including leaked completers variables.

Changes are not breaking now. It is recommended to start the migration in order
to be ready to the future breaking changes. The goal is to be compatible with
v5 built-in and TabExpansionPlusPlus Register-ArgumentCompleter.

The wrapper New-CompletionResult is obsolete and will be removed. Instead,
use New-Object System.Management.Automation.CompletionResult directly.
Reasons:

• PowerShell v5 does not have anything like this at all.
• TabExpansionPlusPlus has it but it is not compatible.

Profile naming convention. Names like *ArgumentCompleters.ps1 should be used
instead of *TabExpansionProfile*.ps1 in order to follow the current trends.
Some completer profiles are supposed to be reusable in other scenarios.

The new function Register-ArgumentCompleter should be used instead of adding
completers directly to tables. In this way, the same completers can be used in
PowerShell v5 natively or with TabExpansionPlusPlus.

The sample TabExpansionProfile.ps1 was renamed to ArgumentCompleters.ps1
and its code was upgraded according to the above notes.

1. Exiting Explorer returned from OpenFile closes parents panel, also without notifying on UIClosing, not letting to interrupt.
   Is that intended behaviour? If so, is there a way to implement file explorer chaining (like archive within archive)?
2. First created Explorer does not notify ExploreParent until other folder is opened.
3. After setting CanExploreLocation, only File.Name is passed to GetContent & OpenFile, without File.Data