Forum Discussion
Former Member
4 years agoThanks austin !
We will look further into detail on using the @
convention when implementing the fix for the 2nd issue.
This is sort of two requests in one. I’m currently using op 1.10.3.
\n\nop edit document UUID FILE --filename TARGETFILE --title TARGETFILE --account ACCOUNT
) any existing metadata (such as notesPlain
) is removed. This feels like a bug.op get item UUID --fields notesPlain > notes
), then edit the document (see above). I have to add the notes through the MacOS UI as the editing the item to add the notesPlain
only gives me the last line of the file (op edit item UUID notesPlain=$(cat notes)
).It would be good if #1 was fixed. It would also be good if I knew how to add a multi-line notes entry on edit item
when the item is a document
. Suggestions are welcome, but I have tried op encode
(I get the encoded value in notesPlain
) and have also tried turning it into an otherwise normal JSON field (the newlines remain encoded as \\n
).
1Password Version: Not Provided
\nExtension Version: Not Provided
\nOS Version: Not Provided
\nSync Type: Not Provided
This is sort of two requests in one. I’m currently using op 1.10.3.
\n\nop edit document UUID FILE --filename TARGETFILE --title TARGETFILE --account ACCOUNT
) any existing metadata (such as notesPlain
) is removed. This feels like a bug.op get item UUID --fields notesPlain > notes
), then edit the document (see above). I have to add the notes through the MacOS UI as the editing the item to add the notesPlain
only gives me the last line of the file (op edit item UUID notesPlain=$(cat notes)
).It would be good if #1 was fixed. It would also be good if I knew how to add a multi-line notes entry on edit item
when the item is a document
. Suggestions are welcome, but I have tried op encode
(I get the encoded value in notesPlain
) and have also tried turning it into an otherwise normal JSON field (the newlines remain encoded as \\n
).
1Password Version: Not Provided
\nExtension Version: Not Provided
\nOS Version: Not Provided
\nSync Type: Not Provided
Thanks austin !
\n\nWe will look further into detail on using the @
convention when implementing the fix for the 2nd issue.
Thanks
We will look further into detail on using the @
convention when implementing the fix for the 2nd issue.