RobC Posted February 1 Posted February 1 I have a workflow that relies heavily on GREP Find & replace, and as there is no way to save the searches (I don't think?) I just cut and paste my set of searches from a notes app. This has been working fine on Affinity 1 but I'm trying to move to Affinity 2. If I copy \n (special character for para return) it now pastes it as \\n as I assume its replacing \ for the special character for \ which is \\ . I realise that I could actually just type a para return on my notes app to copy but the disadvantage of this for me is that it won't be visible (so could be missed) and that it will also make the searches appear over multiple lines in the notes app Can anyone suggest another workaround Rob Quote
lacerto Posted February 1 Posted February 1 Unless you happen to have also a Windows computer and Windows version of Publisher (where this issue does not happen),one thing what comes to mind is selecting the \\ special character and typing \ from the keyboard (Option+Shift+7 on my MacBook), which would turn \\n to a paragraph break special character (that might be a bit faster than selecting \\n and picking the paragraph special character from the menu). Personally I think it was a mistake to add this functionality [macOS version only] for the backslash character, because single backslash still works as a search character within Normal (non-GREP) searches, and because keeping GREP searches plain text (retaining e.g. \n instead of using a special character) is more compatible. Quote
RobC Posted February 1 Author Posted February 1 Thanks for your response but I may have misunderstood. Typing \\¶ or \¶ in the find box doesn't seem find the para breaks. It's strange that I can copy \t from TextEdit and it finds tabs but \n doesn't find para breaks. As you say, I wouldn't want to have to select para break from the pull down menu each time Shame that you can't save searches as that would be so much easier (I see it's a frequently requested feature) Quote
lacerto Posted February 1 Posted February 1 Sorry, I might myself have misunderstood... This is what I meant (replacing mere \\ (in \\n) with \ typed from the keyboard, so that Affinity automatically replaces \n with a paragraph special character): findparabreaks.mp4 Quote
RobC Posted February 1 Author Posted February 1 Got you - I'm just trying to avoid keystrokes as I have to run approx 20 GREPS (that I cut and paste from TextEdit) Thanks for your efforts, but I guess I'll stick with Publisher 1 until Affinity introduce saved searches or undo this 'enhancement' lacerto 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.