# New Guy, gSender 1.0.6, Console Copy

**URL:** <https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165>\
**Category:** 🐛 Bug\
**Created:** [June 27, 2022, 10:57pm UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165 "2022-06-27T22:57:48Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![AutoDoc](https://forum.sienci.com/letter_avatar_proxy/v4/letter/a/e480ec/32.png) [@AutoDoc](https://forum.sienci.com/u/AutoDoc)\
**Post date:** [June 27, 2022, 10:57pm UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/1 "2022-06-27T22:57:48Z")

</div>

When I go and hover over the copy icon while in the console window, I get a tooltip that says that I’ll get the last 50 lines from the console buffer, but when I click it, I get a pop up dialog that says that the last 675 lines were copied. When I go and do a paste operation in my text editor, sure enough, I get what looks like the last 50 lines. This is fine, but I sure would like to get at more history so as to help me figure out what just happened. Is this history stored somewhere where I can get at it?

---

<div class="post-metadata">

**Author:** ![KGN](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/c77e96/32.png) [@KGN](https://forum.sienci.com/u/KGN)\
**Post date:** [June 28, 2022, 2:54pm UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/2 "2022-06-28T14:54:23Z")

</div>

We store up to the last 1000 lines as “history”, but it’s only possible to copy the last 50 easily. We’ll look at making this customizable in the future so it’s easier to grab more/“all” up to the limit.

Kevin

---

<div class="post-metadata">

**Author:** ![AutoDoc](https://forum.sienci.com/letter_avatar_proxy/v4/letter/a/e480ec/32.png) [@AutoDoc](https://forum.sienci.com/u/AutoDoc)\
**Post date:** [June 28, 2022, 3:34pm UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/3 "2022-06-28T15:34:48Z")

</div>

I did manage to get everything out by scrolling to the top of the console text and dragging until I got to the end and just copied everything and pasted it into a text editor so that’s not a terrible workaround, but get rid of that “675 lines” pop-up, because that’s what confused me in the first place.

---

<div class="post-metadata">

**Author:** ![gwilki](https://forum.sienci.com/user_avatar/forum.sienci.com/gwilki/32/366_2.png) [@gwilki](https://forum.sienci.com/u/gwilki)\
**Post date:** [June 29, 2022, 1:57am UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/4 "2022-06-29T01:57:57Z")

</div>

@AutoDoc Welcome to the group, Rial.

What are you using the console information for? Since many projects will be more than 1000 lines long, even the fix may not solve your problem. Knowing what you want to do with the information may enable someone here to offer another solution.

---

<div class="post-metadata">

**Author:** ![AutoDoc](https://forum.sienci.com/letter_avatar_proxy/v4/letter/a/e480ec/32.png) [@AutoDoc](https://forum.sienci.com/u/AutoDoc)\
**Post date:** [June 29, 2022, 11:40am UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/5 "2022-06-29T11:40:52Z")

</div>

In this particular case, I got a couple error 24s while running a job and wanted to poke through the console for clues. In general though, I want to be able to understand exactly what gSender is up to so I can get a better understanding of what’s going on under the hood. Limiting users to the last 50 lines of code just gives them enough to want more. The default copy length should be everything for the last job, be it 50 lines or 50,000.

---

<div class="post-metadata">

**Author:** ![gwilki](https://forum.sienci.com/user_avatar/forum.sienci.com/gwilki/32/366_2.png) [@gwilki](https://forum.sienci.com/u/gwilki)\
**Post date:** [June 29, 2022, 1:16pm UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/6 "2022-06-29T13:16:54Z")

</div>

@AutoDoc Understood, tks.

---

<div class="post-metadata">

**Author:** ![chrismakesstuff](https://forum.sienci.com/user_avatar/forum.sienci.com/chrismakesstuff/32/10759_2.png) [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)\
**Post date:** [March 2, 2024, 5:19am UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/10 "2024-03-02T05:19:49Z")

</div>

Wow, it looks like this bug still exists whoops 😳

---

<div class="post-metadata">

**Author:** ![CrookedWoodTex](https://forum.sienci.com/user_avatar/forum.sienci.com/crookedwoodtex/32/10446_2.png) [@CrookedWoodTex](https://forum.sienci.com/u/CrookedWoodTex)\
**Post date:** [March 2, 2024, 12:51pm UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/11 "2024-03-02T12:51:09Z")

</div>

Yeah, I ran into this recently (relatively) on 1.2.2 testing macros. Insidiously irritating. 😃

I’ll take some blame for not reporting it, but I was dealing with my gcode ignorance at the time. 🤫

---

<div class="post-metadata">

**Author:** ![walid\_kayhan](https://forum.sienci.com/letter_avatar_proxy/v4/letter/w/898d66/32.png) [@walid\_kayhan](https://forum.sienci.com/u/walid_kayhan)\
**Post date:** [July 18, 2024, 6:47pm UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/12 "2024-07-18T18:47:17Z")

</div>

This has been fixed in gSender v.1.4.8, ill close this thread for now 🙂

---

<div class="post-metadata">

**Author:** ![walid\_kayhan](https://forum.sienci.com/letter_avatar_proxy/v4/letter/w/898d66/32.png) [@walid\_kayhan](https://forum.sienci.com/u/walid_kayhan)\
**Post date:** [July 18, 2024, 6:47pm UTC](https://forum.sienci.com/t/new-guy-gsender-1-0-6-console-copy/6165/13 "2024-07-18T18:47:21Z")

</div>


