THanks, John, I'm sure you're right actually. So I've just written my
matching function like this:
(lambda (f) (string-match (concat "\\\(" fname "\\\)\\\([^[:alnum:]]\\\)*"
lname) f))
and if that has a nil result:
(lambda (f) (string-match (concat "\\\(" nname "\\\)\\\([^[:alnum:]]\\\)*"
I would not do that if I were you. The fuzzy match might inadvertently
send feed back to the wrong student. I would fall back to some manual
attachment if you do not find an exact match, e.g. using helm or ivy to
select the files for attachment, perhaps sorted and matched using their
fuzzy
On Thu, 1 Dec 2016, Matt Price wrote:
I have just done something I'm very excited about. Given a directory name
(the variable ~assignment~ in this case) and a list of student info, search
through the directory for files whose names contain the student names, and
attach those to newly created
I have just done something I'm very excited about. Given a directory name
(the variable ~assignment~ in this case) and a list of student info, search
through the directory for files whose names contain the student names, and
attach those to newly created subtrees.
Before now, manually attaching
