# Use contents of an output variable as current input **URL:** \ **Category:** Web Sources Discussion\ **Created:** [November 11, 2025, 4:04pm UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122 "2025-11-11T16:04:47Z")\ **Posts on this page:** 9\ **Page:** 2
**Author:** ![rboss](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/5f9b8f/32.png) [@rboss](https://community.mp3tag.de/u/rboss)\ **Post date:** [November 16, 2025, 6:09pm UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/21 "2025-11-16T18:09:08Z")
(Very) late to this very interesting exchange. I can only have a proper sit down at weekends, so I couldn't make it in time, but here ~~is~~ was my submission for a new tool operating as `RegexpReplace "^.*"`. This is transcribed from my phone, where I usually jot down ideias when I'm not at home. * * * `Feed S n` Wording: - derived from "Line Feed" (LF); also from the verb form "to feed". Usage: - used as `Feed` or `Feed ""`: Clears current buffer content; mimics a new/fresh/clean line (similar to `RegexpReplace "^.*" ""`); - used as `Feed "S"`: Clears current buffer content AND inserts contents of `S`, either string or %output% (similar to `RegexpReplace "^.*" "string|%output%"`); moves pointer to 1; used as `Feed "S" 1`: inserts contents of `S` (string|%output%) at current pointer position (as in _'feeding'_ `S`); moves pointer to 1st character after appended content (previously suggested as [Splice](https://community.mp3tag.de/t/suggestion-splice-command-for-ws/61854)). Inconveniences: Using `Feed "" 1` would, in effect, do nothing. _(behavior already happens in `Replace S S`; so no big deal)_ I'm leaving this here, as it may inspire others. * * * EDIT: I just read about `Use`; and here's an idea: `Use S 1`: Use contents of `S` as current input. If the second parameter is set to 1, `S` is inserted(/spliced? /added? / appended?) at current pointer position. ---
**Author:** ![rboss](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/5f9b8f/32.png) [@rboss](https://community.mp3tag.de/u/rboss)\ **Post date:** [November 16, 2025, 8:13pm UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/22 "2025-11-16T20:13:06Z")
> [@arb](#): > > | UseFormat test2 | test2 | > | --- | --- | > | UseFormat %TEST% | hello world | > | UseFormat 123%TEST%456 | 123hello world456 | > | UseFormat %\_current% | 123hello world456 | > | UseFormat abc%\_current%def | abc123hello world456def | Just to add that `%_output%` (note the leading underscore in the variable title) is considered a hidden output by this command, so that `abc%_current%def%_TEST%` returns the same as `abc%_current%def`, regardless of the value of `%_TEST%` set beforehand. @Florian please consider this as an (appended) bug report, or a request to add a warning in the documentation page, if not (easily) fixable. ---
**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\ **Post date:** [November 16, 2025, 9:49pm UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/23 "2025-11-16T21:49:47Z")
Thanks for pointing! I added this to the documentation for now: > Other outputs can be referenced by their respective names, i.e., `%output%` but cannot start with an underscore `_` (and will most likely make it work with one of the next releases) ---
**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\ **Post date:** [November 16, 2025, 10:27pm UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/24 "2025-11-16T22:27:43Z")
> [@rboss](#): > > EDIT: I just read about `Use`; and here's an idea: > `Use S 1`: Use contents of `S` as current input. If the second parameter is set to 1, `S` is inserted(/spliced? /added? / appended?) at current pointer position. Just wanted to let you know that I've made a note regarding this. I think I prefer `Splice S` or `Insert S` over additional parameters for `Use`. ---
**Author:** ![rboss](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/5f9b8f/32.png) [@rboss](https://community.mp3tag.de/u/rboss)\ **Post date:** [November 16, 2025, 10:52pm UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/25 "2025-11-16T22:52:27Z")
Of course. As you may have noticed from my WSS contributions, I'm one who prefers one tool with many functions over several tools with one function (although sometimes they are needed). I could see that `Use S 1` might not be considered very _in line_ with the main purpose of `Use`; not to mention the extra coding work to add a feature to an existing command (that may be bigger than creating a new simpler command from scratch). Besides, `RegexpReplace` (the multi-purpose command that it is), serves that task quite well (for my current needs). Regardless, the idea of inserting a string|%output% at the current pointer position (via a dedicated command) is there, at your discretion. ---
**Author:** ![arb](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/41988e/32.png) [@arb](https://community.mp3tag.de/u/arb)\ **Post date:** [November 16, 2025, 11:01pm UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/26 "2025-11-16T23:01:01Z")
If itโ€™s a parameter, it makes `Use` act like `Say` where it plonks data onto an existing lot. If itโ€™s a separate command, it might be easier to understand as its own function. Either method makes distinct use of the pointer as a drop-off point, whereas `RegexpReplace` canโ€™t position the pointer where needed but slots in the data immediately without commands before-hand (at the risk of special characters like $.\*? interfering which might require the less powerful `Replace` instead). All have their benefits either way. ๐Ÿ˜ฌ ๐Ÿ‘ ---
**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\ **Post date:** [November 18, 2025, 9:53pm UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/27 "2025-11-18T21:53:22Z")
I've added `Insert S` and support for output variables beginning with underscore at `SayFormat` and `UseFormat` with [Mp3tag v3.32a](https://community.mp3tag.de/t/455). ---
**Author:** ![rboss](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/5f9b8f/32.png) [@rboss](https://community.mp3tag.de/u/rboss)\ **Post date:** [December 1, 2025, 3:26am UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/28 "2025-12-01T03:26:13Z")
> [@Florian](#): > > I've added `Insert S` and support for output variables beginning with underscore at `SayFormat` and `UseFormat` with [Mp3tag v3.32a](https://community.mp3tag.de/t/455). Apologies for the late reply. `Insert S` is working exactly as expected, either with a string or an %output% (or even %\_output%). As for `SayFormat` and `UseFormat`, underscore-lead outputs are now visible and working as well as any other. Thank You ๐ŸคŸ very much. PS: > [@Florian](#): > > Thanks for pointing! I added this to the documentation for now: > > > Other outputs can be referenced by their respective names, i.e., `%output%` but cannot start with an underscore `_` (๐Ÿ‘† This line in the documentation can now be edited and the warning regarding underscores removed.) ---
**Author:** ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)\ **Post date:** [December 31, 2025, 3:26am UTC](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122/29 "2025-12-31T03:26:16Z")
Closed on December 31, 2025, 3:26am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. [Previous page](https://community.mp3tag.de/t/use-contents-of-an-output-variable-as-current-input/70122.md?page=1)