Achim Gratz writes:
> Bastien writes:
>>> We'll have to tell users to forcibly update the tags again.
>>
>> For the users who will not do this, only the release_7.8.11
>> will not properly set, right?
>
> Yes. Another sticky point is that any clones of the orgmode repo (like
> the one on repo.or
Bastien writes:
>> We'll have to tell users to forcibly update the tags again.
>
> For the users who will not do this, only the release_7.8.11
> will not properly set, right?
Yes. Another sticky point is that any clones of the orgmode repo (like
the one on repo.or.cz) will not automatically pick
Achim Gratz writes:
> Bastien writes:
>> Can you summarize what would be the change and why it is called for?
>
> The tag release_7.8.11 is affixed to the merge commit, which means that
> it's first parent is on the master branch rather than maint. The change
> sets it back one commit so that it
Bastien writes:
> Can you summarize what would be the change and why it is called for?
The tag release_7.8.11 is affixed to the merge commit, which means that
it's first parent is on the master branch rather than maint. The change
sets it back one commit so that it correctly is located on the mai
Hi Achim,
Achim Gratz writes:
> It doesn't automatically propagate. Otherwise, it's Bastiens decision —
> I can push the change if he wants to.
Can you summarize what would be the change and why it is called for?
Thanks,
--
Bastien
Nick Dokos writes:
> Does that have any undesirable consequences? If not, can this be done on
> the repo?
It doesn't automatically propagate. Otherwise, it's Bastiens decision —
I can push the change if he wants to.
> I actually did the above in my clone and then fetched tags again which
> reset
Achim Gratz wrote:
> Nick Dokos writes:
> > OK. Is there no way to fix that? That's pretty confusing.
>
> If you already know the tag is on a merge commit on the wrong side:
>
> git tag fixup release_7.8.11
> git tag -d release_7.8.11
> git tag release_7.8.11 fixup^2
> git tag -d fixup
>
Does
Nick Dokos writes:
> OK. Is there no way to fix that? That's pretty confusing.
If you already know the tag is on a merge commit on the wrong side:
git tag fixup release_7.8.11
git tag -d release_7.8.11
git tag release_7.8.11 fixup^2
git tag -d fixup
> And how can I tell that I have fallen into t
Achim Gratz wrote:
> Nick Dokos writes:
> > Achim Gratz wrote:
> >
> >> Nick Dokos writes:
> >> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> >> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> >> > fixed somehow, either because of a rever
Nick Dokos writes:
> Achim Gratz wrote:
>
>> Nick Dokos writes:
>> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
>> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
>> > fixed somehow, either because of a revert or because some fix was
>> > actu
Achim Gratz wrote:
> Nick Dokos writes:
> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> > fixed somehow, either because of a revert or because some fix was
> > actually applied, I don't know
Nick Dokos writes:
> This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> fixed somehow, either because of a revert or because some fix was
> actually applied, I don't know which. It was working until 7.8
Nick Dokos writes:
> Nick Dokos wrote:
>
>> I haven't chased it all the way down because the reverts are
>> making my head spin, but it may be that somehow the above commit
>> got lost somewhere - or it got fixed and then the big revert lost
>> the fix. Maybe Eric or Bastien remembers what happe
Nick Dokos wrote:
> I haven't chased it all the way down because the reverts are
> making my head spin, but it may be that somehow the above commit
> got lost somewhere - or it got fixed and then the big revert lost
> the fix. Maybe Eric or Bastien remembers what happened.
>
This doesn't make s
Nick Dokos wrote:
> Nick Dokos wrote:
>
> > Loris Bennett wrote:
> >
> > > I used to be able do all sorts of stuff with sh, Perl and R. Now the
> > > following example no longer works:
> > >
> > > ,---
> > > | #+begin_src sh :dir /@:/t
Nick Dokos wrote:
> Loris Bennett wrote:
>
> > I used to be able do all sorts of stuff with sh, Perl and R. Now the
> > following example no longer works:
> >
> > ,---
> > | #+begin_src sh :dir /@:/tmp
> > | echo "Executed by `whoami` on
Loris Bennett wrote:
> I used to be able do all sorts of stuff with sh, Perl and R. Now the
> following example no longer works:
>
> ,---
> | #+begin_src sh :dir /@:/tmp
> | echo "Executed by `whoami` on `hostname` in `pwd`"
> | #+end_src
Nick Dokos writes:
> Achim Gratz wrote:
>
>> Nick Dokos writes:
>> > Loris Bennett wrote:
>> >> In the *Org-Babel Error Output* buffer, I get the following:
>> >>
>> >> /bin/bash: /scpc:x@xx:/tmp/sh-script-7472puH: No such file or
>> >> directory
>>
>> It would seem that you are tryi
Achim Gratz wrote:
> Nick Dokos writes:
> > Loris Bennett wrote:
> >> In the *Org-Babel Error Output* buffer, I get the following:
> >>
> >> /bin/bash: /scpc:x@xx:/tmp/sh-script-7472puH: No such file or
> >> directory
>
> It would seem that you are trying to use a remote file with a l
Nick Dokos writes:
> Loris Bennett wrote:
>> In the *Org-Babel Error Output* buffer, I get the following:
>>
>> /bin/bash: /scpc:x@xx:/tmp/sh-script-7472puH: No such file or
>> directory
It would seem that you are trying to use a remote file with a local
bash. That won't work, especial
Loris Bennett wrote:
> Bastien writes:
>
> > Hi Loris,
> >
> > "Loris Bennett" writes:
> >
> >> Nothing works now, not even
> >>
> >> #+BEGIN_SRC sh :file tmp.txt :dir /x@xxx:
> >> echo hostname
> >> #+END_SRC
> >
> > Maybe you don't have permission to read the /tmp/ dir
> > on the rem
Bastien writes:
> Hi Loris,
>
> "Loris Bennett" writes:
>
>> Nothing works now, not even
>>
>> #+BEGIN_SRC sh :file tmp.txt :dir /x@xxx:
>> echo hostname
>> #+END_SRC
>
> Maybe you don't have permission to read the /tmp/ dir
> on the remote machine?
>
> Anyway, it's hard to debug with so
Hi Loris,
"Loris Bennett" writes:
> Nothing works now, not even
>
> #+BEGIN_SRC sh :file tmp.txt :dir /x@xxx:
> echo hostname
> #+END_SRC
Maybe you don't have permission to read the /tmp/ dir
on the remote machine?
Anyway, it's hard to debug with so little information.
--
Bastien
Hi Bastien,
Bastien writes:
> Hi Lorise,
>
> "Loris Bennett" writes:
>
>> I have just updated to emacs 24.2.50.1 and org 7.9-32-g805a9f-elpa and
>> am having this problem again even with an ECM. Commenting out the
>> declaration as suggested above no longer helps.
>>
>> Any suggestions?
>
> Ca
Hi Lorise,
"Loris Bennett" writes:
> I have just updated to emacs 24.2.50.1 and org 7.9-32-g805a9f-elpa and
> am having this problem again even with an ECM. Commenting out the
> declaration as suggested above no longer helps.
>
> Any suggestions?
Can you share the Perl script that is not worki
"Loris Bennett" writes:
> Nick Dokos writes:
>
>> Loris Bennett wrote:
>>
>>> Nick Dokos writes:
>>>
>>> > Loris Bennett wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> When I try to run a Perl script remotely via ":dir", I get the following
>>> >> error:
>>> >>
>>> >> ,-
Nick Dokos writes:
> Loris Bennett wrote:
>
>> Nick Dokos writes:
>>
>> > Loris Bennett wrote:
>> >
>> >> Hi,
>> >>
>> >> When I try to run a Perl script remotely via ":dir", I get the following
>> >> error:
>> >>
>> >> ,--
Loris Bennett wrote:
> Nick Dokos writes:
>
> > Loris Bennett wrote:
> >
> >> Hi,
> >>
> >> When I try to run a Perl script remotely via ":dir", I get the following
> >> error:
> >>
> >> ,-
> >> | org-babel-local-file-na
Nick Dokos writes:
> Loris Bennett wrote:
>
>> Hi,
>>
>> When I try to run a Perl script remotely via ":dir", I get the following
>> error:
>>
>> ,-
>> | org-babel-local-file-name: Invalid function: with-parsed-tramp-file-
Loris Bennett wrote:
> Hi,
>
> When I try to run a Perl script remotely via ":dir", I get the following
> error:
>
> ,-
> | org-babel-local-file-name: Invalid function: with-parsed-tramp-file-name
> `---
Hi,
When I try to run a Perl script remotely via ":dir", I get the following
error:
,-
| org-babel-local-file-name: Invalid function: with-parsed-tramp-file-name
`--
31 matches
Mail list logo
