BUG Copy-Paste from One Note to Another Does Not Preserve Carriage Returns

Ryan
Ryan Member Posts: 121 ✭✭
edited November 21 in English Forum

This has been occurring since Logos 9 back in May 2021 as far as I know based on another post in the Notes forum. The hope was that it would've been addressed after the Logos 10 release but the issue still exists. 

Any chance this would be fixed soon?

Thanks!

https://community.logos.com/forums/t/200903.aspx

Tagged:

Comments

  • MJ. Smith
    MJ. Smith MVP Posts: 53,396

    Bumping this post in hopes of getting it attention.

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Doug Hiser
    Doug Hiser Member Posts: 48

    Ryan:  I would like to confirm this bug too on a MacBook Pro (M1 Max) running Logos 10.0 SR-2 on Ventura 13.0. The work around that I use is to put a space on each "blank" line.  Logos then will copy and paste correctly from one note to another.

    The problem I have not found a work-around for is copying and pasting nested outlines.  Logos likes to scramble these when they are pasted in another note.  If you would like to see this issue do the following:  

    1. Created a nested outline and put the corresponding line identifier as the text of each line.
    2. Then select the outline and hit the hot-key to copy.
    3. Move the cursor below the original outline. Type in a heading to identify the pasted outline.
    4. Hit the hot-key for paste.
    5. Compare.

    In the following screen shot you can see the copy and the corresponding paste result. Note: 2b is now 3, and 2b.i is now 3.i, and 2b.ii is now 3a. It is a real mess, and this has been a problem since Logos 9, if not earlier.

  • Ryan
    Ryan Member Posts: 121 ✭✭

    Ryan:  I would like to confirm this bug too on a MacBook Pro (M1 Max) running Logos 10.0 SR-2 on Ventura 13.0. The work around that I use is to put a space on each "blank" line.  Logos then will copy and paste correctly from one note to another.

    The problem I have not found a work-around for is copying and pasting nested outlines.  Logos likes to scramble these when they are pasted in another note.  If you would like to see this issue do the following:  

    1. Created a nested outline and put the corresponding line identifier as the text of each line.
    2. Then select the outline and hit the hot-key to copy.
    3. Move the cursor below the original outline. Type in a heading to identify the pasted outline.
    4. Hit the hot-key for paste.
    5. Compare.

    In the following screen shot you can see the copy and the corresponding paste result. Note: 2b is now 3, and 2b.i is now 3.i, and 2b.ii is now 3a. It is a real mess, and this has been a problem since Logos 9, if not earlier.

    Same deal

  • Willy Arnold
    Willy Arnold Member Posts: 97 ✭✭

    (Moved this to a new thread here, since I was reporting more issues than the title mentions)

    --------------

    1. Copying Links is Broken

    2. Linking to External Files is Broken

    3. Copying Text with Carriage Returns is Broken

    All of this used to work fine back in Logos 7 or 8 and all got broken with new versions of notes. These issues were not fixed in the life of Logos 9 and still persist in Logos 10.

  • Savanna Lineberger
    Savanna Lineberger Member, Community Manager, Logos Employee Posts: 766

    Ryan said:

    This has been occurring since Logos 9 back in May 2021 as far as I know based on another post in the Notes forum. The hope was that it would've been addressed after the Logos 10 release but the issue still exists. 

    Any chance this would be fixed soon?

    Thanks!

    https://community.logos.com/forums/t/200903.aspx

    Hi Ryan, 

    Thank you for bringing this back up, this is certainly still an issue. Looks like we have an open case for this issue, I will update it to include this thread as well. Unfortunately I don't have a timeframe on when this might be resolved, but I will alert the team once more. 

  • Ryan
    Ryan Member Posts: 121 ✭✭

    Finally fixed with the latest 23.0.30 release. Thank you!