nemo
nemo copied to clipboard
teuben
the file adjustments so far
When I tried it, the last check showed was TESTSUITE: OK /home/teuben/nemo/src/kernel/misc the next one should have been TESTSUITE: OK /home/teuben/nemo/src/kernel/tab but it never showed up for me. Is it waiting for a pipe?
Yea I was haiving that problem myself. I noticed that it would arise every time I removed tabplot from the bin even after I did mknemo to bring it back up. When I synced up my branch to the master, it went away. However, I removed the tabplot and it came back which was very weird. I am still trying to find a solution.
On Wed, Oct 6, 2021 at 11:43 PM Peter Teuben @.***> wrote:
When I tried it, the last check showed was TESTSUITE: OK /home/teuben/nemo/src/kernel/misc the next one should have been TESTSUITE: OK /home/teuben/nemo/src/kernel/tab but it never showed up for me. Is it waiting for a pipe?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/83#issuecomment-937418598, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALE7F2D4CK6HGKFC2XSCHU3UFUJOBANCNFSM5FHFE5VQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
it seems the line
$(EXEC) tabplot -;
in the tabplot target will hang, since it's reading from a pipe, but nothing is feeding it.
On 10/7/21 6:50 AM, Vmbundu wrote:
Yea I was haiving that problem myself. I noticed that it would arise every time I removed tabplot from the bin even after I did mknemo to bring it back up. When I synced up my branch to the master, it went away. However, I removed the tabplot and it came back which was very weird. I am still trying to find a solution.
On Wed, Oct 6, 2021 at 11:43 PM Peter Teuben @.***> wrote:
When I tried it, the last check showed was TESTSUITE: OK /home/teuben/nemo/src/kernel/misc the next one should have been TESTSUITE: OK /home/teuben/nemo/src/kernel/tab but it never showed up for me. Is it waiting for a pipe?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/83#issuecomment-937418598, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALE7F2D4CK6HGKFC2XSCHU3UFUJOBANCNFSM5FHFE5VQ
. Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/83#issuecomment-937676514, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZ4MGLHA36L3Z2CNE5S32DUFV3NZANCNFSM5FHFE5VQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Oh I see what you mean
Sent from my iPhone
On Oct 7, 2021, at 8:54 AM, Peter Teuben @.***> wrote:
it seems the line
$(EXEC) tabplot -;in the tabplot target will hang, since it's reading from a pipe, but nothing is feeding it.
On 10/7/21 6:50 AM, Vmbundu wrote:
Yea I was haiving that problem myself. I noticed that it would arise every time I removed tabplot from the bin even after I did mknemo to bring it back up. When I synced up my branch to the master, it went away. However, I removed the tabplot and it came back which was very weird. I am still trying to find a solution.
On Wed, Oct 6, 2021 at 11:43 PM Peter Teuben @.***> wrote:
When I tried it, the last check showed was TESTSUITE: OK /home/teuben/nemo/src/kernel/misc the next one should have been TESTSUITE: OK /home/teuben/nemo/src/kernel/tab but it never showed up for me. Is it waiting for a pipe?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/83#issuecomment-937418598, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALE7F2D4CK6HGKFC2XSCHU3UFUJOBANCNFSM5FHFE5VQ
. Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/83#issuecomment-937676514, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZ4MGLHA36L3Z2CNE5S32DUFV3NZANCNFSM5FHFE5VQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Do you have any suggestions for what I should feed into the pipe?
On Thu, Oct 7, 2021 at 11:17 AM Vanday Bundu @.***> wrote:
Oh I see what you mean
Sent from my iPhone
On Oct 7, 2021, at 8:54 AM, Peter Teuben @.***> wrote:
it seems the line
$(EXEC) tabplot -;in the tabplot target will hang, since it's reading from a pipe, but nothing is feeding it.
On 10/7/21 6:50 AM, Vmbundu wrote:
Yea I was haiving that problem myself. I noticed that it would arise every time I removed tabplot from the bin even after I did mknemo to bring it back up. When I synced up my branch to the master, it went away. However, I removed the tabplot and it came back which was very weird. I am still trying to find a solution.
On Wed, Oct 6, 2021 at 11:43 PM Peter Teuben @.***> wrote:
When I tried it, the last check showed was TESTSUITE: OK /home/teuben/nemo/src/kernel/misc the next one should have been TESTSUITE: OK /home/teuben/nemo/src/kernel/tab but it never showed up for me. Is it waiting for a pipe?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/83#issuecomment-937418598, or unsubscribe
< https://github.com/notifications/unsubscribe-auth/ALE7F2D4CK6HGKFC2XSCHU3UFUJOBANCNFSM5FHFE5VQ
. Triage notifications on the go with GitHub Mobile for iOS
< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/83#issuecomment-937676514, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAZ4MGLHA36L3Z2CNE5S32DUFV3NZANCNFSM5FHFE5VQ . Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/teuben/nemo/pull/83#issuecomment-937764018, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALE7F2EYRSDI2WTLBDWEIWDUFWKADANCNFSM5FHFE5VQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.