# Show-BluGenieMore

﻿Show-BluGenieMore

### SYNOPSIS <a href="#synopsis" id="synopsis"></a>

Show-BluGenieMore is a command used to view content one screen at a time in case the file is large.

### SYNTAX <a href="#syntax" id="syntax"></a>

```
Show-BluGenieMore [[-Source] <Object>] [[-LineCount] <Int32>] [[-Suffix] <String>] [-Walkthrough] [<CommonParameters>]
```

### DESCRIPTION <a href="#description" id="description"></a>

Show-BluGenieMore is a command used to view content one screen at a time in case the file is large. You can define how many lines are diplayed to the screen as well. The default is 25.

### EXAMPLES <a href="#examples" id="examples"></a>

#### EXAMPLE 1 <a href="#example-1" id="example-1"></a>

```
Command: ,$(Get-ChildItem -Path $env:windir\System32 -File | Select-Object -ExpandProperty FullName) | Show-BluGenieMore
```

```
Description: Query C:\Windows\System32 for all files and display the Full Path names 25 lines per page using the Pipeline
Notes: 
While sending content over the pipeline you need to use an Unary Comma Operator.
      As a binary operator, the comma creates an array. As a unary operator, the comma creates an array with one member. Place the comma before the member.

      ,$MyArray | More
```

#### EXAMPLE 2 <a href="#example-2" id="example-2"></a>

```
Command: ,$(Get-ChildItem -Path $env:windir\System32 -File | Select-Object -ExpandProperty FullName) | More
```

```
Description: Query C:\Windows\System32 for all files and display the Full Path names using the Show-BluGenieMore Alias
Notes: 
While sending content over the pipeline you need to use an Unary Comma Operator.
      As a binary operator, the comma creates an array. As a unary operator, the comma creates an array with one member. Place the comma before the member.

      ,$MyArray | More
```

#### EXAMPLE 3 <a href="#example-3" id="example-3"></a>

```
Command: ,$(Get-ChildItem -Path $env:windir\System32 -File | Select-Object -ExpandProperty FullName) | More -Suffix ' * ' -LineCount 30
```

```
Description: Display content 30 lines per page request.  Each line item will have a Suffix ' * ' appended.
Notes:
```

#### EXAMPLE 4 <a href="#example-4" id="example-4"></a>

```
Command: Show-BluGenieMore -Source $(Get-ChildItem -Path $env:windir\System32 -File | Select-Object -ExpandProperty FullName)
```

```
Description: Query C:\Windows\System32 for all files and display the Full Path names 25 lines per page using the Source Parameter
Notes:
```

#### EXAMPLE 5 <a href="#example-5" id="example-5"></a>

```
Command: Show-BluGenieMore -Help
```

```
Description: Call Help Information
Notes: If Help / WalkThrough is setup as a parameter, this script will be called to setup the Dynamic Help Menu if not the normal Get-Help will be called with the -Full parameter
```

#### EXAMPLE 6 <a href="#example-6" id="example-6"></a>

```
Command: Show-BluGenieMore -WalkThrough
```

```
Description: Call Help Information [2]
Notes: If Help / WalkThrough is setup as a parameter, this script will be called to setup the Dynamic Help Menu if not the normal Get-Help will be called with the -Full parameter
```

### PARAMETERS <a href="#parameters" id="parameters"></a>

#### Source <a href="#source" id="source"></a>

```
-Source <Object>
   Description: The content to display.  While sending content over the pipeline you need to use an Unary Comma Operator.
   Notes: 
   Comma operator ,
           As a binary operator, the comma creates an array. As a unary operator, the comma creates an array with one member. Place the comma before the member.
   
           ,$MyArray | More 
   Alias:
   ValidateSet:
   
   Required?                    false
   Position?                    1
   Default value                
   Accept pipeline input?       true (ByValue, ByPropertyName)
   Accept wildcard characters?  false
```

#### LineCount <a href="#linecount" id="linecount"></a>

```
-LineCount <Int32>
   Description: Define the line items to display.  The Default is 25.
   Notes:  
   Alias:
   ValidateSet:
   
   Required?                    false
   Position?                    2
   Default value                25
   Accept pipeline input?       false
   Accept wildcard characters?  false
```

#### Suffix <a href="#suffix" id="suffix"></a>

```
-Suffix <String>
   Description: Return each line with a suffix.  This can be used as a check list to mark each line. 
   Notes:  
   Alias:
   ValidateSet:
   
   Required?                    false
   Position?                    3
   Default value                
   Accept pipeline input?       false
   Accept wildcard characters?  false
```

#### Walkthrough <a href="#walkthrough" id="walkthrough"></a>

```
-Walkthrough [<SwitchParameter>]
   Description:  Start the dynamic help menu system to help walk through the current command and all of the parameters
   Notes:  
   Alias: Help
   ValidateSet:
   
   Required?                    false
   Position?                    named
   Default value                False
   Accept pipeline input?       false
   Accept wildcard characters?  false
```

#### CommonParameters <a href="#commonparameters" id="commonparameters"></a>

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manuals.blusapphire.io/blugenie/full-function-list/show-blugeniemore.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
