Controversial posts made by oliof

it would be a couple bytes per nested call, and since this feature would most likely be used by people doing more complex macros, it would be more memory than just a few bytes sooner rather than later...

@lynnmt you really should be updating to 3.4.6 at least (I also would suggest leaving out the SBC which has no benefit for your current use).

my money is on the bowden gap issue with the terrible pneumatic push fits on an ender, and that the switch to the board is incidental. See https://www.youtube.com/watch?v=30qqKUwviww

@droftarts I just meant to use the feature that allows you to give macros an unused gcode name and then calling that, without changes to the firmware (-;

I already said I will provide a more detailed explanation when I have the time. Please stop pestering me about it now.

@dragonn I don't have issues with clogging or my all metal hotend's retraction settings. While what you write is an interesting observation, it does not add to my issue here.