github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #1551] Analyse this document. #26607

New Issue
Closed
opened 2026-04-22 02:57:48 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-22 02:57:48 -05:00
Owner
Copy Link

Originally created by @iplayfast on GitHub (Dec 15, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/1551

Thinking of an enhancement. With llava, you could ask what a picture is about and give the file location.
I wonder if it would be useful or worthwhile to analyse a document by giving it the file location.

Downsides, no rag so info can't be easily stored.
Upsides, would be super useful and can use as a reference, using the document itself as the storage medium while its running, ie load the vectors into memory that links to file locations.

Use case:
rewrite the code located at ./oldcode.py and save the new version at ./newcode.py change it to do ....

Originally created by @iplayfast on GitHub (Dec 15, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1551 Thinking of an enhancement. With llava, you could ask what a picture is about and give the file location. I wonder if it would be useful or worthwhile to analyse a document by giving it the file location. Downsides, no rag so info can't be easily stored. Upsides, would be super useful and can use as a reference, using the document itself as the storage medium while its running, ie load the vectors into memory that links to file locations. Use case: rewrite the code located at ./oldcode.py and save the new version at ./newcode.py change it to do ....
GiteaMirror added the feature request label 2026-04-22 02:57:48 -05:00
GiteaMirror commented 2026-04-22 02:57:49 -05:00
Author
Owner
Copy Link

@iplayfast commented on GitHub (Dec 15, 2023):

maybe using a /set parameter to insure safefy.
eg
/set parameter outDir "/home/ollama/generatedcode/"
anytime a file is written, the outDir is prepended it the directory.

<!-- gh-comment-id:1858359006 --> @iplayfast commented on GitHub (Dec 15, 2023): maybe using a /set parameter to insure safefy. eg /set parameter outDir "/home/ollama/generatedcode/" anytime a file is written, the outDir is prepended it the directory.
GiteaMirror commented 2026-04-22 02:57:50 -05:00
Author
Owner
Copy Link

@technovangelist commented on GitHub (Dec 19, 2023):

Hi, thanks for the issue.

If the file fits in the context of the model, then you can do something like this today:

ollama run llama2 "can you rewrite this fish function more efficiently: $(cat md.fish)"

We won't write to the filesystem, so it would be up to you to redirect output to a file. But usually you should verify before writing.

<!-- gh-comment-id:1862161092 --> @technovangelist commented on GitHub (Dec 19, 2023): Hi, thanks for the issue. If the file fits in the context of the model, then you can do something like this today: ``` ollama run llama2 "can you rewrite this fish function more efficiently: $(cat md.fish)" ``` We won't write to the filesystem, so it would be up to you to redirect output to a file. But usually you should verify before writing.
GiteaMirror commented 2026-04-22 02:57:50 -05:00
Author
Owner
Copy Link

@iplayfast commented on GitHub (Dec 19, 2023):

Hi, thanks for this great project. I've never enjoyed AI more!
Yes I've been doing exactly as you've said, and I don't know how this would work using llama.cpp just felt that if you can do it for images, you should be able to do it for text.
and if I specify a file to write to, it should be able to write to the file.

<!-- gh-comment-id:1863470950 --> @iplayfast commented on GitHub (Dec 19, 2023): Hi, thanks for this great project. I've never enjoyed AI more! Yes I've been doing exactly as you've said, and I don't know how this would work using llama.cpp just felt that if you can do it for images, you should be able to do it for text. and if I specify a file to write to, it should be able to write to the file.
GiteaMirror commented 2026-04-22 02:57:50 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (May 10, 2024):

Hi @iplayfast, will merge this with #834

<!-- gh-comment-id:2103643873 --> @jmorganca commented on GitHub (May 10, 2024): Hi @iplayfast, will merge this with #834
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#26607
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?