-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template label for pasting the currently opened file/selection #100
Comments
It would be a nice improvement! I think the placeholder needs to be configurable in the settings. |
Would be great to have another placeholder (something like sub-label), that would produce a path to the file - e.g.
(including the markdown code-block marks) And we could go even further - to paste all files opened in current tab, e.g. Prompting:
would result in:
I frequently find myself doing just that. |
I ditched the placeholders idea and went with simple Select and Ask logic. Please re-open the ticket if you would like to discuss further steps. |
I'm not sure I follow - the string |
No placeholder is used, you need to simply highlight a code block in the main editor and ask the question, highlighted code is included in the prompt automatically. However, I actually think having some proper placeholders will give the user better prompt customization. Reopening the ticket. |
I see. I'm struggling to find the exact prompt being sent. Is it simple |
Yes, the highlighted text is added after the user's prompt. You can see that if you reopen the chat tab. |
Something like For example, it could be used in actions like this: In my experience, the example improves the quality of the code. |
It would be a nice improvement to be able to type something like this in chat:
The
{{this}}
placeholder would be replaced on-the-fly with the content of currently focused file in IDE, or currently selected part of code (if any).I only chose
{{}}
format because o templating used in CodeGPT settings window, for better UX, we could go with!this
format.The text was updated successfully, but these errors were encountered: